Overview:
In WebSphere® 4.0, an EAR file is expanded only if the following
is true:
- The node where the EAR file is located is on the same node where the
EAR will be expanded.
and
- The node where the adminserver is running on and client connected to
is the same node where the EAR will be expanded.
and
- The node where the enterprise application is installed is on the same
node where the EAR will be expanded.
Administration server's WorkLoad Management (WLM) feature in WebSphere
4.0 allows you to violate these three requirements.
WLM selects the target server for request routing either randomly or by
using preferLocal (local to client). Since the administration server is
WLM enabled by default, the request to
install the Enterprise Application does not always go to the adminserver
that the client is connected to; therefore, the EAR is not expanded if the
request goes to a different server.
This is why a local console or a single node environment does not
experience this problem.
Solution:
Apply Interim Fix PQ60657.
Go to http://www14.software.ibm.com/webapp/download/product.jsp?cat=&s=p&id=TDUN-49EVRT&pf=&presb=&type=s&postsb=v
and search on PQ60657.
There is an interim fix for both WebSphere 4.0.2, 4.0.3 and 4.0.4. It is
included in Fix Pack 5 (4.0.5).
Alternative Solution:
If after installation the EAR file is not expanded into the installedApps
directory, use the EarExpander tool to expand it properly:
Usage: EARExpander.(bat|sh) -ear <ear file or directory> -expandDir
<directory in which to expand ear> -operation <expand |
collapse> [-expansionFlags <all | war>]
Make sure the -expandDir is within the InstalledApps directory and
named according to the directory given in the final installation window of
the administrative console.
|