ServerView Resource Coordinator VE Setup Guide

H.1 Coordination with BMC BladeLogic Operations Manager

This section explains how to coordinate Resource Coordinator VE with BMC's server automation software BMC BladeLogic Operations Manager.

External Software

Resource Coordinator VE can be coordinate with the software in the BMC BladeLogic Operations Manager Suite 8.0 or later.

Function Overview

Through coordination the following becomes possible:

• Coordination of registration and deletion of managed servers

  When registration or deletion of managed servers is performed using Resource Coordinator VE, the managed servers are automatically registered or deleted from BMC BladeLogic Operations Manager. When Resource Coordinator VE and BMC BladeLogic Operations Manager both manage a server in the same environment, this coordination eases the workload of the staff responsible for server registration.

• Coordination of cloning and software deployment

  Coordination of Resource Coordinator VE's cloning function and BMC BladeLogic Operations Manager's software deployment function enables deployment of software to servers installed through cloning. This coordination eases the workload of installing software that cannot be deployed using cloning images (software that saves environment specific information such as MAC addresses on installation) on managed servers.

  
  

Function Details

• Common notes

  • The BMC BladeLogic Operations Manager processes and process results resulting from execution of coordination are displayed as Resource Coordinator VE processes in the recent operations area of the RC console.

  • Resource Coordinator VE processes are given priority in the order of execution. If Resource Coordinator VE processes terminate abnormally, BMC BladeLogic Operations Manager processes will not be executed.

  • If Resource Coordinator VE processes are completed normally, but BMC BladeLogic Operations Manager processes terminate abnormally, they will be displayed as errors in the recent operations area of the RC console.

  • Check the details of BMC BladeLogic Operations Manager processes that terminated abnormally on the Server Automation console of BMC BladeLogic Operations Manager, and take corrective action referring to the BMC BladeLogic Operations Manager manual.

• Coordination of managed server registration

  • When managed server registration is performed due to automatic registration of Resource Coordinator VE agents, server registration with BMC BladeLogic Operations Manager is performed automatically.

  • When agents are not registered automatically during server registration, coordination is not performed. By registering agents after registering servers, server registration with BMC BladeLogic Operations Manager is performed automatically.

  • The computer name set in the OS (for Windows) or the hostname (for Linux) is used as the server name of servers registered with BMC BladeLogic Operations Manager.

  • If Resource Coordinator VE processes are completed normally, but BMC BladeLogic Operations Manager processes terminate abnormally, they will be displayed as errors in the recent operations area of the RC console. In such cases, as status is one where the physical server has been registered with Resource Coordinator VE but the agent is still not registered, resolve the cause of the problem and register the agent again.

• Coordination of managed server deletion

  • When performing deletion of managed servers using Resource Coordinator VE, the server will automatically be deleted from BMC BladeLogic Operations Manager.

  • If Resource Coordinator VE processes are completed normally, but BMC BladeLogic Operations Manager processes terminate abnormally, they will be displayed as errors in the recent operations area of the RC console. In such cases, as server deletion from Resource Coordinator VE is complete, perform server deletion for BMC BladeLogic Operations Manager using the Server Automation console.

• Coordination of cloning and software deployment

  • By preparing software application batch jobs with BMC BladeLogic Operations Manager in advance, software deployment settings are performed.

  • After deployment cloning images using Resource Coordinator VE, as well as automatic registration with BMC BladeLogic Operations Manager, the batch job registered on BMC BladeLogic Operations Manager will be executed.

    
    

Installing BMC BladeLogic Operations Manager

Install BMC BladeLogic Operations Manager referring to the BMC BladeLogic Operations Manager manual. The following are advisory notices regarding coordination with Resource Coordinator VE.

• Installation Order

  The order of installation of Resource Coordinator VE and BMC BladeLogic Operations Manager is not important. Therefore you can install in any order you like.

• Manager Installation

  It is possible to install the Resource Coordinator VE manager and Application Server (the BMC BladeLogic Operations Manager manager) on the same server or on separate servers.

