Troubleshooting CA CMDB and CA Configuration Automation Integration

This topic contains the following information:
casm172
This topic contains the following information:
Verify that the 
CA Configuration Automation
 Connector Installed Successfully
Symptom:
I want to verify that the 
CA Configuration Automation
 Connector started properly.
Solution:
Follow these steps:
  1. Check if there are any errors in the Catalyst_CCAConnector_InstallDebug.log file or CatalystInstallDebug.log file.
    These files are located in the %TEMP% directory.
  2. If either of the log files has errors, open a support issue.
  3. If there are no errors in either of the log file, complete the following steps:
    1. Open the CA Catalyst Server Registry UI using the following URL:
      https://<registryserver:port>/registry/carbon/admin/login.jsp
    2. Log in to the CA Catalyst Registry UI and browse to the following directory:
      \topology\physical\<<ACM>_Connector NODE>
    3. Check if connector-modules.xml and startup.properties files are present in the directory.
    4. If either connector-modules.xml or startup.properties file is missing from the directory, then the 
      CA Configuration Automation
       Connector installation has failed.
      • Uninstall and reinstall the 
        CA Configuration Automation
         Connector.
 
Verify that the 
CA Configuration Automation
 Connector Started Properly
Symptom:
I want to verify that the 
CA Configuration Automation
 Connector started properly.
Solution:
Follow these steps:
  1. Open the CA Catalyst Admin UI using the following URL:
    http://<CA_Catalyst_Server>:<port>/adminui
  2. Log in to the CA Catalyst Admin UI.
  3. Click 
    CA Configuration Automation
     Container node from the left panel.
    The 
    CA Configuration Automation
     Container node is expanded to display the 
    CA Configuration Automation
     Connector and status of the 
    CA Configuration Automation
     Connector.
    • If the status of the 
      CA Configuration Automation
       Connector is RUNNING, then the 
      CA Configuration Automation
       Connector has started properly.
    If you have just started the
    CA Configuration Automation
    Connector, wait for the
    CA Configuration Automation
    Connector nodes to move to the Running state before you perform any operation.
cca.log File Displays Exception Traces
Symptom:
The cca.log file shows errors with exception traces.
Solution:
Review and identify a resolution for the exceptions that appear in the cca.log file. The following possible exceptions may appear in the cca.log file:
CA Configuration Automation
 Server Connection Exception
Complete the following steps to remove the 
CA Configuration Automation
 Server Connection Exception found in the cca.log file:
  1. Check if the 
    CA Configuration Automation
     server is online and can be pinged from the 
    CA Configuration Automation
     Connector Server.
  2. Check if there is any firewall that is blocking access to the necessary 
    CA Configuration Automation
     server port from the 
    CA Configuration Automation
     Connector server.
    If you have restarted the
    CA Configuration Automation
    server while starting the
    CA Configuration Automation
    Connector, restart the CA Catalyst container service on the
    CA Configuration Automation
    Connector server.
  3. If the password of the 
    CA Configuration Automation
     user has changed since the installation of the 
    CA Configuration Automation
     Connector, update the password parameter in the CCAConnector.xml file from the CA Catalyst server Registry UI. Complete the following steps:
    1. Go to the following directory:
      <ROSE>_HOME\ tools\encrypt
      Ensure that java.exe in present in the path.
    2. Run encrypter.bat <New Password> command and copy the encrypted string output from the command.
    3. Open the following URL:
      https://<registryserver:port>/registry/carbon/admin/login.jsp
    4. Browse to the following directory:
      \topology\physical\<Configuration_Automation_Connector_Server>\modules\configuration\CCAConnector.xml
    5. Click Edit as Text.
    6. Replace the value for db.password with the value copied from the encryptor utility.
    7. Click Save Content.
    8. Restart the CA Catalyst Container service and verify it again.
Database Exception
Complete the following steps to remove the Database Exception found in the cca.log file:
  1. Check if the database server is online and can be pinged from the 
    CA Configuration Automation
     Connector server.
  2. Check if there is any firewall that is blocking access to the necessary database ports from the 
    CA Configuration Automation
     Connector server.
  3. If the DB password has changed since the installation of the 
    CA Configuration Automation
     Connector, update the db.password parameter in the CCAConnector.xml file from the CA Catalyst server Registry UI. Complete the following steps:
    1. Go to the following directory:
      CATALYST_HOME\ tools\encrypt
      Ensure that java.exe in present in the path.
    2. Run encrypter.bat <New Password> command and copy the encrypted string output from the command.
    3. Open the following URL:
      https://<registryserver:port>/registry/carbon/admin/login.jsp
    4. Browse to the following directory:
      \topology\physical\<CA_Configuration_Automation_Connector_Server>\modules\configuration\CCAConnector.xml
    5. Click Edit as Text.
    6. Replace the value for db.password with the value copied from the encryptor utility.
    7. Click Save Content.
    8. Restart the CA Catalyst Container service and verify it again.
