HCL Workload Automation, Version 9.4

exportserverdata

Use the exportserverdata command to download the list of dynamic workload broker instances from the HCL Workload Automation database and change a port number or a host name.

Syntax

exportserverdata ?

exportserverdata -dbUsr db_user_name -dbPwd db_user_password -exportFile filename

Description

This command extracts a list of URIs (Uniform Resource Identifier) of all the dynamic workload broker instances from the HCL Workload Automation database and copies them to a temporary file so that, if either the hostname or the port number of any of the instances listed are changed, the administrator can record this information in the file and place it back in the database with the importserverdata command. By default, the list of URIs is saved to the server.properties file, located in the current directory.

This action is necessary because the list of dynamic workload broker instances must be kept up-to-date at all times, since the Resource Advisor agents periodically connect to the active instance to send their data about the resources discovered in each computer. They are able to automatically switch between the instances of this list and find the active one to copy these data in its Resource Repository. Since the master domain manager and every backup master are installed with a dynamic workload broker instance, the active dynamic workload broker instance runs in the master domain manager, while an idle instance resides in each backup master.

The URI pointing to each dynamic workload broker instance is the following:
https://hostname:port_number/JobManagerRESTWeb/JobScheduler
You can change only the hostname and the port number.
Important: The list is ordered. You can change the order of the instances as they appear in this list, and the agents will follow this order. If you have several backup masters and decide to follow a specific switching order when a master fails, you can instruct the agents to switch to the right instance using this ordered list, speeding up the transition time.

If your HCL Workload Automation database is DB2 and you use FIPS security, to run this command successfully you need to have the com.ibm.tdwb.dao.rdbms.useSSLConnections option set to TRUE in the CLIConfig.properties file.

Options

?
Displays help information.
-dbUsr db_user_name
The user name required to access the HCL Workload Automation database server.
-dbPwd db_user_password
The user password required to access the HCL Workload Automation database server.
-exportFile filename
The name of the temporary file where the URIs extracted from the database are copied for editing. This text file is created when you run the command and you can open it with any editor to change the hostname or the port number. If you do not specify a path, the file is created in the same directory where the command is located, that is:
<TWA_home>/TDWB/bin
If you do specify a different path, make sure the path exists before you run this command.

Example

To download the current list of all (active and backup) dynamic workload broker instances and copy them in a file named c:\myservers\uris160709, run:
exportserverdata -dbUsr twsadm -dbPwd fprefect -exportFile c:\myservers\uris160709
The command returns file uris160709, that looks like this:
https://accrec015:42127/JobManagerRESTWeb/JobScheduler
https://prodop099:52529/JobManagerRESTWeb/JobScheduler
https://prodop111:31116/JobManagerRESTWeb/JobScheduler
prodop099 is the active dynamic workload broker instance because is hosted by the currently active master domain manager, whereas accrec015 and prodop111 are idle because they are hosted by backup masters.

You can edit this file to apply your changes before using the importserverdata command to upload the URIs back to the database.

See Also

importserverdata