When trying to switch from CA Service Desk Manager (CA SDM) conventional configuration to Advanced Availability, pdm_configure run on a Secondary Server does not allow to select the database details screen or click Next to proceed.

Document ID : KB000029803
Last Modified Date : 14/02/2018
Show Technical Document Details

DESCRIPTION

When trying to switch from CA Service Desk Manager (CA SDM) conventional configuration to Advanced Availability,  pdm_configure run on a Secondary Server does not allow to select the database details screen or click Next to proceed.

Please refer to screenshot below - clicking on NEXT after selecting the database will not do anything.

          SQL Server

1.jpg

Oracle

2.jpg

In addition, an exception is thrown into the NX_ROOT/log/configure.log after clicking on Next on the Select Database window

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
            at com.ca.ServicePlus.configui.wizard.PreDatabasePage.validatePage(PreDatabasePage.java:157)
            at com.ca.ServicePlus.wizard.Wizard.next(Wizard.java:652)
            at com.ca.ServicePlus.wizard.Wizard.actionPerformed(Wizard.java:452)
            at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
            at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
            at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
            at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
            at java.awt.Component.processMouseEvent(Unknown Source)
            at javax.swing.JComponent.processMouseEvent(Unknown Source)
            at java.awt.Component.processEvent(Unknown Source)
            at java.awt.Container.processEvent(Unknown Source)
            at java.awt.Component.dispatchEventImpl(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
            at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
            at java.awt.Container.dispatchEventImpl(Unknown Source)
            at java.awt.Window.dispatchEventImpl(Unknown Source)
            at java.awt.Component.dispatchEvent(Unknown Source)
            at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
            at java.awt.EventQueue.access$200(Unknown Source)
            at java.awt.EventQueue$3.run(Unknown Source)
            at java.awt.EventQueue$3.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.awt.EventQueue$4.run(Unknown Source)
            at java.awt.EventQueue$4.run(Unknown Source)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
            at java.awt.EventQueue.dispatchEvent(Unknown Source)
            at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
            at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 

 In a good case, one would see an expanded left pane with Oracle/SQL Server Database Config and other items that should appear

 

3.jpg

 

NOTE: The problem is only see on CA SDM Secondary servers and NOT on the CA SDM Primary server.

 

 SOLUTION

1.  Locate the NX_ROOT/site/config.properties file and open with a text editor

2.  Locate an entry that looks like:   database.database_provider=

a.  If Oracle is the backend MDB database, modify that entry to look like:    database.database_provider=Oracle

b.  if SQL Server is the backend MDBdatabase, modify that entry to look like:    database.database_provider=SQL

3.  Save the changes to the file

4.  Retry CA SDM Configuration (pdm_configure)

This time the left pane of the CA SDM configuration screen shows properly and lets you proceed further with selection of the database.