Installing BMC BladeLogic configuration automation applications

This topic explains how to install BMC BladeLogic Network Automation and BMC BladeLogic Client Automation.

• #Installing BMC BladeLogic Network Automation
• #Installing BMC BladeLogic Client Automation
• #Configuring the BMC BladeLogic Client Automation database
• #Installing BMC BladeLogic Client Automation Configuration Discovery Integration
• #Providing access to BMC Remedy ITSM from BMC BladeLogic Client Automation user accounts
• #Providing access to BMC BladeLogic Client Automation from BMC Remedy ITSM user accounts

Installing BMC BladeLogic Network Automation

1. Perform the installation of the BMC BladeLogic Network Automation server. 

   Warning

   Note

   You must create a local user account for the BMC BladeLogic Network Automation services and FTP/SCP configuration file transfers.

2. Perform integrations with BMC Remedy AR System and BMC Atrium CMDB.

Installing BMC BladeLogic Client Automation

1. Install the BMC BladeLogic Client Automation master transmitter and console.
2. Choose the additional channels that you want to install.
    If you use BMC BladeLogic Client Automation Configuration Discovery Integration, you must install the following channels:
   • CMS
   • Transmitter
   • Infrastructure Service
   • Report Center
   • Scanner Service
   • Schema Manager

Configuring the BMC BladeLogic Client Automation database

1. Ensure that the correct type of database is used:
   • (Microsoft Windows) Microsoft SQL Server 2005 SP2 is used as the BMC BladeLogic Client Automation database.
   • (UNIX) Oracle Database 10g is used as the BMC BladeLogic Client Automation database.

2. Set up the inventory database. 

   Warning

   Note

   In Tuner, ensure that Schema Manager and Report Center are running. If Schema Manager and Report Center are running, you can select them.

3. To normalize your BMC BladeLogic Client Automation data with the Product Catalog, perform the following steps to configure access. For details, see the BMC Atrium Core Product Catalog and DML Guide.
   1. For Product Catalog integration, set up the database links from both the BMC Remedy AR System database and the BMC Configuration Management (BMC CM) database.

   2. From the BMC BladeLogic Client Automation console, download and run the BMC Remedy AR System security scripts. 

      Warning

      Note

      Use the MSSql_installSecurityScript_Unicode.sql script if the SQL Server AR System database was installed with the Unicode option set to on, the columns are of Unicode data type nvarchar, and the ODBC driver does not automatically translate data. The MSSql_installSecurityScript_Unicode.sql script rewrites the views by casting the Unicode nvarchar types to the varchar datatype, allowing successful population of the CM database columns.

   3. Configure parameters for the BMC CM database. 

      Warning

      Note

      Any time you change AR System settings in CMS, restart CMS or the tuner.

   4. Establish a connection between the CM and BMC Remedy AR System databases. 

      Success

      Tip

      To verify connectivity to the Product Catalog using Report Center Query Library, run one of the predefined queries. For details, see the Service Management integration section of Appendix I, "Query Library list," in the BMC BladeLogic Client Automation Report Center Guide.

4. Install BMC BladeLogic Client Automation views by using the following steps:
   1. From the Schema Manager, connect to the BMC CM database.
   2. Install the CMDB Integration with Configuration Discovery schema.
5. In the Report Center, enable and configure the Inventory plug-in.
    For instructions about enabling and configuring the Inventory plug-in, see the "Updating Report Center and the Inventory and Logging plug-ins" section of the BMC BladeLogic Client Automation Report Center Guide.

Installing BMC BladeLogic Client Automation Configuration Discovery Integration

For Configuration Discovery data to populate BMC Atrium CMDB, install BMC BladeLogic Client Automation Configuration Discovery Integration.

1. Stop the BMC Atrium Integration Engine service.
2. Install BMC BladeLogic Client Automation Configuration Discovery Integration.
    For instructions about installing and configuring the integration, see the "Installing the integration" chapter of the BMC Configuration Management Configuration Discovery Integration for CMDB Implementation Guide.
3. Restart the BMC Remedy Action Request System service and the BMC Atrium Integration Engine service.
   During installation, BMC BladeLogic Client Automation Configuration Discovery Integration creates data exchanges and data mappings in BMC Atrium Integration Engine for the 16 CI classes and relationship classes that are discoverable by BMC BladeLogic Client Automation, as well as data deletion and BMC_ComputerSystem relationships information.
    In the BMC Configuration Automation for Clients Configuration Discovery Integration for CMDB Implementation Guide, see Appendix B, "Using BMC Atrium Integration Engine relationship class mappings," for more information about the data mappings.
    For more information about creating data mappings and data exchanges, see the BMC Atrium Integration Engine User's Guide.

