vRealize Automation includes custom properties that you can use to provide additional controls for BMC BladeLogic Configuration Manager integration.

Table 1. Custom Properties Required for BMC BladeLogic Configuration Manager Integrations
Custom Property Description
VirtualMachine.EPI.Type

Specifies the type of external provisioning infrastructure.

VirtualMachine.Admin.Owner

Specifies the user name of the machine owner.

BMC.Software.Install

Set to True to enable BMC BladeLogic Configuration Manager integration.

EPI.Server.Name

Specifies the name of the external provisioning infrastructure server, for example, the name of the server hosting BMC BladeLogic. If at least one general BMC EPI agent was installed without specifying a BMC BladeLogic Configuration Manager host, this value directs the request to the desired server.

If only dedicated BMC EPI agents for specific BMC BladeLogic Configuration Manager hosts were installed, this value must exactly match the server name configured for one of these agents.

BMC.Service.Profile

Specifies the name of the default authentication profile on the BMC BladeLogic server.

BMC.Software.BatchLocation

Specifies the location in BMC BladeLogic configuration where software jobs are deployed. This value must match the appropriate value of Vrm.Software.IdNNNN. For example, a valid value could be /Application Deployment.

VMware.VirtualCenter.OperatingSystem

Specifies the vCenter Server guest operating system version (VirtualMachineGuestOsIdentifier) with which vCenter Server creates the machine. This operating system version must match the operating system version to be installed on the provisioned machine. Administrators can create property groups using one of several property sets, for example, VMware[OS_Version]Properties, that are predefined to include the correct VMware.VirtualCenter.OperatingSystem values. This property is for virtual provisioning.

For related information, see the enumeration type VirtualMachineGuestOsIdentifier in vSphere API/SDK Documentation. For a list of currently accepted values, see the vCenter Server documentation.

Custom Properties To Make BMC BladeLogic Configuration Manager Software Jobs Available

Configure BMC BladeLogic Configuration Manager jobs for vRealize Automation integrations. Make all software jobs available to machine requesters to select from, or specify a software job to apply to all machines provisioned from the blueprint.

Table 2. Custom Properties to Make Software Jobs Available
Custom Property Description
LoadSoftware

Set to True to enable software install options.

Vrm.Software.IdNNNN

Specifies a software job or policy to be applied to all machines provisioned from the blueprint. Set the value to job_type=job_path, where job_type is the numeral that represents the BMC BladeLogic job type and job_path is the location of the job in BMC BladeLogic, for example 4=/Utility/putty. NNNN is a number from 1000 to 1999. The first property must start with 1000 and increment in numerical order for each additional property. 
1 — AuditJob
2 — BatchJob
3 — ComplianceJob
4 — DeployJob
5 — FileDeployJob
6 — NSHScriptJob
7 — PatchAnalysisJob
8 — SnapshotJob

Optional Custom Properties for BMC BladeLogic Configuration Manager Integrations

You can also use optional custom properties that are commonly used with BMC BladeLogic Configuration Manager blueprints.

Table 3. Optional Custom Properties for BMC BladeLogic Configuration Manager Integrations
Property Definition
BMC.AddServer.Delay

Specifies the number of seconds to wait before adding the machine to BMC BladeLogic Configuration Manager. The default is 30.

BMC.AddServer.Retry

Specifies the number of seconds to wait before retrying if the first attempt to add the machine to BMC BladeLogic Configuration Manager is unsuccessful. The default is 100.