I had to change the password for my database user for UIM

Article Id: 103528
Status: Published
Updated On: 30-01-2020 12:42
Products:
CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) NIMSOFT PROBES
Issue/Introduction:



I had to change the User / Password  for the connection string to the back end SQL server that is used by UIM.
what changes need to be done on the UIM side to put this change in place?
 

Environment:

UIM 9.X and earlier
UMP 9.X and earlier
UR 8.51 and earlier
CABI 3.X and earlier

Resolution:

NOTE: Stop the robot service on CABI robot BEFORE changing the database user password for oracle or the account could become locked.

Primary HUB / Secondary HA HUB
For the primary hub update the data_engine probe and restart the Robot watcher service.
This will cause all other probes on the primary hub to get the new connection string and use it.

Primary UMP / Secondary UMP
After the primary hub is update you should just need to restart the robot watcher service on the ump to have the new connection string take affect.
On rare occasions you will need to use raw edit on the UMP wasp to blank out the connection key and then restart. this will force the wasp to pull
new information from the data_engine.

If you have created any custom JDBC dashboard connections to the same database you will need to update these as well.

Unified Reporter
You will need to run the UR installer again to update the user / password
please see the UR KB article before starting to deal with the license issue when installing the repository.
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=8573


CABI - Bundled
NOTE: Manual step reqired for oracle backend

You must manually update the <nimsoft>/probes/service/wasp/webapps/cabijs/META-INF/context.xml file:
Example:



data source for jaspersoft tables:


<Resource accessToUnderlyingConnectionAllowed="true" auth="Container" driverClassName="tibcosoftware.jdbc.oracle.OracleDriver" factory="com.jaspersoft.jasperserver.tomcat.jndi.JSBasicDataSourceFactory" maxActive="100" maxIdle="30" maxWait="10000" name="jdbc/jasperserver" password="ENC-1819e933d5b10edfb66ff1f4d8411047d09b4e5d2b293d9753e50dc11d3fae7d-" testOnBorrow="true" type="javax.sql.DataSource" url="jdbc:tibcosoftware:oracle://walsh04-E16645:1521;ServiceName=ORCL.ca.com" username="CA_UIM" validationQuery="SELECT 1 FROM DUAL"/>

Reset the password to the new password in clear test. It will be used and then encrypted on the next restart.


After the primary hub is update you should just need to restart the robot watcher service on the CABI robot to have the new connection string take affect.
On rare occasions you will need to use raw edit on the CABI wasp to blank out the connection key and then restart. this will force the wasp to pull
new information from the data_engine.
 
CABI -External
You will need to check the external CABI connection setup and correct.