POST /lcm/api/v1/action/add/product?id={environmentId} adds a vRealize Suite product to an existing environment.

Prerequisites

Satisfy the following conditions before performing any tasks for this use case.

  • Use POST /lcm/api/v1/login to log in to vRealize Suite Lifecycle Manager.

  • Verify that you have a valid authentication token that matches your login credentials. See Request an Authentication Token.

curl Command

The following example adds vRealize Business for Cloud to the specified environment.

curl -X POST "http://localhost:8000/lcm/api/v1/action/add/product?id=78b45f299cbdc2755585cc2bb88f8" \
        -H "accept: application/json" \
        -H "x-xenon-auth-token: $token" \
        -H "content-type: application/json" \
        -d '{
           "id": "vrbc",
           "version": "7.3.0",
           "clusterVIP": [],
           "properties": {
             "currency": "USD - US Dollar"
           },
           "nodes": [
             {
               "sourceLink": "",
               "type": "vrb-server",
               "properties": {
                 "esxHost": "$esxHostFQDN",
                 "guestFullName": "SUSE Linux Enterprise 12 (64-bit)",
                 "ipAddress": "$ipAddress",
                 "cpu": "4",
                 "vCenterHost": "$vCenterHostFQDN",
                 "ssoTenant": "vsphere.local",
                 "storage": "FC-LUN-15 TB",
                 "userName": "[email protected]",
                 "productName": "vRealize Business for Cloud",
                 "network": "infra-traffic-1006",
                 "isTelemetryEnable": "true",
                 "hostname": "$hostname",
                 "password": "$password",
                 "productVersion": "7.2.1.10029 Build 5101870",
                 "powerState": "poweredOn",
                 "cafeHost": "$cafeHost",
                 "memoryInMb": "8192",
                 "name": "S2-vrb-server",
                 "vrbRootPassword": "$vrbRootPassword"
               }
             }
           ]
         }'

JSON Output

The following JSON output is returned when the operation completes successfully.

200 Operation successful