CABI Login url displays 'Page Not found' after moving the UIM database to a new MSSQL Server

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

UIM Database was moved to a new MS SQL Server with a newer SQL version but now CABI Login url  displays 'Page Not found'

Also seeing a secondary issue where OC Report fails with below error

There may be a couple scenarios that you can run into. You may only run into the first scenario:

Scenario 1

Error in jasperserver.log

org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': java.sql.SQLNonTransientConnectionException: [TibcoSoftware][SQLServer JDBC Driver][SQLServer]Cannot open database "CA_UIM" requested by the login. The login failed. [See nested exception: java.sql.SQLNonTransientConnectionException: [TibcoSoftware][SQLServer JDBC Driver][SQLServer]Cannot open database "CA_UIM" requested by the login. The login failed.]

Error in wasp.log

[/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection

Scenario 2

Error in wasp.log, note that jasperserver.log was error free in this scenario

INFO  [Catalina-utility-1, org.apache.catalina.core.ContainerBase.[wasp-engine].[localhost].[/]] No Spring WebApplicationInitializer types detected on classpath
ERROR [Catalina-utility-1, org.apache.catalina.startup.ContextConfig] processContextConfig() Parse error in context.xml for [/cabijs]
ERROR [Catalina-utility-1, org.apache.catalina.startup.ContextConfig] org.xml.sax.SAXParseException; systemId: file:/X:/UIM/probes/service/wasp/webapps/cabijs/META-INF/context.xml; lineNumber: 46; columnNumber: 307; The reference to entity "nQ" must end with the ';' delimiter.

Environment

Any UIM and CABI version

Cause

MS SQL Server Name, User, Password and IP were changed and context.xml was not updated accordingly

Resolution

Resolution for Scenario 1  (The context.xml file was not updated with the new SQL Server information)

1. Deactivate wasp and cabi probe 
2. Backup the X:\Nimsoft\probes\service\wasp\webapps\cabijs\META-INF\context.xml file3. Update the context.xml url parameter with the new database server properties. Update the password and user parameters if they were changed, save the changes.

Note: Make sure that password does not include special characters as as, semicolon (;), ampersand, (&) or double quotes, (") to avoid CABI jdbc connectivity issues with the database

3. Change the url parameter as followed: (remove tibcosoftware):
From:
url=jdbc:tibcosoftware:sqlserver://databaserver:1433;databaseName=CA_UIM

To:
url=jdbc:sqlserver://databaserver:1433;databaseName=CA_UIM

4. Activate wasp and cabi probe
5.  After cabi and wasp are active, login to cabi directly using superuser with superuser (default) as the password 
http://<ipforcabi>:<port>/cabijs/login.html 
or
http://<fqdnforcabi>:<port>/cabijs/login.html 

6. In the Home page click on Data Sources

7. The UIM Datasource and UIM JNDI Datasource will display

8. Hover the mouse over the UIM Datasource, right click and select edit. 

Update with new SQL Server properties, Click on Test Connection to validate connectivity and Save changes

 

 

9. Hover the mouse over the  UIM JNDI Datasource, right click and select edit. 

Click on Test Connection to validate connectivity and click on Cancel

Resolution for Scenario 2 (The database user password configured in the data_engine probe includes special characters such as ampersand (&) or double quotes (") and context file on the CABI robot was updated with the password in plain text.

Option 1. Update the X:\Nimsoft\probes\service\wasp\webapps\cabijs\META-INF\context.xml file on the cabi robot with the password in encrypted format per steps in Changing the JNDI Password for CABI Server

Option 2: Change the database user id's password to not include ampersand (&) or double quotes ("). 

**To change the password on SQL Server users, use SQL Server Management Studio (SSMS)

**To change the password on Domain service users, use Active Directory User and Computers snap-in