Things to validate:
- Validate that each serverindex.xml file from the master repository,
has no reference to the XYZ application.
- Validate that each node binary installation has no reference to the
XYZ application.
Note: v5 and v5.1 <install_root>/InstalledApps
Note: v6
<install_root>/profiles/<profilename>/InstalledApps/<cellName>
- Validate that each config/cells/<cellname>/application
directory, has no reference to the XYZ application.
If the above steps are validated successfully and problem still
persists then it is possible the cause is the application ear itself.
Example:
XYZ.ear
application.xml in meta-inf has following reference
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application id="Application_ID">
<display-name>DefaultEAR</display-name>
<module id="WebModule_1110326143477">
<web>
<web-uri>xyz.war</web-uri>
<context-root>service</context-root>
</web>
</module>
</application>
As you can see the display-name is incorrect in display-name tag. This
is the reason why the application can not be deployed. The deployment
process thinks that XYZ already exits in
Applications -> Enterprise Applications -> Enterprise
Applications list.
In this case we did have a DefaultEAR deployed so application
deployment was failing indicating that the application already exits.
To correct this:
1. Import the application into the Application Assembly tool kit
(ASTK)
2. Correct the application.xml display name tag.
3. Export the application
Try deploying the application via the adminconsole.
If this fails then please collect our mustgather doc
General/swg21145599.html
And open a PMR with IBM support.
|