After deployment of the tomcat probe to a robot installed in a Solaris OS, the probe doesn't show up in IM, neither in Admin Console. This same behavior was experienced also with the jboss probe, however, other probes like the zones probe could be successfully deployed, and it showed up in the AC and IM consoles.
In controller.log, you can find error messages like:
Oct 19 16:37:43:101  Controller: MyStringExpand (rm "probes/application/jboss/jar/nimsoft.jar" "probes/application/jboss/jar/nimsoft-eb-jsr160.jar" "probes/application/jboss/jar/Twofish.jar")...
Oct 19 16:37:43:103  Controller: Pre-install command rm "probes/application/jboss/jar/nimsoft.jar" "probes/application/jboss/jar/nimsoft-eb-jsr160.jar" "probes/application/jboss/jar/Twofish.jar" returned 512 exited with 2
Oct 19 16:37:43:104  Controller: inst_execute - pre-install failure; installation of section SOLARIS in package tomcat aborted
Oct 19 16:37:43:104  Controller: SREPLY: status = 7(temporarily out of resources) ->192.xxx.xxx.xx/59430
and in distsrv.log:
Oct 19 07:02:32:939  distsrv: unzip - zipfile not found for C:\Program Files (x86)\Nimsoft/archive/tomcat.zip
Oct 19 07:02:33:124  distsrv: Dependency check error: Unable to find any version of package jre_solaris on /domain/hub/unknown
jre_solaris was installed in the system.
Defined probe pre-requisites were preventing a successfully install of the probe in the robot.
1. If you are using jboss probe, deactivate the probe and move the below
files into different directory.
2. Log In to Primary HUB Server via Infrastructure Manager
3. Go to Archive
> Your HUB > Application. Highlight and right click tomcat probe and go
4. Package Editor will come. Go [SOLARIS] tab > [Miscellaneous] tab
5. Remove all the arguments in [Pre install command] section.
6. Save the change and finish the Package Editor.
7. Deploy the pacakge.
As always, please contact CA Technologies support for CA UIM if you have further questions.