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

Problem(Abstract)

When installing an application or performing other administrative actions in WebSphere Process Server version 7.x, the following error is received: 
CWWMH1001W Composition unit already exists/cannot load document deployment.xml

Symptom

The following error message may be seen:

[9/8/10 13:56:40:248 PDT] 00000019 DefaultSyncHa W CWWMH1001W: 
Unexpected error occurred during synchronization of configuration files 
associated with business-level applications. Error data: 
com.ibm.wsspi.management.bla.op.OpExecutionException: Cannot load 
document applications/MyApp.ear/deployments/MyApp/deployment. xml 
relative to the cell configuration context. which is 
Caused by: java.io.FileNotFoundException: C:\Program 
Files\IBM\WID7_WTE\runtimes\bi_v7\profiles\qwps\config\cells\qcell\appli 
cations\MyApp.ear\deployments\MyApp\deployment.xml 
(The system cannot find the path specified.) 

or

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

Cause

This is most frequently observed during the installation or removal of applications, but it may also turn up during other administration tasks such as deleting servers.

The issue maybe caused by WebSphere Application Server APAR PM20642.

In this scenario, if there is an error with the deployment of a module, then this bad deployment is saved, then the WebSphere Application Server configuration will be out of sync.

In WebSphere Process Server, this often happens with a module that has WebSphere Business Integration Adapter Resources that might not be complete or set up properly.
When deploying using WebSphere Integration Developer using "Add Projects", the configuration changes for this bad deployment are automatically saved.

Even after the application is removed, you might not be able to do any further or new application installs or uninstalls (even with a corrected module).

 

Resolving the problem

The manual workaround is to delete the /blas and /cus directories for the bad application from the configuration.

The resources will be located in the config directory of the profile.:

<profile name>/config/cells/qcell/blas 
<profile name>/config/cells/qcell/cus 


The WebSphere Application Server team has built interim fixes for this defect for WebSphere Application Server V7.0.0.7 and V7.0.0.11. If needed, these interim fixes can be obtained from the WebSphere Application Server Support through a PMR Request. Obtaining PM20642 will help avoid the out of sync configuration during failed deployments. 

If the above Cause and Resolution do not match your problem then a different scenario may be responsible for the issue.