ca configuration automation

Integrating CA Configuration Automation and CA CMDB

CA GREEN BOOKS

CA Configuration Automation

BEST PRACTICES FOR INTEGRATING CA ACM OR CA CONFIGURATION AUTOMATION AND CA CMDB

STRATEGIES FOR EXPORTING CA ACM OR CA CONFIGURATION AUTOMATION CONFIGURATION ITEMS AND MANAGING THEM IN CA CMDB

LEGAL NOTICE

This publication is based on current information and resource allocations as of its date of publication and is subject to change or withdrawal by CA at any time without notice. The information in this publication could include typographical errors or technical inaccuracies. CA may make modifications to any CA product, software program, method or procedure described in this publication at any time without notice.

Any reference in this publication to non-CA products and non-CA websites are provided for convenience only and shall not serve as CA’s endorsement of such products or websites. Your use of such products, websites, and any information regarding such products or any materials provided with such products or at such websites shall be at your own risk.

Notwithstanding anything in this publication to the contrary, this publication shall not (i) constitute product documentation or specifications under any existing or future written license agreement or services agreement relating to any CA software product, or be subject to any warranty set forth in any such written agreement; (ii) serve to affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement relating to any CA software product; or (iii) serve to amend any product documentation or specifications for any CA software product. The development, release and timing of any features or functionality described in this publication remain at CA’s sole discretion.

The information in this publication is based upon CA’s experiences with the referenced software products in a variety of development and customer environments. Past performance of the software products in such development and customer environments is not indicative of the future performance of such software products in identical, similar or different environments. CA does not warrant that the software products will operate as specifically set forth in this publication. CA will support only the referenced products in accordance with (i) the documentation and specifications provided with the referenced product, and (ii) CA’s then-current maintenance and support policy for the referenced product.

Certain information in this publication may outline CA’s general product direction. All information in this publication is for your informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness of the information. To the extent permitted by applicable law, CA provides this document “AS IS” without warranty of any kind, including, without limitation, any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, business interruption, goodwill or lost data, even if CA is expressly advised of the possibility of such damages.

COPYRIGHT LICENSE AND NOTICE:

This publication may contain sample application programming code and/or language which illustrate programming techniques on various operating systems. Notwithstanding anything to the contrary contained in this publication, such sample code does not constitute licensed products or software under any CA license or services agreement. You may copy, modify and use this sample code for the purposes of performing the installation methods and routines described in this document. These samples have not been tested. CA does not make, and you may not rely on, any promise, express or implied, of reliability, serviceability or function of the sample code.

Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respective companies. Microsoft product screen shots reprinted with permission from Microsoft Corporation.

TITLE AND PUBLICATION DATE:

CA Configuration Automation Green Book Version 3 Publication Date: May 22, 2012

ACKNOWLEDGEMENTS

Principal Author and Technical Editors

Sara Curwen

The principal author and CA would like to thank the following contributors:

■ Adnan Hafeezullah

■ John Sorensen

■ Billy Keefer

■ Richard Self

■ CA Services

■ Development

■ Product Marketing

■ QA

■ Support

■ Engineering Services

■ Technical Sales

■ Technical Information

Third-Party Acknowledgements

Microsoft® SQL Server®, Microsoft® Exchange Server, Microsoft® Windows®, Microsoft® Internet

Explorer®, Microsoft® System Center Operations Manager and Microsoft® Visual C++® are

registered trademarks of Microsoft Corporation in the United States and other countries.

CA PRODUCT REFERENCES

This document references the following CA products:

■ CA Configuration Automation (formerly CA Application Configuration Manager)

■ CA Business Intelligence

■ CA Embedded Entitlements Manager (CA EEM)

FEEDBACK

Please email us at [email protected] to share your feedback on this publication. Please

include the title of this publication in the subject of your email response. For technical assistance

with a CA product, please contact CA Support at http://ca.com/support. For assistance with

support specific to Japanese operating systems, please contact CA at http://www.casupport.jp.

http://www.ca.com/greenbooks

http://www.ca.com/support

http://www.casupport.jp/

http://www.casupport.jp/

CA Configuration Automation 5

Contents Chapter 1: Integration Overview 7

The Integration.............................................................................................................................................. 8 Prerequisites ................................................................................................................................................. 8

Chapter 2: Configuring the Integration 9 Planning the Integration ............................................................................................................................... 9 Implementing the Integration ..................................................................................................................... 10

Create an MDR ........................................................................................................................................ 11 Configure the GRLoader Environment on the BusinessObjects XI Server ............................................... 14 GRLoader Arguments .............................................................................................................................. 16 Install the Integration Patch .................................................................................................................... 18 Replace the Existing CAFApp Directory (Post-installation Task) .............................................................. 33 Configure Database Connection in BusinessObjects Designer ................................................................ 34

Upgrading to CA Configuration Automation r12.5 ...................................................................................... 40

Chapter 3: Working with the Integration 41 Schedule the BOXI_GRLoader ..................................................................................................................... 41

Receiving Import Results by Email .......................................................................................................... 45 Schedule the CA CMDB Export Report ........................................................................................................ 46 Schedule Multiple Report Instances ........................................................................................................... 52 Execute GRLoader Manually ....................................................................................................................... 54

Chapter 4: Viewing the Import Results 55 View CIs and Relationships in the Service Desk Web Client ........................................................................ 55 View CIs and Relationships in the CMDB Visualizer .................................................................................... 58

Chapter 5: Customizing the Integration 61 Create a Backup .......................................................................................................................................... 61 Modify Attribute Mappings ......................................................................................................................... 62 Modify Class Mappings ............................................................................................................................... 63 Modify Relationship Mappings ................................................................................................................... 64

Chapter 6: Troubleshooting 65 Running Patch Installers in Debug Mode .................................................................................................... 65 View the GRLoader Log File......................................................................................................................... 65 Installing the Integration Patch Directly from the DVD ............................................................................... 68 Using Java JRE v1.6.0_29 Causes Patch Installer to Hang............................................................................ 68

Appendix A: Relationships and Mappings 69 Supported Network Discovery Gateway (NDG) Relationships .................................................................... 69 Predefined CA ACM to CA CMDB Mappings ............................................................................................... 71

Attribute Mappings ................................................................................................................................. 71 Class Mappings ........................................................................................................................................ 74 Relationship Mappings ............................................................................................................................ 78

6 Contents


Chapter 1: Integration Overview CA CMDB enables you to maintain a consistent set of managed information that make up

configuration items (CIs) that exist in your environment. These CIs and their relationships may be

obtained from a variety of sources (including other software products) and imported into CA

CMDB which acts as a common repository. Having a common collection of configuration items

provides you with the ability to determine the impact of a change in the environment before the

changes goes into effect.

CA Configuration Automation (formerly CA Application Configuration Manager or CA ACM) is a

standards-based suite of products that enables you manage your enterprise's distributed

hardware and software services from a centralized, browser-based user interface. CA

Configuration Automation provides an application-level best practices platform for managing

configuration, configuration change, and rule compliance. You can discover and manage

components in your enterprise at the network, server, service, and software level.

CA Configuration Automation automates the configuration management of complex and

distributed applications to ensure security, performance, availability, and compliance by

implementing the following:

■ Infrastructure Discovery—Discovers infrastructure components including servers, software

and applications with agentless and agent-based discovery mechanisms to extract granular

configuration settings from applications running on discovered components.

■ Application Dependency Mapping—Visually depicts relationships and dependencies

between discovered components and IT services in interactive graphical topology maps to

help improve service availability and change impact analysis.

■ Change Detection—Captures and saves configurations as point-in-time copy or snapshot

that can be stored as Gold Standard and compared with future snapshots to detect changes

for troubleshooting, record keeping, or migration planning.

■ Configuration Compliance Audits and Remediation—Ensures that servers and applications

meet internal IT configuration or industry benchmarks based on CIS benchmarks for

supporting security configuration mandates such as PCI and DISA. Policy compliance rules

can be automatically enforced through remediation.

The Integration

8 Chapter 1: Integration Overview

