Managing multiple Workload Automation environments

During the installation, to enable Clara interaction with multiple Workload Automation environments, you must properly configure the CLARACONFIGWA keyword in the <BUILD_DIR>/clara/config/Clara-WA.env.TEMPLATE file. For Workload Automation for z, configure the CLARACONFIGWAZ keyword.

This keyword contains a json object (envs) with informations about the different Workload Automation environments. See the examples below.

 

After Clara installation, if a re-configuration is needed  (for example to integrate Clara in the Dynamic Workload Console), or you want to enable Clara interaction with additional Workload Automation environments, you must modify the .env file created during the installation process and located in the folder <BUILD_DIR>/clara.

After you have modified the .env file, run the following command to activate the updates:

clara.sh --up --nc

 

In Example 1, envs contains only one environment named WA-PROD.

 

Example 1

 

For Workload Automation:

CLARACONFIGWA = '{"envs": { "WA-PROD": {"ip": "mdm-host.example.com", "port": "31116",  "engineId": "engine_wa-server", "dwcGrp":"DWC-1"}}, "dwcEnvsGrp":{ "DWC-1":{"dwcIp":"dwc-host.example.com", "dwcPort": "16311"}}, "license" : {"licenseServer":"https\://hclsoftware.compliance.flexnetoperations.com/instances/", "licenseID" : "38K36F2YXS18"}, "tkt_url":"https://servicenow.com", "product":"WA"}'

 

 

For Workload Automation for z:

CLARACONFIGWAZ = '{"envs": { "WA-PROD": {"engineId": "engine_wa-server", "dwcGrp":"DWC-1"}}, "dwcEnvsGrp":{ "DWC-1":{"dwcIp":"dwc-host.example.com", "dwcPort": "16311"}}, "license" : {"licenseServer":"https\://hclsoftware.compliance.flexnetoperations.com/instances/", "licenseID" : "38K36F2YXS18"}, "tkt_url":"https://servicenow.com", "product":"WAz"}'

 

If you want to add another environment, you must add another element with all the requested information. In Example 2, envs contains two environments named Bot1 and Bot2.

 

Example 2

 

For Workload Automation:

CLARACONFIGWA = '{"envs": { "Bot1": {"ip": "54.89.190.168", "port": "", "engineId": "engine_waadmin", “dwcGrp”: ”dwcGroup1”}, "Bot2": {"ip": "192.168.1.15", "port": "",  "engineId": "engine_waadmin"}}, "dwcEnvsGrp":{ “dwcGroup1”:{"dwcIp":”localhost”, "dwcPort": ""}},"product":"WA", "license" : {"licenseServer":"https\://flex1513-uat.compliance.flexnetoperations.com/instances/" , "licenseID" : "38K36F00XS18"},"tkt_url":"https://servicenow.com"}'

 

 

For each environment, you specify the following information: 

 

In addition to the envs json object, the dwcGrp json object can also be configured.

The dwcGrp json object defines one or more groups to set the connection to the Dynamic Workload Console. For each group, you must specify the following information:

 

Moreover, you specify:

 

In the dwcGRP json, if you set “default” as groupName, all the envs that do not have dwcGrp specified will get the default connection. See the following example.

 

 

Example 3

 

For Workload Automation:

CLARACONFIGWA = '{"envs": { "Bot": {"ip": "localhost", "port": "", "engineId": "engine_waadmin"}}, "dwcEnvsGrp":{ “default”:{"dwcIp":”localhost”, "dwcPort": ""}},"product":"WA", "license" : {"licenseServer":"https\://flex1513-uat.compliance.flexnetoperations.com/instances/" , "licenseID" : "38K36F11XS18"},"tkt_url":"https://servicenow.com"}'