JVM Port Binding Exception
Complete the following steps to remove the JVM Port Binding Exception found in the cca.log file:
  1. Check if any process is using the port that is used for the notification_listen_port parameter during the 
    CA Configuration Automation
     Connector installation.
  2. If a port conflict exists after the installation, update the parameter in the CCAConnector.xml file from the CA Catalyst server Registry UI. Complete the following steps:
    1. Open the following URL:
      https://<registryserver:port>/registry/carbon/admin/login.jsp
    2. Browse to the following directory:
      \topology\physical\<CA_Configuration_Automation_Connector_Server>\modules\configuration\CCAConnector.xml
    3. Click Edit as Text.
    4. Replace the value of the notification_listen_port with the value that does not conflict with other ports on the 
      CA Configuration Automation
       server.
    5. Click Save Content.
    6. Restart the CA Catalyst Container service and verify it again.
Verify that the 
CA Configuration Automation
 Connector Sent Data to the CA Catalyst Server Successfully
Symptom:
I want to verify that the 
CA Configuration Automation
 Connector sent data to the CA Catalyst Server successfully.
Solution:
Follow these steps:
  1. Open the Catalyst USM web view using the following URL:
    http://catalystserver:8080/ca-rest/browse/type?mdr=all
  2. Select CMDB-View from Data Source and check if the CIs are listed on the page.
  3. If the CIs are not listed in the CMDB-View, complete the following steps:
    1. Ensure that the Catalyst Container Service of the 
      CA Configuration Automation
       Connector is restarted when you started the 
      CA Configuration Automation
       server.
    2. Check if the time settings on the CA Catalyst server and the 
      CA Configuration Automation
       Connector server nodes are same to avoid connectivity issues.
    3. If you used the Catalyst Job to push the data from 
      CA Configuration Automation
       Connector, verify completion of the Catalyst Job. This verification is applicable for the Management Profile based integration. If the Catalyst Job is complete, the log view on the 
      CA Configuration Automation
       server displays the Job started and Job finished messages.
    4. Match the Check Sum Table with the projections of the 
      CA Configuration Automation
       Connector.
Match the Check Sum Table
Match the Check Sum table with the projections of the 
CA Configuration Automation
 Connector. The CA Catalyst Persistence Store maintains the projections of the 
CA Configuration Automation
 Connector for every CI sent to the CA Catalyst server.
Follow these steps:
 
  1. Run queries to find the failed CIs.
    You must adapt the queries with the corresponding database names, passwords, and so on. The Database may also need to configure cross computer DB access for
    CA Configuration Automation
    and CA Catalyst databases.
    • Use the following query in SQL to identify the failed CIs:
      select ci_id = CASE CHARINDEX( '|', ci_typ)
      WHEN '0' THEN ci_id
      ELSE (ci_id + substring( ci_typ, CHARINDEX( '|', ci_typ) + 1, len(ci_typ)))
      END collate sql_latin1_general_cp1_ci_as from acm_catlst_ci_cksum
      EXCEPT
      select c_mdrelementid from [catalystdb].[dbo].t_ci_detail where c_mdrproduct = 'CA:00033'
    • Use the following query in ORACLE to identify the failed CIs:
      CREATE PUBLIC DATABASE LINK catalystdb CONNECT TO catalystadmin IDENTIFIED BY <Password> USING '//<DBServer>/<DB SID>';
      select CASE instr( ci_typ, '|')
      HEN 0 THEN cast( ci_id as NVARCHAR2(36) )
      ELSE concat( cast( ci_id as NVARCHAR2(36) ) , substr( ci_typ, instr( ci_typ, '|') + 1, length(ci_typ)))
      END as c_mdrelementid
      from acm_catlst_ci_cksum
      minus
      select c_mdrelementid from t_ci_detail@catalystdb where c_mdrproduct = 'CA:00033'
  2. Check the invalidCIs.log file from the CATALYST_HOME\container\data\log directory.
    For each CI ID output that is received from the query, there exists a corresponding dump for the CI in the
    invalidCIs.log file.
    • If either the invalidCIs.log file is empty or the CI ID is not present in the file, then the CI synchronization from 
      CA Configuration Automation
       Connector to the CA Catalyst server is still in progress.
      The synchronization and reconciliation activities on the CA Catalyst server are not instantaneous and results in the CIs to take time to get across to CMDB.
Failed to Select the Items to Synchronize Between CA Configuration Automation and CMDB
Symptom:
I am unable to choose the items to synchronize between CA Configuration Automation and CMDB. In the old CA Configuration Automation or CMDB CA Business Intelligence-boxed integration I could choose the CI types.
Solution:
A combination of the attribute profile and Catalyst Job or management profile helps you filter data. This filtering mechanism has no similarity with the previous CA Business Intelligence integration where the filter was using CI types.