■ Dashboards and Visualization—Displays graphical summary information about servers,

services, operations such as rule compliance and virtualized components. Visualization

displays the relationships between network elements. Both views include predefined

contents, graphs, and templates.

■ Reporting—Provides interactive reporting with CA Business Intelligence which includes more

than 80 predefined reports.

The Integration

The CA Configuration Automation/CA CMDB integration allows CIs and their relationships from

CA Configuration Automation to be imported into CA CMDB. At the core of the integration is

BusinessObjects XI's reporting functionality provided by CA Business Intelligence. Using

BusinessObjects XI from within CA Configuration Automation, you execute a CA CMDB Export

report to generate an XML file containing the desired CA Configuration Automation CIs and CI

relationships. CA CMDB includes a utility called General Resource Loader (GRLoader) that is used

to import the CIs and relationships from the XML file. This import action may be automated in

BusinessObjects XI or run manually.

Prerequisites

The integration supports the following product versions:

■ CA Configuration Automation r12.5 (Build 12.5.8)

■ CA ACM r12.0.2 (also known as r12 SP2 or Build 12.0.26.x)

Note: For versions prior to CA ACM r12.0.26.x, please contact CA Support.

■ CA Service Desk Manager (SDM) r12.5 with CMDB

■ CA Business Intelligence r3.2/BusinessObjects XI

The integration steps documented in this Green Book assume that CA Configuration Automation,

CA CMDB and BusinessObjects XI are installed and running. Additionally, it is assumed that

Network and Component Discoveries were executed to populate CA Configuration Automation

with configuration data.


Chapter 2: Configuring the Integration

Planning the Integration

When planning the integration deployment, it is important to answer the following two

questions:

■ Are BusinessObjects XI and CA CMDB installed on the same machine?

■ Will you manually run the GRLoader utility to import the CIs or will you automate the

process via BusinessObjects XI?

The answers to these questions determine the appropriate process for implementing the

integration.

The following diagram describes the process flow for configuring the integration.

Implementing the Integration

10 Chapter 2: Configuring the Integration


The CA Configuration Automation/CMDB integration patch RO28655 is available from the CA

Support Online Download Center. It is accessible from the Product pages for CA Application

Configuration Manager and CA Service Desk Manager via the Solution & Patches link.

The patch can be applied to CA ACM r12.0.26.x (SP2). For earlier versions of CA ACM, please

contact CA Support. The patch includes the following files:

■ acm-cmdb.exe: Integration patch to be installed on the BusinessObjects XI server (Windows

only)

■ CA_CMDB_r12.5_and_CA_ACM_r12_Integration_Guide.pdf

No patches are required for the ACM Server or for CA CMDB.

The patch is distributed as a CAZ file. To unzip this file, you must use the cazipxp utility as follows:

cazipxp –u <patchName>.CAZ

The cazipzp utility is also available from the CA Support Online Download Center.

https://support.ca.com/





Create an MDR

You must manually create an entry for CA Configuration Automation in the CA CMDB

Management Data Repository (MDR) list prior to importing CIs from CA Configuration

Automation.

To create an entry for CA Configuration Automation in the CA CMDB Management Data

Repository (MDR)

1. Open the CA Service Desk Web Client.

2. Select the Administration tab.

3. In the left hand pane, click CA CMDB, MDR Management, MDR List.

4. In the right hand pane, click Create New.

5. Complete the following fields, and then click Save:

■ Button Name—Enter a button label (for example, ACM-R12 or CCA-R12.5).

■ MDR Name—Enter the host name of the ACM Server or the CCA Server.

■ MDR Class—Enter ACM r12 or CCA 12.5 depending on your product version. The MDR

Class must be named ACM r12 or CCA 12.5.

■ Active—Select Active from the drop-down list.

■ Owner—Enter a user name (for example, CMDBAdmin or ServiceDesk).



■ Description—Enter a description about the server.

■ Hostname—Enter the hostname of the ACM Server or the CCA Server.

■ Port—Enter the port number of the ACM Server or the CCA Server (default port is 8080).

■ Path—Enter caacm/ACMUI.html for CA ACM r12 SP2 or index.html for CA Configuration

Automation r12.5.

■ Parameters—Enter type=ci{federated_asset_id}.

■ URL to launch in Context—Enter http://{hostname}:{port}/{path}?{parameters}



The MDR provides launch in-context capability back to CA Configuration Automation or

CA ACM from CA CMDB (as shown in the following graphic) if the URL for the CA ACM or

CA Configuration Automation UI is specified in the MDR.



Configure the GRLoader Environment on the BusinessObjects XI Server

If CA CMDB and BusinessObjects XI exist on different computers and you want to automate the

CI import process, you must configure the GRLoader environment on the BusinessObjects XI

server prior to scheduling the CA CMDB Export report and BOXI_GRLoader program.

To configure the GRLoader environment on the BusinessObjects XI server

1. Install Java Runtime Environment (JRE) version 6.0 or higher

2. From your CA CMDB server, copy the contents of the %NX_ROOT%\java\lib directory to a

directory on the BusinessObjects XI server. The remainder of this procedure refers to this

directory as %ROOT%.

Note: %NX_ROOT% refers to the installation path for CA Service Desk Manager. For

example:

C:\Program Files\CA\Service Desk Manager.

3. Create a %ROOT%\log directory.

For example: C:\GRLoader\log

4. Create a %ROOT%\site\cfg directory.

For example: C:\GRLoader\site\cfg

5. Create a file named NX.ENV in the %ROOT% directory



6. Open the file with a text editor and add the following line:

@NX_LOG=path_to the_GRLoader_log_files

For example: @NX_LOG=C:\GRLoader\log

7. Save and close the file.



GRLoader Arguments

During the installation of the Integration Patch (described in the next section), you are prompted

to enter arguments for the GRLoader utility. The arguments for GRLoader may be specified using

one of following two methods:

■ Create a configuration file specifying all the necessary GRLoader parameters. Using this

method, when prompted for the GRLoader arguments, use the -cfg flag followed by

configuration file name using its absolute path, for example: -cfg c:\conf.txt.

The following fields are required in the configuration file:

grloader.userid=<username>

Specifies a defined CA CMDB username.

grloader.password=<password>

Specifies the password for the CA CMDB user.

grloader.server=http://<hostname>:CA Portal

Specifies the hostname and port for your CA CMDB server.

grloader.inputfile=<path_to_XML_file_containing_CCA_CIs>

Specifies the path to the XML file containing the CA ACM or CA Configuration

Automation CIs, for example: c:\XMLFiles\cca2cmdb.xml.

grloader.nxroot=<path_to_directory_containing_copied_GRLoader_files>

Specifies the path to the directory containing the copied GRLoader files, for example:

c:\GRLoader.

gloader.allowupdate=yes

grloader.allowinsert=yes

grloader.overwriteerrorxml=yes



■ Explicitly enter the GRLoader command-line options when prompted for the GRLoader

arguments. The minimum arguments required to execute GRLoader from BusinessObjects XI

are as follows:

-s

