HCL Workload Automation, Version 9.4

Backing up the configuration files

The configuration files used by HCL Workload Automation are found in the following places:

<TWA_home>/TWS

For the user options file, useropts.

<TWA_home>/TWS/*.*

For the localopts, Sfinal, Security and *.msg files

<TWA_home>/TWS/mozart/*.*

This directory contains the following files:

runmsgno: This is used for the allocation of unique prompt numbers. On the master domain manager, this file should not be edited manually. On other workstations it can be edited only in the circumstances described in the HCL Workload Automation: Troubleshooting Guide. This file does not need to be backed up.
globalopts: This is used to store a copy of three of the global properties stored in the database. If you have used versions of HCL Workload Automation prior to version 8.3 you will probably remember that it was an editable file that contained the global options. It is no longer used for this purpose. It must be edited only in the circumstances described in Changing a master domain manager. This file should be backed up if it is edited.

<TWA_home>/WAS/TWSprofile/properties

For the application server configuration file, TWSConfig.properties

<TWA_home>/WAS/TWSprofile/config

This contains the other configuration files for the WebSphere Application Server. Do not back them up manually. A utility to back them up is described in Application server - configuration files backup and restore.

<TWA_home>/TWS/schedForecast

For forecast plan files.

<TWA_home>/TWS/schedlog

For archived plan files.

<TWA_home>/TWS/schedTrial

For trial plan files.

A detailed list of all files is not supplied, as there are too many files. Back up all the files in these directories.

Note: The tws_inst_pull_info tool (described in the HCL Workload Automation: Troubleshooting Guide) is provided for sending information to support, but can also be used to perform a backup of a DB2® database and some of the configuration files.