PM20642: FAILED APPLICATION DEPLOYMENT DOES NOT LEAVE THE WORKSPACE CLEANED PROPERLY

Error description

• Business-level application (BLA) code plugs into the  application management deployment framework to create a BLA  and composition unit (CU) for the new application. After it  does that, more tasks added by the product extension run and  fail, and the BLA and CU are left hanging around. The sceanrio  is a failed deployment and the session is then saved. If the  session is discarded or if the deployment succeeds, things  work correctly. So, the problem is that a failed deployment is  not leaving the work space clean. No warning is issued to  notify the user.  

Local fix

Remove any directories or files created, clean work space.  

http://www-01.ibm.com/support/docview.wss?uid=swg1PM20642
CUS folder path
<WAS_HOME>/profiles/<dmgr>\Dmgr01\config\cells\<CellName>\cus
BLAS folder path
<WAS_HOME>/profiles/<dmgr>\Dmgr01\config\cells\<CellName>\blas

--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

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

Problem(Abstract)

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

http://www-01.ibm.com/support/docview.wss?uid=swg21455322
--
Thanks and Regards
Bhaskar Ramaraju
http://www.linkedin.com/in/ramarajubhaskar

Collector Tool

Someone asked me how to run collector tool. IBM Doc says, run the tool not from APPSERVER_INST_PATH/bin, but run from working directory. What exactly is that?

The collector tool gathers information about your WebSphere Application Server installation and packages it in a Java archive (JAR) file that you can send to IBM Customer Support to assist in determining and analyzing your problem. Information in the JAR file includes logs, property files, configuration files, operating system and Java data, and the presence and level of each software prerequisite.

collector command - summary option

WebSphere Application Server products include an enhancement to the collector tool beginning with Version 5.0.2, known as the collector summary option.

The collector summary option helps you communicate with WebSphere Application Server technical staff at IBM Support. Run the collector tool with the -Summary option to produce a lightweight text file and console version of some of the information in the Java archive (JAR) file that the tool produces without the -Summary parameter. You can use the collector summary option to retrieve basic configuration and prerequisite software level information when starting a conversation with IBM Support.

The collector summary option produces version information for the WebSphere Application Server product and the operating system as well as other information. It stores the information in the Collector_Summary.txt file and writes it to the console. You can use the information to answer initial questions from IBM Support or you can send the Collector_Summary.txt file directly to IBM Support.

Collector tool collect key information including ffdc, configuration, logs, and so on and makes a jar file with all the information. So, depending on your configuration and all, jar file may occupy lot of space. So, IBM docs says that, create a folder out of appserver installation path.
Example,
mkdir /tmp/collector
cd /tmp/collector

Then run the script as needed
/appserver/instpath/profiles/profilename/bin/collector.sh
or
/appserver/instpath/profiles/profilename/bin/collector.sh -summery