Specifies the Server URL including port (http://hostname:port).

-u

Specifies the CA CMDB username.

-p

Specifies the password for the CA CMDB user.

-i

Specifies the input XML file.

-n

Specifies that new CIs can be created.

-a

Specifies that updates to CIs can be made.

-N

Specifies the path to NX.ENV (directory containing copied GRLoader files).

-E

Specifies that overwriting of the Error XML file is allowed if it exists.



The following example shows how the parameter list would look on the command line, or when

prompted for the GRLoader arguments in the Integration Patch installation wizard:

-s http://<hostname>:CA Portal -u <username> -p <password> -i

<path_to_XML_file_containing_CCA_CIs> -n -a -N

<path_to_directory_containing_copied_GRLoader_files> -E

Example:

-s http://cmdb:8080 –u ServiceDesk -p Password -i c:\XMLFiles\cca2cmdb.xml -n

-a -N c:\GRLoader -E

Install the Integration Patch

The integration patch (acm-cmdb.exe or cca-cmdb.exe, depending upon whether you are using

ACM r12 SP2 or CCA r12.5) must be applied to your CA Business Intelligence /BusinessObjects XI

server. The patch is only available for Windows as CA currently only supports BusinessObjects XI

on Windows. The patch installer requires Java Runtime Environment (JRE) 1.5 or higher.

Note: Java JRE v1.6 Update 29 (1.6.0_29) is not supported due to a known database connection

issue with this version.

Ensure that you are able to access the ACM Database or CCA Database from the BusinessObjects

XI server using the appropriate database client software (Oracle or Microsoft SQL Server) or

ODBC datasource (Microsoft SQL Server). For Oracle, you must configure the TNS listener to have

an entry named “ACM” which points to the ACM Database or “CCA” which points to the CCA

Database. BusinessObjects XI uses this name as the datasource name to connect to the Oracle

database. If you do not perform these steps, the CA CMDB Export report execution will fail on

Oracle.



The integration patch performs the following tasks on your BusinessObjects XI server:

■ Imports the CA_ACM_CMDB universe (CA ACM r12 SP2) or the CCA_CMDB universe (CA

Configuration Automation r12.5)

■ Imports the CA CMDB Export report and the BusinessObjects XI-GRLoader program (wrapper

for GRLoader) and places them in one of the following folders:

■ CA ACM r12 SP2: CA Reports\CA ACM to CMDB\

■ CA Configuration Automation r12.5: CA Reports\CCA to CMDB\

■ Modifies the oledb.sbo file (if using an OLE DB)

■ Deploys the Client Access Framework (CAF) Page WAR file, CAFApp.war

■ Configures the imported CMC Program Object’s rights

■ Creates a Schedule Event: Successful_Report_XML_Event

■ Configures the destination settings (email, ftp, and file system) for the

CrystalReportJobServer, ProgramJobServer, and DestinationJobServer

Note: The destination settings will only be configured if you supply the requested

information during the integration patch installation.

■ Configures the GRLoader settings for the imported BOXI_GRLoader program

Note: The GRLoader settings will only be configured if you supply the requested information

during the integration patch installation.

To install the integration patch (CA ACM r12 SP2)

1. On your BusinessObjects XI server, from the directory where you extracted the patch,

double-click acm-cmdb.exe.



The Introduction screen appears.

2. Click Next.

The ACM Database Server screen appears.



3. Enter the ACM database server connection information, including database type (SQL Server

or Oracle), and then click Next.

The ACM Database Configuration screen appears.

4. Enter the name of the ACM database and the database user credentials, then click Next.

The Choose CABI Folder screen appears.



5. Specify the location of the CA Business Intelligence/BusinessObjects XI installation, then click

Next.

Note: The typical folder location when using a standard installation is C:\Program

Files\CA\SC\CommonReporting3.

The Choose CABI webapps Folder screen appears.

6. Specify the location of the CA Business Intelligence/BusinessObjects XI webapps folder, then

click Next.


Files\CA\SC\CommonReporting3\Tomcat55\webapps.

The Configuring CABI 3.0 screen appears.



7. Enter the connection details and credentials for CA Business Intelligence/BusinessObjects XI.

Click Next.

Note: The specified System user should be a local or domain user that is a member of the

administrators group on the BusinessObjects XI server.

The Configure Email screen appears.

8. Configure the email settings for the BusinessObjects XI job servers, then click Next.

Note: The BOXI_GRLoader program is typically configured to send an email notification on

completion. Although listed as optional, it is recommended to configure these settings at

installation time if email notifications are wanted. However, it is possible to manually

configure them post-installation. Instructions are included in the Integration Guide that is

packaged with the patch.

The Configure FTP screen appears.



9. Configure the FTP settings for the BusinessObjects XI job servers, then click Next.

Note: Although listed as optional, it is recommended to configure these settings at

installation time if you plan to FTP files to another server. However, it is possible to manually

configure the FTP settings post-installation. Instructions are included in the Integration

Guide that is packaged with the patch.

The Configure File System screen appears.

10. Configure the destination directory where the XML file generated by the CA CMDB Export

report will be stored, and the name for the XML file, and then click Next.

The information is set for the BusinessObjects XI job servers.


installation time in order to save the generated XML file to the file system. However, it is

possible to manually configure these settings post-installation. Instructions are included in

the Integration Guide that is packaged with the patch.



The Configure CABI_GRLoader screen appears.

The following GRLoader arguments were used in the this example:

-s http://cmdb:8080 -u ServiceDesk –p Password -i C:\ACM-CMDB\acm2cmdb.xml -n -a -N

C:\GRLoader -E

11. Configure the following settings for GRLoader, then click Next:

■ Arguments—Parameters needed to execute GRLoader from BusinessObjects XI

Note: Additional information on the GRLoader arguments can be found in GRLoader

Arguments (see page 16).

■ Working Directory—Directory containing the copied GRLoader files


installation time. You can also manually configure these settings post-installation as

described in the Integration Guide that is packaged with the patch.

The Pre-Installation Summary screen appears.



12. Review the summary information, then click Install.

13. Click Done when the installation is complete.

To install the integration patch (CCA r12.5)

1. Log on to your BusinessObjects XI server and navigate to the \CCA\CMDB\Windows

directory on the CA Configuration Automation r12.5 installation media, and then

double-click cca-cmdb.exe.



The Introduction screen appears.

2. Click Next.

The CCA Database Server screen appears.



3. Enter the CCA Database server connection information, including database type (SQL Server

or Oracle), and then click Next.

The CCA Database Configuration screen appears.

4. Enter the name of the CCA Database and the database user credentials, then click Next.

The Choose CABI Folder screen appears.



5. Specify the location of the CA Business Intelligence/BusinessObjects XI installation, then click

Next.


Files\CA\SC\CommonReporting3.

The Choose CABI webapps Folder screen appears.

6. Specify the location of the CA Business Intelligence/BusinessObjects XI webapps folder, then

click Next.


Files\CA\SC\CommonReporting3\Tomcat55\webapps.

The Configuring CABI 3.0 screen appears.



7. Enter the connection details and credentials for CA Business Intelligence/BusinessObjects XI.

Click Next.

Note: The specified System user should be a local or domain user that is a member of the

administrators group on the BusinessObjects XI server.

The Configure Email screen appears.

8. Configure the email settings for the BusinessObjects XI job servers, then click Next.

Note: The BOXI_GRLoader program is typically configured to send an email notification on

completion. Although listed as optional, it is recommended to configure these settings at

installation time if email notifications are wanted. However, it is possible to manually

configure them post-installation. Instructions are included in the Integration Guide that is

packaged with the patch.

The Configure FTP screen appears.



9. Configure the FTP settings for the BusinessObjects XI job servers, then click Next.


installation time if you plan to FTP files to another server. However, it is possible to manually

configure the FTP settings post-installation. Instructions are included in the Integration

Guide that is packaged with the patch.

The Configure File System screen appears.

10. Configure the destination directory where the XML file generated by the CA CMDB Export

report will be stored, and the name for the XML file, and then click Next.

The information is set for the BusinessObjects XI job servers.


installation time in order to save the generated XML file to the file system. However, it is

possible to manually configure these settings post-installation. Instructions are included in

the Integration Guide that is packaged with the patch.



The Configure CABI_GRLoader screen appears.

The following GRLoader arguments were used in this example:

-s http://cmdb:8080 -u ServiceDesk -p Password -i C:\CCA-CMDB\cca2cmdb.xml -n -a -N

C:\GRLoader -E

11. Configure the following settings for GRLoader, then click Next:

■ Arguments—Parameters needed to execute GRLoader from BusinessObjects XI



■ Working Directory—Directory containing the copied GRLoader files


installation time. You can also manually configure these settings post-installation as

described in the Integration Guide that is packaged with the patch .

The Pre-Installation Summary screen appears.

12. Review the summary information, then click Install.

The installation begins.

13. Click Done when the installation is complete.



Replace the Existing CAFApp Directory (Post-installation Task)

As part of the installation process, a new Client Access Framework (CAF) Page WAR file

(CAFApp.war) is deployed. The CAFApp WAR file provides a new parameters prompt page for the

CA CMDB Export report. However, the new page does not take effect until the existing CAFApp

directory is deleted from the BusinessObjects XI webapps directory and the applicable

BusinessObjects XI services stopped and restarted.

Before:

After:



To replace the existing CAFApp directory

1. Stop the following services using using either the Windows Service Control Manager or the

BusinessObjects XI Central Configuration Manager:

■ Installed application server such as Apache Tomcat

■ Server Intelligence Agent

2. Delete the CAFApp folder from the BusinessObjects XI webapps directory.

For example: C:\Program Files\CA\SC\CommonReporting3\Tomcat55\webapps

3. Start the previously stopped BusinessObjects XI services

A new CAFApp folder is created in the BusinessObjects XI webapps directory. It may take

several minutes to appear.

Configure Database Connection in BusinessObjects Designer

If you are implementing the integration with the CCA Database residing on an SQL Server

instance, you must modify the CCA_CMDB universe connection properties using BusinessObjects

Designer.

To configure the universe connection

1. Select Designer from the BusinessObjects Enterprise Start menu.

Note: If a wizard appears, click Cancel



The Universe Designer appears.

2. Select File, Import.

The Import Universe dialog appears.

3. Select the CA Universes/CCA_CMDB universe, then click OK.

The dialog closes.



4. Select Tools, Connections from the top menu bar.

The Connection List dialog appears.

5. Select CCA_CMDB then click Edit.

The Login Parameters dialog appears (the graphic shows user-entered data, not default

data).



6. Enter or select the following information in the corresponding field, and then click Next:

Authentication Mode

Specifies the user authentication mode used to access the database. Select Use

specified username and password.

User name

Specifies the user accessing the database.

Default: cca

Password

Specifies the password for the CCA Database user.

Server

Specifies the database server using the following syntax:

<server>\<instance_name>,CA Portal

Database

Specifies the database name.

A confirmation message appears.

7. Click Next, then click Finish.

The Login Parameters dialog closes.

8. Click Save, and then click File, Export.

The settings are saved, then exported. When the export completes, a message confirms the

successful export.

9. Click OK.

The message closes.



10. Open the BusinessObjects Central Configuration Manager (CCM) from the Start menu.

The Central Configuration Manager appears.

11. Select the Apache Tomcat and Server Intelligence Agent services, then click the Stop icon.

The services are stopped.



12. Navigate to the CA\SC\CommonReporting3\Tomcat55\webapps folder, then delete the

CAFApp folder.

You are prompted to confirm the deletion.

13. Click Yes.

The folder is deleted.

14. Start the Apache Tomcat and Server Intelligence Agent services

The CAFApp folder is recreated. It may take several minutes to appear.

15. Navigate to CAFApp\WEB-INF\classes\com\ca\parameters, open the database.properties

file, and then edit the DB_URL line to match the entries you made in the Login Parameters

dialog (step 5):

DB_URL=jdbc:sqlserver://<myServer>;instanceName=<myInstance>;databaseName=<CCAdatabas

eName>;user=<CCAdatabaseUser>;password=<CCAdatabasePassword>;

Note: The default CCA Database name and user name are cca.

Save and close the file.

16. Restart the Apache Tomcat and Server Intelligence Agent services.

The database connection is configured for the integration.

Upgrading to CA Configuration Automation r12.5


Upgrading to CA Configuration Automation r12.5

If you configure the integration between CA ACM r12 and CA CMDB and later decide to upgrade

to CA Configuration Automation r12.5, there are no updates required for the integration. If you

upgrade CA ACM r12 as documented in CA Configuration Automation Implementation Guide, the

integration will continue to work. There is no need to re-install the integration patch or update

the MDR entry (that is, the MDR Class should remain as CA ACM r12).


Chapter 3: Working with the Integration After installing the integration, you must complete the following tasks to import the CA ACM or

CA Configuration Automation CIs and CI relationships into CA CMDB:

■ Configure and schedule the CA CMDB Export report within BusinessObjects XI to generate

the XML file that will be used by GRLoader

■ Import the CIs and CI relationships listed in the XML file by performing one of the following:

■ Automate the GRLoader import process by scheduling the BOXI_GRLoader program

within BusinessObjects XI

■ Manually execute GRLoader (copy the XML file to your CMDB machine)

Schedule the BOXI_GRLoader

If you decide to automate the CMDB import process, you must configure and schedule the

BOXI_GRLoader program that you added to BusinessObjects XI as part of the integration patch

installation. The scheduling of BOXI_GRLoader must be done prior to scheduling the CA CMDB

Export report. The CA CMDB Export report triggers an event that indicates the export of the CA

Configuration Automation or CA ACM CIs is complete. The BOXI_GRLoader listens for the

specified event and when it detects it, initiates the GRLoader import.


42 Chapter 3: Working with the Integration

To schedule the BOXI_GRLoader program

1. Launch the BusinessObjects Enterprise Center Management Console. From the

BusinessObjects XI server, select Start, Programs, BusinessObjects XI 3.1, BusinessObjects

Enterprise, BusinessObjects Enterprise Central Management Console.

2. Enter your login credentials (Default: Administrator) and click Log In.

3. Select Folders from the Organize category or from the drop-down menu.

4. Navigate to one of the following folders:

■ CA ACM r12 SP2: All Folders, CA Reports, CA ACM to CMDB

■ CA Configuration Automation r12.5: All Folders, CA Reports, CCA to CMDB.

5. In the right pane, right-click BOXI_GRLoader and select Schedule.

6. Configure the following settings in the Schedule section:

■ Recurrence: The frequency that the BOXI_GRLoader program should run

Run Object - Default: Now

Note: You may want to consider scheduling the import on a daily basis during

non-business hours.

■ Program Parameters: The configuration settings for executing GRLoader, including:

Arguments—Specifies the parameter list necessary for executing GRLoader from

BusinessObjects XI



Working Directory—Specifies the directory that contains the copied GRLoader files

Class to run—Specifies the class within the BOXI_GRLoader.jar file. This value must

always be acm2cmdb.BOXI_GRLoader (applies to both CA ACM r12 SP2 and CA

Configuration Automation r12.5).



Classpath—Specifies the path to the GRLoader jar file and the path to the directory

containing the GRLoader files (separate paths by a semi-colon)

Example: c:\GRLoader\GRLoader.jar; c:\GRLoader

Note: These fields are populated if values were specified during installation.

The following values were used in the example:

Arguments:

-s http://cmdb:8080 -u ServiceDesk –p Password -i C:\CCA-CMDB\cca2cmdb.xml -n -a -N

C:\GRLoader –E

Classpath:

c:\GRLoader\GRLoader.jar; c:\GRLoader

■ Destination: Email (Optional). Specifies the following settings necessary to send an email

when the import is complete:

From

To

Cc (optional)

Subject

Message



■ Events: Specifies the name of the event the BOXI_GRLoader needs to wait for before it

executes GRLoader

Events to wait for—Default: Successful_Report_XML_Event

Note: Changes to the Schedule settings are not retained for subsequent scheduling

instances of the BOXI_GRLoader program. To make the changes persistent, update the

same options in the Default Settings section of BOXI_GRLoader properties.

7. Click Schedule (bottom right).

The history table for BOXI_GRLoader appears and a new program instance is displayed in the

table. The instance remains in the Pending state until the specified event occurs (triggered

by the CA CMDB Export report).

8. Close the BOXI_GRLoader History window.



Receiving Import Results by Email

If you configured the destination for BOXI_GRLoader program as Email and specified the required

email settings, you will receive an email message similar to the one shown in the following

graphic after the GRLoader import process is complete.

The email message contains an attached output file containing the results of the GRLoader

operation. The report specifies the number of CIs and relationships that were:

■ Read in from the XML file

■ Skipped

■ Inserted into CA CMDB

■ Updated in CA CMDB

■ Resulted in an error

■ Flagged as a warning

Schedule the CA CMDB Export Report


For additional information on the error or warning messages, see the GRLoader.log file located in

the following locations:

■ CA CMDB server: <install_path>\CA\Service Desk Manager\log

■ BusinessObjects XI server: <path_to_directory_containing_copied_GRLoader_files>\log

Note: The BusinessObjects XI destination servers (CrystalReportJobServer, ProgramJobServer,

and DestinationJobServer) must be configured for Email for you to receive an email message

from BusinessObjects XI. These destination server configurations are done either during

installation or as a post-installation step. Instructions for configuring the destination servers as a

post-installation task are included in Appendix A of the Integration Guide that is packaged with

the patch.


The CA CMDB Export report generates an XML file that contains the CA ACM or CA Configuration

Automation CIs and CI relationships. If configured, the report triggers an event that starts the

BOXI_GRLoader program.

To schedule the CA CMDB Export report

1. Launch the BusinessObjects Enterprise Center Management Console. From the

BusinessObjects XI server, select Start, Programs, BusinessObjects XI 3.1, BusinessObjects

Enterprise, BusinessObjects Enterprise Central Management Console.


3. Select Folders from the Organize category or from the drop-down menu.

4. Navigate to one of the following folders:

■ CA ACM r12 SP2: All Folders, CA Reports, CA ACM to CMDB

■ CA Configuration Automation r12.5: All Folders, CA Reports, CCA to CMDB

5. In the right pane, right-click CA CMDB Export and select Schedule.



6. Configure the following settings in the Schedule section:

■ Recurrence: The frequency that the CA CMDB Export report should run

Run Object - Default: Now

Note: You may want to consider scheduling the import on a daily basis during

non-business hours.

■ Parameters: Specifies the export settings for extracting the desired CIs and CI

relationships from CA Configuration Automation.

• Include Network Interface Card CIs—Export all network interface card CIs associated

with the selected servers.

Note: If you are not required to manage network interface cards as separate CIs within

the CA CMDB, clear this option.



• Include FileSystem CIs—Export all file system CIs associated with the selected servers.

Note: If you are not required to manage file systems as separate CIs within the CA

CMDB, clear this option.

• Include Harddrive CIs—Export all harddrives CIs associated with the selected servers.

Note: If you are not required to manage hard drives as separate CIs within the CA

CMDB, clear this option.

• Include servers not listed in the Server Table—Export any servers associated with the

selected servers even if it is not listed in the CA ACMCA Configuration Automation

Servers table (that is, the servers that appear in the Relationship table for a selected

server).

• Server Status—Export the server CIs with a status of Imported, Managed, New and/or

Unmanaged. Selecting ‘*’ includes all server states.

• Servers—Select the server CIs to export. Selecting ‘*’ exports all servers listed in the

Servers table.

• Service—Select the service CIs to export. Selecting ‘*’ exports all services listed in the

Services table.

• Service Groups—Select the service group CIs to export. Selecting ‘*’ exports all server

groups listed in the Server Groups table.

• Blueprints—Select the blueprints CI to export. Selecting ‘*’ exports all blueprints

associated with the exported servers and services.

Note: You must click Set Parameters at the bottom of the Parameters page to save your

selections.

■ Format: Specifies the format of the generated file. This option must be set to Plain Text.



■ Destination: Specifies the location of where the generated XML file should be stored.

File System—Settings necessary to save the generated XML file to the local file system.

This option is used in conjunction with the BOXI_GRLoader program when automating

the CI import to the CA CMDB.

• Directory—Enter the name of the directory where the file should be stored.

• File Name (Use Specific Name)—Enter a name for the XML file.

• User Name—Enter the name of a user who has write access to the directory.

• Password—Enter the password for the specified user.

FTP Server - Settings necessary to save the generated XML file to a remote file system.

This option may be used when manually executing GRLoader to import the CA ACM or

CA Configuration Automation CIs into the CA CMDB.

• Host—Enter the host name of the remote FTP server.

• Port—Enter the port number for the FTP server (default: 21).

• User Name—Enter the user who has rights to upload files to the FTP server.

• Password—Enter the password for the specified user.

• Account—Enter the FTP account information, if required (rarely implemented).



• Directory—Enter the name of the directory where the file should be stored.

• File Name (Use Specific Name)—Enter a name for the XML file.

■ Events: Specifies the name of the event the CA CMDB Export report needs to trigger

when the export is complete. This event is used in conjunction with the BOXI_GRLoader

program.

• Events to trigger on completion—Default: Successful_Report_XML_Event

Note: If you plan to manually run the GRLoader program to import the CIs and CI

relationships contained in the CA CMDB Export report, it is not necessary to specify an

event. Leave the ‘Events to trigger on completion’ field empty.

Note: Changes to the Schedule settings are not retained for subsequent scheduling

instances of the CA CMDB Export report. To make the changes persistent, update the

same options listed in the Default Settings section of CA CMDB Export properties. Note

that you cannot configure the Parameter settings under Default Settings. The

Parameters settings must be configured each time the CA CMDB Export report is

scheduled.



7. Click Schedule in the lower right corner of the right pane.

The History table for CA CMDB Export report appears and a new report instance is displayed

in the table. The status first shows Pending, followed by Running, and then either Success or

Failed. Click on the Refresh button to update the history table.

If the Status is listed as Success, you can view the generated XML file in the specified

destination location.

If the Status is listed as Failed, highlight the instance in the history table and click the

Instance Detail button. The Instance Details window displays an error message.

8. Close the CA CMDB Export History window.

Schedule Multiple Report Instances



To specify different sets of export parameters, you must schedule multiple CA CMDB Export

reports. Although not functionally necessary, it is recommended that you schedule separate

instances of the BOXI_GRLoader program to correspond to each of your CA CMDB Export reports

as follows:

■ Supply unique names for the different CA CMDB Export report and BOXI_GRLoader program

instances.

■ Create new Events within BusinessObjects XI that can be used by the CA CMDB Export

reports and the BOXI_GRLoader programs.

■ Specify a different name for the generated XML file with the CA CMDB Export report and use

the new name as the input for the associated BOXI_GRLoader program.

This ensures the correct set of CIs is imported at the appropriately scheduled time.

Creating Events

Events are a key component when automating the importation of CA ACM or CA Configuration

Automation CIs into CA CMDB. The BOXI_GRLoader program can be configured to wait for a

specific event. Subsequently, the CA CMDB Export report can be configured to trigger that

specific event once the CI export from CA ACM or CA Configuration Automation is complete.

After the BOXI_GRLoader program detects the event, it starts the CI import process using

GRLoader.

To create new events in BusinessObjects XI:

1. Open the BusinessObjects Enterprise Center Management Console from the BusinessObjects

XI server by selecting Start, Programs, BusinessObjects XI 3.1, BusinessObjects Enterprise,

BusinessObjects Enterprise Central Management Console.


3. Select Events from the Organize category or from the drop-down menu.



4. Select Manage, New, New Event.

The New Event dialog appears:

5. Enter the following information in the appropriate field, then click OK:

■ Type—Select Schedule.

■ Event Name—Enter a unique name for the event.

■ Description—(Optional) Enter a brief summary of when and how the event will be used.

■ Option buttons—Select Success.

Execute GRLoader Manually


Execute GRLoader Manually

To manually import the CIs and CI relationships from CA ACM or CA Configuration Automation

to CA CMDB

1. Ensure a copy of the generated XML file containing the CIs and CI relationships is available

on the CA CMDB host computer. You can manually copy the file to your CA CMDB host or

automate the file copy using the CA CMDB Export Report by either saving the XML file to a

mapped drive or configuring an FTP Server destination.

2. Execute the GRLoader utility from the command line, using the generated XML file as the

input file. Run the grloader -? command from a command prompt on your CA CMDB host

computer to display the syntax for the utility.

For more information on the GRLoader utility, please see the General Resource Loader

(GRLoader) chapter in the CA Service Desk Manager CA CMDB Technical Reference Guide.


Chapter 4: Viewing the Import Results After the CA ACM or CA Configuration Automation CIs are imported into CA CMDB using

GRLoader (either manually or automatically), you can view the CIs and any relationships between

them from the CA CMDB UIs.

View CIs and Relationships in the Service Desk Web Client

From the Service Desk Web Client, you can view lists of CIs and relationships exported from CA

ACM or CA Configuration Automation.

To view Cis or CI relationships in the Service Desk Web Client

1. Open the Service Desk Web Client.

2. Click the Administration tab, then expand the CA CMDB node in the left pane.

3. Click CI List or CI Relationship List.

You can search for a particular CI or relationship, or display the entire list of CIs (by leaving

the search criteria blank and clicking Search).


56 Chapter 4: Viewing the Import Results

The Configuration Item List and the Configuration Item Relationship List are shown in the

following graphics:

4. Click a CI or Relationship name to display details about the object.

CI details include the imported attribute information from CA ACM or CA Configuration

Automation. For example, for a virtual machine, this attribute information could include

processor type, processor speed, memory installed, and disk capacity.



Additionally, you can view all the CMDB relationships for that particular CI.

As part of the integration between CA ACM or CA Configuration Automation and CA CMDB,

you can select a CI within CA CMDB and launch CA ACM or CA Configuration Automation

in-context to that CI as described in the next section.

To launch CA Configuration Automation in-context from a CA CMDB CI

1. From a CI detail page, click the Attributes tab.

2. Click the MDR button (top right corner) of the Attributes tab.

Note: The MDR was created as part of the integration process.

View CIs and Relationships in the CMDB Visualizer


A new browser window opens and contains the CA ACM or CA Configuration Automation

details for the selected CI.

Note: You may be prompted to log into CA ACM or CA Configuration Automation.


With the CMDB Visualizer, you can view a graphical representation of the CA ACM or CA

Configuration Automation CIs and the relationships between them.

To view CIs and Relationships in the CMDB Visualizer

1. Open the CMDB Visualizer.

2. Click Search in the left pane to search for a specific CI or relationship or leave the CI Name as

‘*’ and click Search to display a list of all CIs.

3. Drag-and-drop the desired CI to the right pane to see its associated relationships.



To launch a CI in-context in CA ACM or CA Configuration Automation from the CA CMDB

Visualizer

1. Do one of the following:

■ Right-click a CI in the Search Results list in the left pane, and select Launch MDR:

■ Right-click a CI in the graphical diagram in the right pane, and select Launch MDR:

The Managed Data Repository (MDR) window appears.

2. Select the MDR you created as part of the integration process, and click Launch.



A new browser window opens and displays the CA ACM or CA Configuration Automation

details for the selected CI.

Note: You may be prompted to log into CA ACM or CA Configuration Automation.


Chapter 5: Customizing the Integration The integration uses the information in the integration’s tables within the CCA Database or the

ACM Database (acmbo_attrmapping, acmbo_classmapping, and acmbo_relshpmapping) to

determine which CA ACM or CA Configuration Automation CIs, attributes, and relationships are

exported and how to map them to CA CMDB’s families, classes, attributes, and relationships.

Note: Unlike the integration between CA Cohesion and CA CMDB, there is no longer a

cmdb_mapping.xml file.

For more information on customization, see Chapter 3 of the CA CMDB Integration Guide.

Create a Backup

Before making any changes to the integration tables within the CCA Database or the ACM

Database, it is highly recommended you make backup copies of the tables. Should something

adverse happen after making your customizations, you can always revert to the backup copy.

To create a backup version of database tables

1. Log in to your database client as a user with access to add and update database objects in

Microsoft SQL Server or Oracle.

2. Run the following three queries against the CCA Database or the ACM Database:

■ SELECT * INTO acmbo_attrmappingorig FROM acmbo_attrmapping

■ SELECT * INTO acmbo_classmappingorig FROM acmbo_classmapping

■ SELECT * INTO acmbo_relshpmappingorig FROM acmbo_relshpmapping

The queries create a backup table with the suffix ‘orig’ for each of the integration’s mapping

tables. You can specify any name for the backup tables.

If subsequent backups of any of the three mapping tables are necessary, it is highly

recommended that the current backup tables are dropped and the previous queries are

executed again. For example:

DROP TABLE acmbo_attrmappingorig;

SELECT * INTO acmbo_attrmappingorig FROM acmbo_attrmapping;

Modify Attribute Mappings

62 Chapter 5: Customizing the Integration

To restore the original mappings to the three tables

Run the following queries:

■ SELECT * INTO acmbo_attrmapping FROM acmbo_attrmappingorig

■ SELECT * INTO acmbo_classmapping FROM acmbo_classmappinggorig

■ SELECT * INTO acmbo_relshpmapping FROM acmbo_relshpmappingorig

Modify Attribute Mappings

To modify the attribute mappings between CA ACM or CA Configuration Automation and CA

CMDB, you must update the acmbo_attrmapping table in the CCA Database or the ACM

Database. Use the following SQL query to update the table:

UPDATE acmbo_attrmapping SET cmdbattribute=’<attributeName>’ WHERE

ci=’<ciType>’ AND acmattribute=’<attributeName>’

For a complete list of the predefined attribute mappings between CA ACM or CA Configuration

Automation and CA CMDB contained in the acmbo_attrmapping table, see Appendix A (see

page 69).

The process for adding new attribute mappings can be fairly involved and is out of the scope of

this document. In addition to inserting the new attribute mappings into the acmbo_attrmapping

table in the CCA Database or the ACM Database, the process requires the modification of the CA

CMDB Export report located within BusinessObjects using the report designer, SAP Crystal

Reports.

Note: The license for SAP Crystal Reports is not included as part of the license for CA Business

Intelligence.

Modify Class Mappings


Modify Class Mappings

The class mapping database table includes a list of default CA ACM or CA Configuration

Automation components and their default mappings to CA CMDB Classes. Any component not

listed in the table is assigned a default class value. For example, if a discovered software

component is not listed in the database table it is assigned a default value of Software.COTS as

defined in the following table entry:

To modify class mappings between CA ACM or CA Configuration Automation and CA CMDB

1. Run the following query:

SELECT * FROM acmbo_classmapping WHERE componentname=’*’

The results of the query shows each CI type that has a default CMDB class entry:

Modify Relationship Mappings

64 Chapter 5: Customizing the Integration

2. Do one of the following:

■ Update the acmbo_classmapping table in the CCA Database or the ACM Dtabase using

the following SQL query:

UPDATE acmbo_classmapping SET cmdbclass=’<className>’ WHERE ci=’<ciType>’ AND

cmdbclass=’<className>’ AND componentname=’<componentName>’ AND

cmdbfamily=’<familyName>’

■ Add a new class mapping, you will need to use the SQL query:

INSERT INTO acmbo_classmapping (ci, componentname, cmdbfamily, cmdbclass) VALUES

('<ciType>', '<componentName>', '<familyName>', '<className>')

Note: When you specify or change a CMDB class mapping in the database table, that class

and family must already exist in CA CMDB or else the export will fail.

For a complete listing of predefined class mappings between CA ACM or CA Configuration

Automation and CA CMDB found in the acmbo_classmapping table, see Appendix A (see

page 69).

Modify Relationship Mappings

To modify the class mappings between CA ACM or CA Configuration Automation and CA CMDB

Update the acmbo_relshpmapping table in the CCA Database or the ACM Database using the

following SQL query:

UPDATE acmbo_relshpmapping SET relationship=’<relationshipType>’ WHERE

ci='<ciType>' AND targetci='<ciType>' AND relationship='<relationshipType>'

For a complete list of the predefined relationship mappings between CA ACM or CA

Configuration Automation and CA CMDB contained in the acmbo_relshpmapping table, see

Appendix A (see page 69).


Chapter 6: Troubleshooting This section includes the following topics:

■ Running the patch installer in debug mode

■ Viewing the GRLoader log file

■ An advisement for users attempting to install the integration patch (cca-cmdb.exe) directly

from the CCA r12.5 DVD

■ Information on a known issue when using a particular Java JRE version

Running Patch Installers in Debug Mode

If you encounter problems installing any of the patches for the CA ACM or CA Configuration

Automation/CA CMDB integration, you can run the installer in debug mode by pressing and

holding the CTRL key down immediately after launching the installer until a console window

appears. Then, step through the installer, entering the required information. Output is written to

the console window. Prior to exiting the installer, make sure to copy the contents of the console

window to a text file. If necessary, this file can be sent to CA Support for further analysis.

View the GRLoader Log File

If the GRLoader utility fails to import the CA ACM or CA Configuration Automation CIs and/or

relationships, you can view the GRLoader log file to see any accompanying error messages. The

GRLoader log file location is dependent upon whether GRLoader is executed automatically from

the BusinessObjects XI server or manually from the CA CMDB server:

■ CA CMDB server: <install_path>\CA\Service Desk Manager\log

■ BusinessObjects XI server: <path_to_directory_containing_copied_GRLoader_files>\log


66 Chapter 6: Troubleshooting

The following error and warning messages may appear:

■ ERROR grCI 1013 Error trying to insert CI (boxi.forwardinc.ca). INVALID

nr::cmdb_update_idmap:120 - MDR mdr_class(CA ACM

r12)/mdr_name(acmserver.forwardinc.ca) is undefined for CI name (boxi.forwardinc.ca)

This message occurs when the Management Data Repository (MDR) entry within CA CMDB is

incorrectly configured. In this example, GRLoader is unable to import the CI,

boxi.forwardinc.ca. If you see a similar message, ensure the following is true of the MDR

entry:

■ The MDR Class is specified as CA ACM r12 or CCA 12.5, depending upon the product

version you are using. In cases where the integration was configured for CA ACM r12

and CA ACM was later upgraded to CCA 12.5, the MDR Class should remain specified as

CA ACM r12.

■ The MDR Name is listed as the hostname of your ACMServer or your CCA Server.

■ ERROR grCIRelation 558 ERROR: Provider CI not found.

This message occurs when the integration attempts to extract a relationship between a

virtual machine and its provider (such as VMware ESX Host) and the provider CI is not

present in the database. First, make sure that the provider CI was discovered within CA ACM

or CA Configuration Automation. Additionally, verify the credentials for the provider (that is,

VMware ESX Host or VMware vCenter Server) are present in the appropriate credential

vault. After adding the credentials, you must re-run Network Discovery using a network scan

that includes the Softagent.

■ ERROR grCI 1013 Error trying to insert CI (webserver.forwardinc.ca). Error setting attr

'manufacturer' on object 'nr:41E76BE947CB8946B771969D09A8941A' to value

'3018C6F5BE38BC4BB1822B42FF3BCF98' AHD05206:Not allowed to modify this field.

This message occurs when the integration attempts to update the Manufacturer field for a CI

being imported into CMDB. This error prevents the CI from being inserted within the CMDB.

The Manufacturer is a read-only field and cannot be updated. As a workaround, remove the

<manufacturer> </manufacturer> lines from the generated XML file and manually import

the file using GRLoader.



To manually import the modified XML file using the GRLoader

1. Open a command prompt.

2. Change directory to the folder containing the copied GRLoader files (for example,

c:\GRLoader).

cd <directory_containing_copied_GRLoader_files>

Example:

cd \GRloader

3. Execute the following command:

grloader.jar -s http://<CMDB_hostname>:Port -u <username> -p

<password> -i <path_to_modified_XML_file_containing_CCA_CIs>

-n -a -N <path_to_directory_containing_copied_GRLoader_files> -E

Example:

grloader.jar -s http://cmdb:8080 -u ServiceDesk -p Password -i

c:\XMLFiles\cca2cmdb.xml -n -a -N c:\GRLoader -E

■ WARNING: Unable to find ca_cmpny.sym=(CA, Inc).

This message occurs when the integration attempts to import a CI with a Manufacturer

attribute that was not predefined within CA CMDB. You must ensure the company name (for

example, CA, Inc.) specified in the <manufacturer> tag within the generated XML file is

defined as a Company in the CA CMDB prior to importing the CIs from CA Configuration

Automation. Despite the warning message, the CI is still inserted or updated. However, the

value for the field is not updated on the CI.

Note: All SREL objects, contacts, organizations, locations, models, and so on, should be

defined within the CA CMDB database prior to loading CIs.

■ WARNING: Unable to find mfrmod.sym=(Dell Inc. PowerEdge R710).

This message occurs when the integration attempts to import a CI with a Model attribute

that was not predefined within CA CMDB. You must ensure the model (for example, Dell Inc.

PowerEdge R710) specified in the <model> tag within the generated XML file is defined as a

Model in the CA CMDB prior to importing the CIs from CA Configuration Automation.

Despite the warning message, the CI is still inserted or updated. However, the value for the

field is not updated on the CI.

Installing the Integration Patch Directly from the DVD

68 Chapter 6: Troubleshooting

Note: All SREL objects, contacts, organizations, locations, models, etc. should be defined

within the CA CMDB database prior to loading CIs.

Installing the Integration Patch Directly from the DVD

If you attempt to install the cca-cmdb.exe integration patch directly from the CA Configuration

Automation r12.5 DVD, the installation will fail and the following exception is logged in the

cmdb-acm-boxi.log file (located in the Windows’ TEMP directory):

Action: exception while executing: com.zerog.ia.installer.GhostDirectory --

temp

java.lang.Exception: Failed to create directory: D:\CCA\CMDB\Windows\temp

at com.zerog.ia.installer.GhostDirectory.installSelf(DashoA10*..)

at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)

