If a system from which BMC BladeLogic Configuration Manager deploys software is available on the network and you have installed an EPI agent to interact with it, software can be deployed from it directly to newly provisioned machines. The requesting user can select which software to deploy or the blueprint can contain the specific jobs to be deployed on all machines provisioned from that blueprint.

Prerequisites

  • Install an EPI Agent for BMC BladeLogic

  • Log in to the vRealize Automation EPI/BMC Agent host as a system administrator.

  • As the system administrator under which the EPI agent is running, log in to the BladeLogic console to configure the authentication profile to be used and to accept any BladeLogic security certificates, and then close the console. This prerequisite is required only once.

Procedure

  1. Select Start > Administrative Tools > Services, and stop the vRealize Automation EPI/BMC Agent service.
  2. On the EPI agent installation host, which could be the same as the Manager Service host, change to the EPI agent installation directory, typically %SystemDrive%\Program Files (x86)\VMware\vCAC Agents\agent_name.
  3. Edit every file in the Scripts\nsh folder in the EPI agent directory and under the parameter list section of each .nsh file, update the values for the following variables. The description of each variable appears above the variable definitions.

    USERNAME_USER=BLAdmin

    AUTH_TYPE=SRP

    PASSWORD_USER=password

    APP_SERVER_HOST=bladelogic.dynamicops.local

    ROLE_NAME=BLAdmins

  4. Edit the agent configuration file, VRMAgent.exe.config, in the EPI agent installation directory and replace CitrixProvisioningUnregister.ps1 with DecomMachine.ps1.
    1. Locate the following line.
      <DynamicOps.Vrm.Agent.EpiPowerShell
        registerScript="CitrixProvisioningRegister. ps1"
        unregisterScript="CitrixProvisioningUnregister.ps1"/>
    2. Change the line to match the following line.
      <DynamicOps.Vrm.Agent.EpiPowerShell
        registerScript="CitrixProvisioningRegister. ps1"
        unregisterScript="DecomMachine.ps1"/>
  5. If you intend to provision by cloning with a static IP address assignment, you can enable BMC BladeLogic registration of provisioned machines by IP address rather than by machine name.
    1. Edit the files InstallSoftware.ps1 and DecomMachine.ps1 in theScripts folder in the EPI agent directory and change the line $byip=$false to $byip=$true. edit the files InstallSoftware.ps1 and DecomMachine.ps1 in the Scripts folder in the EPI agent directory and change the line $byip=$false to $byip=$true.
    2. If you enable registration by IP address by making the above change, you must provision by using static IP address assignment, otherwise, BMC BladeLogic integration fails.
  6. Select Start > Administrative Tools > Services to start the EPI/BMC agent service (vRealize Automation Agent – agentname service).
  7. Place all the BMC BladeLogic jobs you want available to be selected by machine requestors or specified by blueprint creators under a single location within BMC BladeLogic Configuration Manager, for example, /Utility.
  8. If you want to make software jobs available to the requesting user for selection on a per machine basis, create a file named Software.txt in the Web site directory under the vRealize Automation server install directory, typically %SystemDrive%\Program Files(x86)\VMware\vCAC\Server\Website. Each line of the Software.txt file must be in the following format: job_name=job_type=job_path Job, where the following substitutions must be made.

    Variable

    Description

    job_name

    Name of the software job to be presented to the machine requestor.

    job_type

    Numeral that represents the BMC BladeLogic job type.

    job_path

    Location of the job within BMC BladeLogic.

    The following job types are available for BMC BladeLogic Operations Manager 7.6.0.115.

    Job Type Number

    Job Type

    1

    AuditJob

    2

    BatchJob

    3

    ComplianceJob

    4

    DeployJob

    5

    FileDeployJob

    6

    NSHScriptJob

    7

    PatchAnalysisJob

    8

    SnapshotJob

    In addition to the jobs available for BMC BladeLogic Operations Manager 7.6.0.115, BMC Server Automation Console 8.2 includes the following job types.

    Job Type Number

    Job Type

    9

    ACLPushJob

    10

    PatchingJob

    11

    UpdateServerPropertyJob

    For example, to give the requestor a choice of two software deployment jobs and two file deploy jobs, you might create a Software.txt file that contains the following specifications:

    Notepad++=4=/Utility/Notepad++ Job
    Putty=4=/Utility/Putty Job
    Red Hat Shell Scripts=5=/Utility/RHELScripts Job
    Knowledge Base Library=5=/Utility/KBLibDec11 Job
  9. Prepare a reference machine and convert it to a template for cloning.
    1. Install a BMC BladeLogic agent that points to the server on which BMC BladeLogic Configuration Manager is running.
    2. Verify that you are able to connect to the agent on the guest and successfully execute jobs as expected after provisioning.

Results

Tenant administrators and business group managers can now integrate BMC BladeLogic into clone blueprints. See Add BMC BladeLogic Integration to a Blueprint.