7.4

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 6‑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 6‑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.
IaaS Integration for BMC BladeLogic
VMware, Inc. 16