at com.zerog.ia.installer.GhostDirectory.install(DashoA10*..)

at com.zerog.ia.installer.InstallablePiece.install(DashoA10*..)

at com.zerog.ia.installer.Installer.install(DashoA10*..)

at com.zerog.ia.installer.actions.InstallProgressAction.n(DashoA10*..)

at com.zerog.ia.installer.actions.ProgressPanelAction$1.run(DashoA10*..)

Because the installation program attempts to create a temp directory in the same location as the

integration patch, the patch must be moved to a drive with read-write permission prior to its

execution.

Using Java JRE v1.6.0_29 Causes Patch Installer to Hang

The cca-cmdb.exe integration patch requires Java Runtime Environment (JRE) 1.5 or higher.

However, there is a known database connection issue with JRE version 1.6 Update 29 (1.6.0_29).

When using this JRE version, the integration patch installer hangs after you enter your database

connection details and click Next. Because of this, Java JRE version 1.6 Update 29 is not

supported by the integration.


Appendix A: Relationships and Mappings This section contains information about NDG relationships and the various types of predefined

CA Configuration Automation to CA CMDB mappings.

Supported Network Discovery Gateway (NDG) Relationships

CA Configuration Automation stores server information discovered by the Network Discovery

Gateway (NDG) on the Server Details page on the Server tab.

