Check data transfer - BMC BladeLogic Decision Support for Server Automation to BMC Atrium CMDB source dataset (BMC.BL)

Verify that the data exchange ran to pull computer systems from BMC BladeLogic Decision Support for Server Automation into BMC Atrium CMDB.

BMC Atrium Integration Engine

Data exchanges are scheduled to run periodically, and can be configured in BMC Atrium Integration Engine.

The BL_LOAD_SRVR_PROPS data exchange runs first. It triggers the BL_PULL_COMPUTERSYSTEM data exchange, which populates computer systems in BMC Atrium CMDB. When this exchange completes, it triggers other data exchanges that transfer components and relationships.

On the server running BMC Atrium Integration Engine, check the following log file:

<AtriumCore Install Dir>\aie\service\loginstanceName_aiemain.dbg

This file indicates when data exchanges started and completed, and reports issues such as the inability to connect to a database.

Search for the following strings in the log:

• Start Data Exchange BL_PULL_COMPUTERSYSTEM
• Finished processing Data Exchange BL_PULL_COMPUTERSYSTEM

Verify connectivity.

BMC Atrium Integration Engine

For issues about connecting to the BMC Server Automation database or BMC Atrium CMDB, check the aiemain.dbg file:

<AtriumCore Install Dir>\aie\service\loginstanceName_aiemain.dbg

You can also use the following procedure to verify the server names and credentials:

1. Access the AIE Console of the Atrium Integration Engine.
2. Go to the Connection Settings page and click the Test Connection(s) button.

Verify that product components are operational.

See description column for details.

BMC Atrium Integration Engine

Run the AtriumCoreMaintenanceTool and use the Health Check page feature to verify that BMC Atrium Integration Engine is operational.

BMC Atrium CMDB

Run the AtriumCoreMaintenanceTool and use the Health Check page feature to verify that BMC Atrium CMDB is operational. For more information, see "Post-installation Health Check" in the BMC Atrium Core Installation Guide, which is available here.

BMC Server Automation

Using the BMC Server Automation Console, select Configuration > Infrastructure Management. Expand the Application Servers node, and click the name of each Application Server. This displays configuration information about the Application Server.

Enable debug logs in BMC Atrium Integration Engine

BMC Atrium Integration Engine

If a data exchange runs, but encounters errors transferring some records, you can enable more verbose logging to see the details of which records receive the errors and what data is passed. Data exchange debug logs can grow large quickly, so they should be enabled only during testing.

1. Access the BMC Remedy AR System by using the following URL in a browser:
   http://<midTierServer>:<port>/arsys/forms/<ARserverName>
2. Log on.
3. Click the AIE Console link.
4. Click Data Exchange Mapping.
5. Select the data exchange that is having issues.
6. Click Open.
7. Go to the Advanced Settings page.
8. Select the checkboxes for all debug levels: API calls, SQL Statements, Record Summary, Record Details.
9. Set the Max Debug Size to a large value (such as 1048596 bytes) to minimize the number of files generated.
10. Generate the logs and search for ERR to find error numbers.
    
    Tips on interpreting AIE log entries:
    
    ORA- or SQLSERV - Errors interacting with the BMC BladeLogic Decision Support for Server Automation database
    
    3300 - 3399 - Errors given by BMC Atrium Integrator, such as issues with adapters
    
    8755, 8760 – Errors with BMC Remedy AR System plugins, requires Filter and Plugin logging
    
    90, 91, 92, 93, 94 - Connection or timeout errors to BMC Remedy AR System, which might indicate performance issues
    
    10000 or above – These errors can be caused by BMC Remedy AR System workflow. Search API/SQL, Filter, and Plugin logs to find more detail about the transaction that leads to the error.
    
    <unable to connect to db vendor> - Verify the vendor database connection and parameters
    
    <column does not exist> - Verify that the database views exist in the inventory database.
    
    For help interpreting the logs and using BMC Atrium Integration Engine diagnostics, see "BMC Atrium Integration Engine logging and debugging" in the BMC Atrium Core Troubleshooting Guide, which is available here.
    
    

Enable debug logs in BMC Remedy AR System.

BMC Remedy AR System

If appropriate, enable Filter/API/SQL/Plugin logs in BMC Remedy AR System to investigate specific errors.

To enable BMC Remedy AR System Filter, API, SQL, and Plug-In logs:

1. Access BMC Remedy AR System by using the following URL in a browser:
   http://<midTierServer>:<port>/arsys/forms/<ARserverName>
2. Log on.
3. Click the AR System Administration Console link.
4. Navigate in the tree: System > General > Server Information.
5. Select the Log Files page.
6. Select the checkboxes for API, SQL, Filter, and Plug-In. Verify each writes to a file, and note the file name and location. Select the option for Plug-In Log, and set Log Level to All. Set Maximum Log-File Size to 0 (zero) for unlimited.
7. Click Apply to enable the logs. The changes happen immediately.

Collect standard diagnostics.

BMC Atrium Integration Engine

You can use the AtriumCoreMaintenanceTool to collect environment, version, configuration, and log files into a zip file for investigation. To do this, launch the tool and click Zip All Logs. This collects the logs and configuration for BMC Atrium Integration Engine, BMC Atrium CMDB, and BMC Remedy AR System.

For more details, see "How to prepare log files for BMC Customer Support" in the BMC Atrium Core Installation Guide, which is available here.