1- On the 'cabi' robot
Copy the uim.jks keystore file from:
2- Restart the cabi and wasp probes on the cabi robot.
If it still fails and this is a new installation of bundled cabi, please perform the following steps below.
1- Using the IM Console, Deactivate wasp and cabi probes on cabi robot
2- Using the IM Console, Delete wasp and cabi probes on cabi robot
3- On the file system of the cabi robot, delete these folders:
Restart cabi robot (Nimsoft service)
4- Run the Oracle script to drop cabi tables in Oracle as the UIM database user(schema). Please see file attachment.
5- Deploy the cabi probe to the cabi robot.
6- Monitor cabi robot - cabi log (takes a few minutes for the probe to show up).
A successful deployment will show something like the following in the log file:
Mar 07 12:38:52:564 [main, cabi] changing probe state
from 'INITIALIZING' to 'INSTALLING_CABI'
Mar 07 12:38:52:565 [main, cabi] extracting cabi installer ...
7- Monitor the cabi log:
Mar 07 12:46:32:929 [main, cabi]
****************[ Starting ]****************
Mar 07 12:46:32:929 [main, cabi] 3.2.0
Mar 07 12:50:19:378 [main, cabi] changing probe state from
'INSTALLING_CABI' to 'STARTING_WASP'
Mar 07 12:50:19:378 [main, cabi] activating wasp...
Mar 07 12:50:19:385 [main, cabi] waiting for wasp to start...
10- Login to cabi directly. For example:
superuser / superuser
11- Deploy uim_core_dashboards and other uim_###_dashboards to the cabi robot.
12- Deploy ump_cabi 3.20 to UMP robot.
Monitor UMP wasp for errors Wasp will take a few minutes to restart.