NDG—in conjunction with the SoftAgent technology—gathers the following server information:

■ Virtual Environment

■ Network Adapters

■ Hardware

■ Installed Applications

■ Services and Daemons

■ Open Ports

■ Relationships

Only the virtual environment, relationship, and limited hardware information can be transferred

to CA CMDB after configuring the CA Configuration Automation integration. A list of the

predefined attribute and relationship mappings between CA Configuration Automation and CA

CMDB is included later in this Appendix.

Predefined CA ACM to CA CMDB Mappings

70 Appendix A: Relationships and Mappings

When exporting the relationship data, the integration attempts to export the target CIs even if

they do not appear in the Server table and were not selected for export (you may see

‘Dependent CI not found’ errors in the generated error XML file). If this is not desirable, disable

the “Include servers not listed in the Server Table” option in the Parameters section of the CA

CMDB Export Report.

Virtual Environments

As previously mentioned, the NDG is able to gather information on virtual environments. This

information includes server type and virtual environment relationships, and is found in the

Virtualization page on the Server tab. You can view the relationships between your virtual

machines, hypervisors, and management servers.

As part of the CA Configuration Automation / CA CMDB Integration, the ‘hosts virtual machine’ in

the Relationship Type column is exported from CA Configuration Automation. This enables you to

see the relationship between a hypervisor and its hosted virtual machines within CA CMDB (is

server of/is the child of). However, the ‘manages hypervisor’ relationship (relationship between

management server and hypervisor) is not exported. For example, within the CMDB, you cannot