• Required Coordination Components

  When the Resource Coordinator VE manager and Application Server are installed on separate servers, please install the BMC BladeLogic Server Automation console on the server on which the Resource Coordinator VE manager has been installed.

  
  

Setup Procedure

Coordination can be performed after processing of Resource Coordinator VE, by executing BMC BladeLogic Operations Manager functions by using the coordination script. Before using the coordination script, use the following procedure to perform settings for BMC BladeLogic Operations Manager and the coordination script.

Common Settings

• Settings for BMC BladeLogic Operations Manager

  1. Perform settings for managed server name resolution.

     On BMC BladeLogic Operations Manager, servers are registered by specifying the server names. Therefore it is necessary to configure DNS or a hosts file in advance so that registered server names can be resolved from Application Server.

     Note

     When using the Resource Coordinator VE cloning function to install a server, the name of the server can be set in "Server name after deployment" of the "Deploy a Cloning Image" dialog.
     If the server name set in "Server name after deployment" cannot be resolved from Application Server, the coordination process for BMC BladeLogic Operations Manager will fail.
     In order to avoid the above problem, in "Server name after deployment" set a server name that can be resolved.

  2. Connect to Application Server using the Server Automation console and obtain the certificate. When the certificate has already been obtained, this step is not necessary.

     [Windows]
     While logged in as the Administrator, connect to the Application Server.

     Note

     Depending on the language version of Windows, the name of the built-in account for the administrator may not be named "Administrator". In such cases, change the user name of the administrator based on the environment being used.

     [Linux]
     While logged in to the OS as root, connect to the Application Server.

  3. In the property dictionary, create an integer type property named "CLONING_DEPLOY" as a property of the server, setting the default value to "0".

  4. Create a server smart group named "CLONING_DEPLOY" in the [Server] workspace. In the conditions area of the window displayed when creating the smart group, configure the following conditions.

     • Select "Server" from the list, and enter "CLONING_DEPLOY".

     • Select "equals" from the list, and enter "1".

• Settings for Resource Coordinator VE

  1. Change the extension of the script for coordination.

     The script for coordination can be found in the following location:

     [Windows]
     Installation_folder\Manager\etc\scripts

     [Linux]
     /etc/opt/FJSVrcvmr/scripts

     Based on the functions being used, change the extension of the file named "sample" to "bat".

     Table H.1 Coordination Scripts

     Function	File name (excluding extension)
     Server registration	post_register_server
     Server deletion	post_delete_server
     Cloning image deployment	post_cloning_deploy

  2. Settings for connection to Application Server

     Edit the file named "blenv.bat" that is in the same folder as the script for coordination, rewriting the values specified for the following variables based on the connection information for Application Server.

     Variable	Meaning
     PROFILE	The name of the authentification profile used for connection to Application Server
     ID	A user name with authority for executing coordination patch jobs
     PASSWD	The password for the above user

     Note

     • As "blenv.bat" contains connection information for Application Server, protect the connection information using the following method.

       - Secure the admin server.

       - Restrict the authority of the BMC BladeLogic Operations Manager account used for coordination so that only the coordination batch job can be executed.

     [Windows]

     • The following path configured in "blenv.bat" may not exist depending on the language version of Windows being used. In such cases, change the user name of the built-in administrator and the application data storage folder based on the environment being used.

       set BL_SSO_TRUSTED_CERT_KEYSTORE_FILE="C:\Documents and Settings\Administrator\Application Data\BladeLogic\client_keystore.pkcs12.PEM"

Required Settings for Coordination of Cloning and Software Deployment

Perform the following settings for Resource Coordinator VE.

Edit the script for coordination "post_cloning_deploy.bat", and specify the batch job created for software deployment using BMC BladeLogic Operations Manager.
Re-write the values of the following variables as given below.

Variable	Meaning
JOB_GROUP	Job folder name
JOB_NAME	Batch job name

Advisory Notes

When uninstalling the manager, the coordination scripts will not be saved. Therefore back them up if necessary.