4. From BMC Atrium CMDB, manually run the Configuration Discovery Reconciliation Process job to reconcile your Configuration Discovery data with the BMC_Asset dataset. 

   Warning

   Note

   You should also create a schedule for the Configuration Discovery Reconciliation Process job so that it can reconcile your Configuration Discovery data after each transfer. By default, the job has no scheduled runs.

Providing access to BMC Remedy ITSM from BMC BladeLogic Client Automation user accounts

1. Ensure that you have installed and configured BMC BladeLogic Client Automation Configuration Discovery Integration. 

   Warning

   Note

   Ensure that your environment has a directory service enabled.

2. Configure BMC BladeLogic Client Automation to use the directory service for user authentication in User Authentication > User Authentication Type:
   1. Log on to the BMC CM console and select Applications > Console > System Settings.
   2. select the User Authentication tab.
   3. On the User Authentication Settings page, click the User Authentication Type link.
   4. Set the User Authenticate Type to Directory Service.
3. From Schema Manager, connect to the directory service and install the Policy Manager schema.
    This action generates a script that you need on the directory service server.
4. Configure Deployment Manager to use the BMC BladeLogic Client Automation database.
    The Deployment Manager is located, for example, at http://<deploymentManagerHost>:<deploymentManagerPort>, with a default port number of 8000.
5. Configure Deployment Manager to use the directory service for user authentication.
6. Configure console settings to enable Report Center integration.
7. Create a user in the directory service in cn=Users that is accessible by BMC BladeLogic Client Automation, Deployment Manager, and CMS.
8. Configure the master transmitter to use the Product Catalog by editing the settings in the AR System tab.

Providing access to BMC BladeLogic Client Automation from BMC Remedy ITSM user accounts

1. Ensure that BMC BladeLogic Client Automation is installed.
2. Replace cms host:port with the actual value for the CMS host and port in both of the following files:
   • CAICMS_SSOWebService.xml
   • CMSTSM_PolicyManager.xml
3. Use BMC Remedy Administrator to import the changed XML definitions to the BMC Remedy AR System server.
4. In the BMC Remedy AR System server, configure the ARDBC LDAP plug-in to use the directory services of BMC BladeLogic Client Automation.
   For instructions about configuring the ARDBC LDAP plug-in, see the "ARDBC LDAP plug-in" section of the BMC Remedy Action Request System Integration Guide.
5. In BMC Remedy Administrator, modify the form properties for LDAP:Users and LDAP:Groups so that they use the directory services server.
6. Create a directory services user.
   For the purposes of integration, you must create the following types of users in the CTM:People form to use the Change Management application.
   • CMS AR System User — This is a single special user created for the integration.
   • Change Management Users — These are regular users created for the Change Management application.
      For both users, you must use the same user name and password combination in the Configuration Management and Change Management applications. Therefore, you must create users in CTM:People that match the user name and password combinations that have access to CMS in LDAP.
7. Provide the CMS Host and DM Host names and set the status to Active.
   This step creates links between the BMC BladeLogic Client Automation system, Change Management, and Task Management System.
8. For the integration to be complete, you must perform the following actions:
   • Edit the Directory Service or Remedy Integration to include the CMS AR System User with exactly the same user name and password.
      For instructions about editing directory services, see the "Adding or editing a directory service" section of the BMC Configuration Automation for Clients CMS and Tuner Guide.
     
   • Ensure that the user has appropriate roles to perform configuration management tasks. Verify that correct roles are available in BMC BladeLogic Client Automation.
      For information about user roles, see the "What are user roles?" section of the BMC Configuration Automation for Clients CMS and Tuner Guide.
     
   • Configure the mid tier, BMC Remedy AR System database, and Java runtime settings. For instructions about these procedures, see the following guides:
     • Mid tier — See the "Configuring the mid tier" chapter of BMC Remedy AR System BMC Remedy Mid Tier Guide.
       
     • BMC Remedy AR System database — See the "Server information-Database tab" section of BMC Remedy Action Request System Configuration Guide.
       
     • Java runtime settings — See the "Run-time configuration" section of the BMC Remedy Action Request System Integration Guide.