see the relationship between a VMware vCenter server and the VMware ESX server.




The following sections describe the predefined mapping types:

■ Attribute Mappings

■ Class Mappings

■ Relationship Mappings

Attribute Mappings

The following table shows the CA Configuration Automation to CA CMDB attribute mappings for

each type of CI are listed. These mappings are stored in the acmbo_attrmapping table in the

ACM Database.

CI ACM Attribute CMDB Attribute

cluster biosver bios_ver

cluster domainname dns_name

cluster domainname network_name

cluster Gateway gateway_id

cluster host_id federated_asset_id

cluster Hostname name

cluster ip_address network_address

cluster mac_address mac_address

cluster ospatchlvl security_patch_level

cluster system_name system_name

component comp_id federated_asset_id

component delete_flag delete_flag

component description description

component host server

component name name

component root install_dir

component system_name system_name

component type type

component Vendor manufacturer

component version version




File System media_type media_type

File System name name

File System Size total_capacity

File System used_space used_space

Hard Drive media_type media_type

Hard Drive name name

Hard Drive Size total_capacity

lpar arch proc_type

lpar biosver bios_ver

lpar cpucount number_proc_inst

lpar cpuspeed proc_speed

lpar host_id federated_asset_id

lpar Hostname name

lpar locstorcap hard_drive_capacity

