Setting up options for using the user interfaces
About this task
To use the Dynamic Workload Console, the connection parameters are supplied within the console and saved as part of its configuration.
- hostname
- The hostname of the master domain manager.
- port number
- The port number used when establishing the connection with the master domain manager.
- user name, password
- The credentials, user name and password, of the TWS_user.
- proxy hostname
- The proxy hostname used in the connection with the HTTP protocol.
- proxy port number
- The proxy port number used in the connection with the HTTP protocol.
- protocol
- The protocol used during the communication. This can be HTTP with basic authentication, or HTTPS with certificate authentication.
- timeout
- The timeout indicating the maximum time the connecting user interface program can wait for the master domain manager response before considering the communication request as failed.
- default workstation
- The workstation name of the master domain manager you want to connect to.
- SSL parameters
- If you have configured your network to use SSL to communicate between the interfaces and the master domain manager, you need also to supply the appropriate set of SSL parameters (which depends on how your SSL is configured.
In the case of the command line client installed on the master domain manager, this configuration is performed automatically at installation.
For the command line client installed on other workstations, this information can be supplied either by storing it in properties files on those workstations, or by supplying the information as part of the command string of the commands you use.
localopts
and useropts
files:- localopts
- This contains a set of parameters applicable to the local workstation for a specific instance of the installed product. See Localopts details
- useropts
- This contains a subset of those localopts parameters that have custom values for a specific
user. The path of this file is within the user's home directory, which maintains the privacy of this
information. See Setting user options for
details about useropts.
Because HCL Workload Automation supports multiple product instances installed on the same machine, there can be more than one
useropts
file instance of each user. The possibility to have moreuseropts
files, having a different name each, provides the ability to specify different sets of connection settings for users defined on more than one instance of the product installed on the same machine.In the
localopts
file of each instance of the installed product the option named useropts identifies the file name of theuseropts
file that has to be accessed to connect to that installation instance.This means that, if two HCL Workload Automation instances are installed on a machine and a system user named
operator
is defined as user in both instances, then in thelocalopts
file of the first instance the local optionuseropts = useropts1
identifies theuseropts1
file containing the connection parameters settings that useroperator
needs to use to connect to that HCL Workload Automation instance. On the other hand, in thelocalopts
file of the second HCL Workload Automation instance the local optionuseropts = useropts2
identifies theuseropts2
file containing the connection parameters settings that useroperator
needs to use to connect to that HCL Workload Automation instance.
Full details of how to configure this access are given in the Administration Guide, in the topic entitled "Configuring command-line client access authentication".