wasp fails to activate after deploying a package

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

A common use case is where after deploying a package to the OC Server robot, the wasp probe fails to activate. 

A probe will show up in the console and can be deleted there, however, a package only shows up when viewing Installed Packages either in IM via controller > configure > Status or Admin Console select the robot > Installed Packages. 

This is also applicable if a package was deployed by mistake or has been deprecated. 

In the logs it will show:

Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\webservices_rest] is not valid
    at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:751)
    at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:708)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\uimapi] is not valid
    at org.apache.catalina.webresources.StandardRoot.createMainResourceSet(StandardRoot.java:751)
    at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:708)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

Environment

• Any UIM version

Resolution

IM console 

go to the robot with the package to be removed 

select controller

Ctrl + P 

from the drop-down menu select inst_pkg_remove

at the bottom left corner under 'package' enter the package name

click the green arrow

 

Admin Console 

go to the robot

Probes

controller

View Probe Utility in New Window

select inst_pkg_remove

enter the name in either the 'probe' or 'package' field. 

click the green arrow

 

OR just edit the wasp.cfg and remove the entry that is missing based on the IM-> Controller ->Setup-> installed packages and compare the installed packages.

Additional Information

Note if the removed package was a wasp webapp go to:

wasp configure > webapps > mcs-ws > right click Edit > set Startup Mode: Manual

or 

wasp raw configure > webapps > select mcs-ws > click Delete Section. 

Deactivate, activate. 

This is all due to the fact that once a webapp is removed, wasp will not start if it is still configured to load it.