× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Mark Phippard
>
> What problems are you having with WAS 5?  The structures of a WAS 4 and
> WAS 5 application are exactly the same.  All that has changed is the root
> location where the application installs to by default.  WAS 4 AE
> and WAS 4
> AES also had different root locations, as does each of the WAS 5
> versions.
>  This allows you to run each of the versions on the same machine.

Wrong.  The "root location" for WebSphere is "\QIBM\UserData\WebASE\ASE5".
However, the structure beneath that has changed from WAS4 to WAS5.
Specifically, the structure under installedApps has changed.

Let me give you an example:

\QIBM\UserData\WebASE\ASE5\WDSC\installedApps\PBD270_WDSC\RETAILSTOR.ear

The above is the path used to install the RETAILSTOR ear file, IBM's own
example.  Note the fact that the "cell name" PBD270_WDSC is stuck in there.
PBD270 is the node name of my machine, although that's not really documented
anywhere.  In any event, since the cell name changes on each machine, that
means the directory structure will be different on every machine.

This is a nightmare for deployment, and is absolutely unnecessary.  Shoving
the machine ID in the cell name should have been a configurable option.
Instead, it's hardcoded in order to support the Network Deployment model.

If you think this is acceptable, then you and I have different definitions
of acceptable, so please let's drop this.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.