Setting user options

Set the user options you require for each user on a workstation in the useropts file. Changes do not take effect until HCL Workload Automation is stopped and restarted.

The useropts file contains values for localopts parameters that must be customized for an individual user. Both files are located in the user_home/.TWS directory of the user. When HCL Workload Automation needs to access data from the localopts file, it looks first to see if the property it requires is stored also in the useropts file for the current user. The value specified in the useropts file always takes precedence over the value in the localopts file. If a property is not specified when invoking the command that requires it, or in the useropts and localopts files, an error is displayed.

The main use of the useropts file is to store the user-specific connection parameters for accessing the command line client, for example conman or composer.

You can define authentication using either the username and password parameters or the JWT parameter:

username: User name used to access the master domain manager. The user must be defined in the security file on the master domain manager. For more information, see Configuring user authorization (Security file).
password: Password used to access the master domain manager. The presence of the ENCRYPT or AES label in the password field indicates that the specified setting has been encrypted; if this label is not present, you must exit and access the interface program again to allow the encryption of that field.
JWT: JSON Web Token (JWT) used to access the master domain manager. The JWT parameter always takes precedence over the username and password parameters. If it is incorrect, the connection does not take place, even if the username and password parameters are present and correct. You retrieve the JWT from the Dynamic Workload Console.

Note that these parameters are not stored in the localopts file.

For more information, see Configuring command-line client access authentication.

A useropts file is created for the TWS_user during the installation, but you must create a separate file for each user that needs to use user-specific parameters on a workstation.