|
Pete,
Maybe try this:
\QIBM\UserData\WebSphere\AppServer\V6\Base\profiles\*PROFILE
NAME*\installedApps ....etc....
Robert
|---------+--------------------------------------------------->
| | Pete Helgren <Pete@xxxxxxxxxx> |
| | Sent by: |
| | web400-bounces+rking=estes-express.com@m|
| | idrange.com |
| | |
| | |
| | 08/23/2007 08:54 AM |
| | Please respond to Web Enabling the AS400|
| | / iSeries |
|---------+--------------------------------------------------->
>------------------------------------------------------------------------------------------------------------|
| |
| To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx> |
| cc: |
| Subject: [WEB400] Websphere applications folder |
>------------------------------------------------------------------------------------------------------------|
I deployed an EAR using the Websphere console rather than the HTTP Admin
application and I can't figure out where the application deployed. The
app is running but looking at the configuration using the Websphere
Console I can't make heads or tails out of where WAS put the files. It
asked for a folder name when I deployed but it didn't tell me the root
folder name it would be appended to.
Anyone know how to find the deployed files? With Web apps I can pretty
much count on www as being the root folder for web deployments. For
WAS, where the heck did that stuff deploy to? Its WAS Express 6.0 if
that makes any difference.
Pete Helgren
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.