lpar mac_address mac_address

lpar ospatchlvl security_patch_level

lpar pmem phys_mem

lpar serialno serial_number

lpar system_name system_name

nic Gateway gateway_id

nic IP Address ip_mgmt_addr

nic IP Address network_address

nic name name

nic Speed line_speed

nic Subnet Mask subnet_mask

server arch proc_type

server biosver bios_ver

server cpucount number_proc_inst

server cpuspeed proc_speed

server domainname dns_name

server dvddrive cd_rom_type

server host_id federated_asset_id




server Hostname name

server ip_address alarm_id

server locstorcap hard_drive_capacity

server mac_address mac_address

server make manufacturer

server model model

server niccount number_net_card

server ospatchlvl security_patch_level

server platform_name server_type

server pmem phys_mem

server serialno serial_number

server system_name system_name

server vmem swap_size

service comp_id federated_asset_id

service description description

service name name

service version version

virtual arch proc_type

virtual biosver bios_ver

virtual cpuspeed proc_speed

virtual host_id federated_asset_id

virtual Hostname name

virtual locstorcap hard_drive_capacity

virtual mac_address mac_address

virtual ospatchlvl security_patch_level

virtual pmem phys_mem

virtual serialno serial_number

virtual system_name system_name



Class Mappings

The following table shows the CA Configuration Automation CI mappings to the corresponding

