Introduction › Integration Considerations

Integration Considerations

Consider the following information before you begin the integration:

• If you have previously used the CA Cohesion product, CA Cohesion ACM r5.0 and CA Configuration Automation r12.8 are different products with different architectures. The data that these two products discover may also differ. Duplicate data may appear in CA CMDB after migrating from the CA Cohesion ACM r5.0 system to the CA Configuration Automation r12.8 system. To manage these duplications, use the CA CMDB TWA, the CMDB ambiguity Index features, and other CMDB advanced reconciliation features.
• You installed and configured CA Business Intelligence r3.2, or r3.3 SP1 CA Service Desk Manager r12.7, and CA Configuration Automation r12.8 successfully.

  Important! You must upgrade CA Configuration Automation to r12.8 before executing the integration installer.

  Note: We recommend that you use the CA Business Intelligence instance where you deployed CA Configuration Automation r12.8 reports, but you can configure this integration on a separate CA Business Intelligence instance if you want.

• CA Cohesion ACM r5.0 sometimes stores server names without the fully qualified domain. CA Configuration Automation r12.8 always stores server names with fully qualified domain names. In these situations, duplicates could be created in CA CMDB after CIs are imported from CA Configuration Automation r12.8. To avoid this situation, the administrator can manually change all Cohesion r5.0 server names to the fully qualified (with domain) server names in Cohesion r5.0. After completing these tasks, run the CA CMDB Export Report again on Cohesion r5.0 to extract and import all CIs and their relationships into CA CMDB. Alternatively, use the TWA to store CI information from Cohesion r5.0, and SQL scripts run to change the system_name fields in the records to the fully qualified domain names. After this step, the records can be imported into CA CMDB.
• You inactivated the management data repository (MDR) for CA Cohesion ACM r5.0 if you are migrating to CA Configuration Automation r12.8

  Important! Do not change the previous CA Cohesion ACM r5.0 MDR definition to turn it into the CA Configuration Automation r12.8 MDR. You must inactivate the r5.0 MDR and create a new r12.8 MDR definition to enable cleanup of unused resources.

  Note: If you want to retain both CA Cohesion ACM r5.0 and CA Configuration Automation r12.8 as active MDRs, do not inactivate the CA Cohesion ACM r5.0 MDR.

• You created and activated an MDR for CA Configuration Automation r12.8.

  Note: This MDR defines a URL for launching a CA Configuration Automation CI from CA CMDB.

  Note: If you want to execute GRLoader from a remote system that does not have CA CMDB installed, see the Appendix.

• You installed the SQL Server or Oracle client on the CA Business Intelligence system.
• You downloaded the integration patch that contains the following files:

  CCA_CMDB_Report.biar

  Contains the CCA to CMDB Export Group, the CA CMDB Export Report, the BOXI_GRLoader.jar file, the CA Business Intelligence Universe, and the Universe Connection. You import this file to the computer that contains CA Business Intelligence.

  Important! You must add users (in CA Business Intelligence) to the CCA to CMDB Export Group who are responsible for executing the CA CMDB Export Report. When you add users to this group, they have full control to access the CA CMDB Export Report, the CCA_CMDB universe, and CCA_CMDB connections on importing the BIAR file. For more information about adding users to groups in CA Business Intelligence, see the CA Business Intelligence r3.2, or r3.3 SP1 Administration Guide.

  CCA_CMDB_DBSCRIPTS_MSSQL.zip

  Contains the SQL Server scripts that create the necessary tables, views, and insert statements to populate the required tables. You execute these scripts on the CA Configuration Automation database.

  CCA_CMDB_DBSCRIPTS_ORCL.zip

  Contains the Oracle scripts that create the necessary tables, views, and insert statements to populate the required tables. You execute these scripts on the CA Configuration Automation database.

  CAFApp.war

  Specifies the WAR file that you deploy in the Web Application Server used by CA Business Intelligence to generate the Prompt Page for the CA CMDB Export Report. This file is deployed on the CA Business Intelligence application server, for example the %BusinessObjects%/tomcat/webapps folder.

  CAFApp.xml

  Specifies the configuration file for the deployed WAR file. This file is deployed on the CA Business Intelligence server in the %BusinessObjects%/cacaf folder.

(Optional) Consider the following scenarios when configuring the GRLoader environment variables:

• If you do not want CA Business Intelligence to run the GRLoader, schedule the CA CMDB Export report and copy the report-generated XML file into the CA CMDB computer and execute the GRLoader manually.
• If CA CMDB and CA Business Intelligence are not installed on the same computer, run GRLoader remotely to configure GRLoader on the CA Business Intelligence computer, and configure BOXI_GRLoader to schedule the program object to execute the GRLoader
• If CA CMDB and CA Business Intelligence are on the same computer, configure BOXI_GRLoader.jar.