ADA Data Source fails to bind with CA Performance Management (CAPM)

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

Description:

The ADA Data Source created in CA Performance Management (CAPM) fails to complete the bind process when configuring the ADA to CAPM integration.

Solution:

When first trying to integrate the CAPM product with the CA ADA product this issue may be encountered.

After creating the ADA Data Source in the CAPM UI, when it first tries to bind the systems together it may fail.

If it does fail we need to examine the DMService.log file on the CAPM server. That file is located in:

$CAPM_HOME/CA/PerformanceCenter/DM/logs

When examining that log, we should first look for the appearance of this type of error message in the log file:

       ERROR | pool-4-thread-13   | 2013-03-26 12:01:36,951 | com.ca.im.portal.dm.productsync.DataSourcePoller                 
        | 
       Data source Application Delivery Analysis@10.224.90.18 encountered an error while processing a sync request.  
       The problem may be in either the data source or CAPC.  The following stack trace may indicate where the problem lies.  
       You may also want to check the logs for the data source to determine if it is the cause of the problem.
       java.lang.NullPointerException
             at com.ca.im.portal.dm.productsync.DataSourceBind.migrateRoleNames(DataSourceBind.java:1023)
             at com.ca.im.portal.dm.productsync.DataSourceBind.bindRoles(DataSourceBind.java:901)
             at com.ca.im.portal.dm.productsync.DataSourceBind.processBindingTables(DataSourceBind.java:192)
             at com.ca.im.portal.dm.productsync.DataSourceBind.bind(DataSourceBind.java:102)
             at com.ca.im.portal.dm.productsync.DataSourceBindPhase.executeInternal(DataSourceBindPhase.java:55)
             at com.ca.im.portal.dm.productsync.DataSourceSyncPhase.execute(DataSourceSyncPhase.java:95)
             at com.ca.im.portal.dm.productsync.BindSyncPhaseTask.execute(BindSyncPhaseTask.java:78)
             at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:120)
             at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:113)
             at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
             at java.util.concurrent.FutureTask.run(Unknown Source)
             at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
             at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

The key parts of this message are where it references the 'migrateRoleNames' and 'bindRoles'.

This implies problems with the integration's mapping of user roles between the CA ADA and CAPM servers.

If this same error is seen, the currently known cause is that at some point prior to configuring the integration, the default roles defined in the out of the box CAPM product had been deleted and removed from the system.

Once the roles are removed, the are listed in the deleted_role_definitions tables in the CAPM DB. That is why we see the java.lang.NullPointerException in the error. In the products code, these roles being sought and expected are not there, so the query for the roles is returned with NULL values, and due to that we get an exception as seen above.

During synchronization with ADA, CAPM gathers all of the roles that ADA has and attempts to map them to its own. The CAPM/ADA roles are mapped as follows:

CA Application Delivery Analysis CA Performance Management

CA Application Delivery Analysis              CA Performance Management 
Network Engineer                              IT Engineer
Network Manager                               IT Manager
Network Operator                              IT Operator

Due to the missing CAPM roles, the migration and mapping of the roles fail. This in turn causes the synchronization process between CA ADA and CAPM, via the Data Source created against the ADA server, to fail to successfully complete.

At this time there is no simplistic method available to resolve this by recreating the default roles, short of uninstall/reinstall of the CAPM Server. There is no workaround available for this issue without uninstall/reinstall without engineering involvement.

A code change based, permanent fix for this issue, is included in the CA Performance Manager software release 2.4.1.

If this problem is encountered and the CA IM 2.4.1 release is not able to be installed to resolve it, please open a new issue with CA Performance Management Support for further assistance in determining a resolution.