7.3

Table Of Contents
Installation can take a long time depending on the deployment size. Again, locate the command ID,
and use the aggregated status GET command to obtain installation progress. The GET response
might resemble the following example.
"progress": "78%", "counts": {"failed": 0, "completed": 14, "total": 18,
"queued": 3, "processing": 1}, "failed-commands": 0
n
If something goes wrong with the installation, you can trigger log collection for all nodes using the
following command.
PUT /commands/log-bundle
Similar to installation, the returned alphanumeric command ID lets you monitor log collection status.
Convert Between vRealize Automation Silent Properties
and JSON
For silent vRealize Automation CLI or API based installations, you can convert a completed properties
answer file to JSON or vice versa. The silent CLI installation requires the properties file, while the API
requires JSON format.
Prerequisites
A completed properties answer file or completed JSON file
/usr/lib/vcac/tools/install/ha.properties
or
/usr/lib/vcac/tools/install/installationProperties.json
Procedure
1 Log in to a vRealize Automation appliance console session as root.
2 Run the appropriate converter script.
n
Convert JSON to Properties
/usr/lib/vcac/tools/install/convert-properties --from-json
installationProperties.json
The script creates a new properties file with the timestamp in the name, for example:
ha.2016-10-17_13.02.15.properties
n
Convert Properties to JSON
/usr/lib/vcac/tools/install/convert-properties --to-json ha.properties
The script creates a new installationProperties.json file with the timestamp in the name,
for example:
installationProperties.2016-10-17_13.36.13.json
Installing vRealize Automation
VMware, Inc. 129