CMDB class and family. These mappings are stored in the acmbo_classmapping table in the ACM

database.

CI Component Name CMDB Family CMDB Class

cluster * Cluster Cluster

component * Software.COTS COTS

component AIX Software.Operating System

AIX OS

component BEA WebLogic Domains (UNIX)

Software.Application Server

Application Server

component BEA WebLogic Domains (Windows)


Application Server

component BSD Unix Software.Operating System

Unix OS

component HP-UX Software.Operating System

HP UX OS

component IBM DB2 Universal Database (UNIX)

Software.Database DB2

component IBM DB2 Universal Database (Windows)

Software.Database DB2

component IBM LPAR Software.COTS COTS

component IBM WebSphere 5 Server Instance (UNIX)


Application Server

component IBM WebSphere 5 Server Instance (Windows)


Application Server

component IBM WebSphere 6 Server Instance (UNIX)


Application Server

component IBM WebSphere 6 Server Instance (Windows)


Application Server

component Informix Dynamic Server (UNIX)

Software.Database Other Software Database

component Informix Dynamic Server (Windows)

Software.Database Other Software Database

component Ingres (UNIX) Software.Database Ingres

component Microsoft Access Software.Database SQL




component Microsoft SQL Server Software.Database SQL

component Microsoft SQL Server - Client

Software.Database SQL

component Microsoft SQL Server - Datafiles


component Microsoft SQL Server 2005


component Microsoft SQL Server 2005 - Datafiles

Software.COTS SQL

component Microsoft SQL Server 2005 -Tools


component Microsoft Virtual Server

Software.COTS COTS

component MySQL (UNIX) Software.Database Other Software Database

component MySQL (Windows) Software.Database Other Software Database

component MySQL Administrator Software.Database Other Software Database

component MySQL Connector/Net Software.Database Other Software Database

component MySQL Datafiles Software.Database Other Software Database

component Oracle - Client (UNIX) Software.Database Oracle

component Oracle - Client (Windows)

Software.Database Oracle

component Oracle - Datafiles Software.Database Oracle

component Oracle 10g Application Server (UNIX)


Oracle

component Oracle 10g Application Server (Windows)


Oracle

component Oracle 8i Database (UNIX)


component Oracle 8i Database (Windows)


component Oracle 9i Database (UNIX)


component Oracle 9i Database (Windows)





component Oracle Database 10g (UNIX)


component Oracle Database 10g (Windows)


component Oracle Database 11g (Windows)


component PostgreSQL (UNIX) Software.Database Other Software Database

component PostgreSQL (Windows) Software.Database Other Software Database

component Red Hat Linux Software.Operating System

Linux OS

component Solaris Software.Operating System

Sun OS

component Solaris Zones Software.COTS COTS

component SuSE Linux Software.Operating System

Linux OS

component Sybase Adaptive Server Enterprise (UNIX)

Software.Database Sybase

component Sybase Adaptive Server Enterprise (Windows)

Software.Database Sybase

component Tru64 Unix Software.Operating System

Unix OS

component VMware (GSX) Server Software.COTS COTS

component VMware ESX Server Software.COTS COTS

component Windows Software.Operating System

Windows OS

component WinNT Software.Operating System

Windows OS

File System * Hardware.Storage File System

Hard Drive * Hardware.Storage Hard Drive

lpar * Hardware.Logical Partition

Logical Partition

lpar IBM LPAR Hardware.Logical Partition

Logical Partition

nic * Network.Network Interface Card

Network Interface Card




server * Hardware.Server Other Operating System

server AIX Hardware.Server AIX

server Any Hardware.Server Other Operating System

server Any Device Hardware.Server Other Operating System

server Any Unix Hardware.Server Unix

server Any Windows Hardware.Server Windows

server BIG-IP Hardware.Server Other Operating System

server CATOS Hardware.Server Switch

server FreeBSD Hardware.Server Unix

server HP-UX Hardware.Server HP UX

server IOS Network.Router Router

server Linux Hardware.Server Linux

server NetBSD Hardware.Server Unix

server Solaris Hardware.Server Sun

server System V Hardware.Server Unix

server Tru64 Hardware.Server Unix

server Windows 2000 Hardware.Server Windows

server Windows 2003 Hardware.Server Windows

server Windows NT Hardware.Server Windows

server Windows Vista Hardware.Server Windows

server Windows XP Hardware.Server Windows

service * Service Service

Virtual * Hardware.Virtual Machine

Other Hardware Virtual Machine

Virtual Microsoft Virtual Server

Hardware.Virtual Machine

Microsoft Virtual Server

Virtual Solaris Zones Hardware.Virtual Machine

Other Hardware Virtual Machine

Virtual VMware (GSX) Server Hardware.Virtual Machine

GSX Server

Virtual VMware ESX Server Hardware.Virtual Machine

ESX Server



Relationship Mappings

The following table shows the CA CMDB relationship mappings between the CIs. These mappings

are stored in the acmbo_relshpmapping table in the CA Configuration Automation database.

Source CI Target CI Relationship

cluster cluster fails over

component component uses

component server communicates with

component service is used by

lpar component hosts

lpar File System contains

lpar nic contains

lpar server is server of

lpar service runs

server component hosts

server File System contains

server Hard Drive contains

server lpar is the parent of

server nic contains

server server communicates with

server service runs

server virtual is the parent of

virtual component hosts

virtual File System contains

virtual Hard Drive contains

virtual nic contains

virtual server is server of

virtual service runs

ca configuration automation

Documents