Please find below the latest episode of debugging joy.
Recently, a patient came into my office complaining about the pain he has with one of his applications. The patient mentioned that he could not perform any tip deployment of this specific application where Advanced content gets deployed on the Process Center Server. The tip deployment fails independent of triggering in Integration Designer or Process Designer. For instance, the following error popup appears in Process Designer:
As expert debuggers, you and I know that we should look into the logs (Dmgr and AppTarget of Process Center) first, since it seems to be a problem at the server-side (not client-side). The AppTarget logs showed the entire stack trace of the exception:
[2/11/16 3:22:20:598 PST] 000001ac ObjectManagem E Process application or Toolkit tip could not be deployed. Please check the server logs for more information.: CWPFD2005W: Because the "HSAV1-Tip-Hiring_Sample_Advanced_Library.jar" asset already exists, the installation of the process application has been canceled.
com.ibm.bpm.pal.PALException: CWPFD2005W: Because the "HSAV1-Tip-Hiring_Sample_Advanced_Library.jar" asset already exists, the installation of the process application has been canceled.
Caused by: com.ibm.bpm.fds.common.FDSException: CWPFD2005W: Because the "HSAV1-Tip-Hiring_Sample_Advanced_Library.jar" asset already exists, the installation of the process application has been canceled.
OK, so the exception seems to be pretty clear: „Because the "HSAV1-Tip-Hiring_Sample_Advanced_Library.jar" asset already exists, the installation of the process application has been canceled.“. Now this .jar-file looks like an app specific .jar-file. We can confirm that by looking into the Advanced Content of the process app using Integration Designer:
Yep. There it is. Now the question is what blocks the tip deployment in terms of this .jar-file and how can we resolve this issue?!
To answer the question what exactly is blocking, we'll need to think about tip deployment itself. Well, via tip deployment the Advanced content gets installed. Advanced content can be EAR files, BLAs, SCA-Modules and … Assets. And where can we view the assets? Bingo! In the WAS Admin Console under Applications > Application Types > Assets .
Looking into this section we can see all assets of the asset repository. And we can see that the trouble maker is also listed here:
Great, if we just delete this asset the tip deployment should run through since there is no blocking asset anymore.
Furthermore, there is no big pain with that since the asset is included in the process application and will be installed by the next tip deployment anyway. Based on to these findings, let's simply delete this .jar-file in the Assets manually by using the „Delete“ option in the WAS Admin Console.
This removed the blocking asset and the tip deployment successfully went through the next attempt. Of course, this also might help patients with other occurrences of this exception where other assets are involved. It is hard to tell what caused the remain of the asset. However, the problem can occur when this asset got exported and imported, for example (this has been reproduced).
Now I hope this will help you with your tip deployments. And if it does not, take two of these and call me in the morning.
Your Doc D