A composition unit with name MAXIMO already exists

After the WAS installation is abnormal, an error  a composition unit with name XXX already exists is reported. The solution is as follows:

http://www-01.ibm.com/support/docview.wss?uid=swg21663042

A composition unit with name MAXIMO already exists

 

Technote (troubleshooting)


Problem(Abstract)

Unable to deploy maximo.ear file due to partial files being left over in the deployment directories.

Symptom

When attempting to install the maximo.ear file the following message is received.

ADMA5016I: Installation of MAXIMO started.

A composition unit with name MAXIMO already exists. Select a different
application name.


Cause

This is caused by a previous failed deployment which left deployment files in the WebSphere directory.

Resolving the problem

To resolve this issue, delete the following deployment folders, replacing MAXIMO.ear with the name of the ear file deployed.

\profiles\ctgAppSrv01\config\cells\ctgCell01\applications\MAXIMO.ear.
\profiles\ctgAppSrv01\config\cells\ctgCell01\cus\MAXIMO
\profiles\ctgAppSrv01\config\cells\ctgCell01\blas\MAXIMO
\profiles\ctgAppSrv01\installedApps\ctgCell01\MAXIMO.ear

\profiles\ctgDmgr01\config\cells\ctgCell01\cus\MAXIMO
\profiles\ctgDmgr01\config\cells\ctgCell01\blas\MAXIMO
\profiles\ctgDmgr01\config\cells\ctgCell01\applications\MAXIMO.ear

Also open

IBM\WebSphere\AppServer\profiles\<profileName>\config\cells\<cellName>\n
odes\<nodeName>\serverindex.xml

Look for <deployedApplications>maximo.ear</deployedApplications> and remove that line, once done try and redeploy the maximo.ear file.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325340662&siteId=291194637