Visual Basic scripts are run outside of vRealize Automation as additional steps in the machine life cycle and can be used to update the custom property values of machines. Visual Basic scripts can be used with any provisioning method.
For example, you could use a script to generate certificates or security tokens before provisioning and then use those certificates and tokens in provisioning a machine.
This information does not apply to Amazon Web Services.
When executing a Visual Basic script, the EPI agent passes all machine custom properties as arguments to the script. To return updated property values to vRealize Automation, you must place these properties in a dictionary and call a function provided by vRealize Automation.
The sample Visual Basic script PrePostProvisioningExample.vbs is included in the Scripts subdirectory of the EPI agent installation directory. This script contains a header to load all arguments into a dictionary, a body in which you can include your functions, and a footer to return updated custom properties to vRealize Automation.
The following is a high-level overview of the steps required to use Visual Basic scripts in provisioning:
A system administrator installs and configures an EPI agent for Visual Basic scripts. See Installation and Configuration.
A system administrator creates Visual Basic scripts and places them on the system where the EPI agent is installed.
Gather the following information for tenant administrators and business group managers for each Visual Basic script:
The complete path to the Visual Basic script, including the filename and extension. For example, %System Drive%Program Files (x86)\VMware\vCAC Agents\EPI_Agents\Scripts\SendEmail.vbs.
A fabric administrator can create a build profile by using the property sets ExternalPreProvisioningVbScript and ExternalPostProvisioningVbScript to provide this required information. Doing so makes it easier for tenant administrators and business group managers to include this information correctly in their blueprints.
Tenant administrators and business group managers use custom properties in their blueprints to call the Visual Basic scripts.