Functional 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 Orchestrator, the managed servers are automatically registered or deleted from BMC BladeLogic Server Automation. When Resource Orchestrator and BMC BladeLogic Server Automation 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 Orchestrator's cloning function and BMC BladeLogic Server Automation'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 Server Automation processes and process results resulting from execution of coordination are displayed as Resource Orchestrator processes in the recent operations area of the ROR console.
Resource Orchestrator processes are given priority in the order of execution. If Resource Orchestrator processes terminate abnormally, BMC BladeLogic Server Automation processes will not be executed.
If Resource Orchestrator processes are completed normally, but BMC BladeLogic Server Automation processes terminate abnormally, they will be displayed as errors in the recent operations area of the ROR console.
Check the details of BMC BladeLogic Server Automation processes that terminated abnormally on the Server Automation console of BMC BladeLogic Server Automation, and take corrective action referring to the BMC BladeLogic Server Automation manual.
Coordination of managed server registration
When managed server registration is performed due to automatic registration of Resource Orchestrator agents, server registration with BMC BladeLogic Server Automation 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 Server Automation 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 Server Automation.
If Resource Orchestrator processes are completed normally, but BMC BladeLogic Server Automation processes terminate abnormally, they will be displayed as errors in the recent operations area of the ROR console. In such cases, as status is one where the physical server has been registered with Resource Orchestrator 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 Orchestrator, the server will automatically be deleted from BMC BladeLogic Server Automation.
If Resource Orchestrator processes are completed normally, but BMC BladeLogic Server Automation processes terminate abnormally, they will be displayed as errors in the recent operations area of the ROR console. In such cases, as server deletion from Resource Orchestrator is complete, perform server deletion for BMC BladeLogic Server Automation using the Server Automation console.
Coordination of cloning and software deployment
By preparing software application batch jobs with BMC BladeLogic Server Automation in advance, software deployment settings are performed.
After deployment of cloning images using Resource Orchestrator, as well as automatic registration with BMC BladeLogic Server Automation, the batch job registered with BMC BladeLogic Server Automation will be executed.
If Resource Orchestrator processes are completed normally, but BMC BladeLogic Server Automation processes terminate abnormally, they will be displayed as errors in the recent operations area of the ROR console. In such cases, as image deployment from Resource Orchestrator is complete, execute the software deployment batch job for BMC BladeLogic Server Automation using the Server Automation console.
Installing BMC BladeLogic Server Automation
Install BMC BladeLogic Server Automation referring to the BMC BladeLogic Server Automation manual. The following are advisory notices regarding coordination with Resource Orchestrator.
Installation Order
The order of installation of Resource Orchestrator and BMC BladeLogic Server Automation is not important. Therefore, you can install in any order you like.
Manager Installation
It is possible to install the Resource Orchestrator manager and Application Server (the BMC BladeLogic Server Automation manager) on the same server or on separate servers.
Note
When registering BMC BladeLogic Server Automation with Resource Orchestrator as server management software, it is recommended to install it on the same server. However, when operating Resource Orchestrator managers in clusters, it is recommended to install in on a different server.
Required Coordination Components
When the Resource Orchestrator manager and Application Server are installed on separate servers, please install the BMC BladeLogic Server Automation console on the server on which the Resource Orchestrator manager has been installed.
Setup Procedure
Coordination can be performed after processing of Resource Orchestrator, by executing BMC BladeLogic Server Automation functions by using the coordination script. Before using the coordination script, use the following procedure to perform settings for BMC BladeLogic Server Automation and the coordination script.
Common Settings
Settings for BMC BladeLogic Server Automation
Perform settings for managed server name resolution.
On BMC BladeLogic Server Automation, 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 Orchestrator 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 Server Automation will fail.
In order to avoid the above problem, in "Server name after deployment" set a server name that can be resolved.
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.
In the property dictionary, create an integer type property named "CLONING_DEPLOY" as a property of the server, setting the default value to "0".
Create a server smart group named "CLONING_DEPLOY" in the [Servers] 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 Orchestrator
Change the extension of the script for coordination.
The script for coordination can be found in the following location:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\scripts
[Linux Manager]
/etc/opt/FJSVrcvmr/scripts
Based on the functions being used, change the extension of the file named "sample" to "bat".
Function | File name (excluding extension) |
|---|---|
Server registration | post_register_server |
Server deletion | post_delete_server |
Cloning image deployment | post_cloning_deploy |
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 authentication 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 Server Automation 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 Orchestrator.
Edit the script for coordination "post_cloning_deploy.bat", and specify the batch job created for software deployment using BMC BladeLogic Server Automation.
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.
