How do I connect to the license server if the master domain manager is using a proxy server?

How to connect to the license server using a proxy server.

About this task

Managing your licenses requires an Internet connection, but your master domain manager is located on a network without Internet access. In this case, you can set up a proxy server and indicate the specifics of the proxy server when installing HCL Workload Automation. If you cannot set up a proxy server, see How do I install a master domain manager to reach the license server with no Internet connection?.

To configure HCL Workload Automation to communicate with the proxy server, perform the following steps:

Procedure

  1. Set up the proxy server according to the specifics of your environment.
  2. Log in as root or Administrator to the workstation where you plan to install the master domain manager.
  3. Browse to the folder where the serverinst command is located in image_location/TWS/interp_name.
  4. Start the installation specifying proxy details in addition to the typical set of parameters. In this case, default values are used for all remaining parameters:
    On Windows operating systems
    cscript serverinst.vbs --acceptlicense yes --rdbmstype <db_type>
    --dbhostname <db_hostname> --dbport <db_port> --dbname <db_name>
    --dbuser <db_user> --dbpassword <db_password> --wauser <wa_user>
    --wapassword <wa_password> --wlpdir <Liberty_installation_dir>\wlp
    [--sslkeysfolder <certificate_files_path>] [--sslpassword <keystore_truststore_password>]
    --licenseserverid <license_server_ID> --licenseproxyserver <license_proxy_server> 
    --licenseproxyport <license_proxy_port> [--licenseproxyuser <license_proxy_user> 
    --licenseproxypassword <license_proxy_password>]
    On UNIX operating systems
    ./serverinst.sh --acceptlicense yes --rdbmstype <db_type>
    --dbhostname <db_hostname> --dbport <db_port> --dbname <db_name>
    --dbuser <db_user> --dbpassword <db_password> --wauser <wa_user>
    --wapassword <wa_password> --wlpdir <Liberty_installation_dir>/wlp
    [--sslkeysfolder <certificate_files_path>] [--sslpassword <keystore_truststore_password>]
    --licenseserverid <license_server_ID> --licenseproxyserver <license_proxy_server> 
    --licenseproxyport <license_proxy_port> [--licenseproxyuser <license_proxy_user> 
    --licenseproxypassword <license_proxy_password>]
    where
    --acceptlicense
    Specify yes to accept the product license.
    --rdbmstype|-r rdbms_type
    The database type. Supported databases are:
    • DB2
    • ORACLE
    • MSSQL This value applies to MSSQL,Azure SQL and Google Cloud SQL for SQL server.
    • IDS This value is supported only on UNIX operating systems. and applies to Informix.
    • ONEDB This value is supported only on UNIX operating systems.
    This parameter is optional. The default value is DB2.
    --dbhostname db_hostname
    The host name or IP address of database server.
    --dbport db_port
    The port of the database server.
    --dbname db_name
    The name of the HCL Workload Automation database.
    --dbuser db_user
    The database user that has been granted access to the HCL Workload Automation tables on the database server.
    --dbpassword db_password
    The password for the user that has been granted access to the HCL Workload Automation tables on the database server.
    --wauser user_name
    The user for which you are installing HCL Workload Automation.
    --wapassword wauser_password
    The password of the user for which you are installing HCL Workload Automation.
    On Windows operating systems
    Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?*~+.
    On UNIX operating systems
    Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?=*~+.
    --wlpdir
    The path where WebSphere Application Server Liberty Base is installed.
    --licenseserverid
    The ID of the license server which processes license usage information. This parameter is required. For more information about enabling your product license, see Enabling product license management. For more information about creating and setting up the license server, see What is the HCL License & Delivery Portal (FlexNet Portal)?
    --licenseproxyserver
    The IP address of the proxy used to connect to the license server.
    --licenseproxyport
    The port on which to contact the proxy used to connect to the license server.
    --licenseproxyuser
    The username for authenticating to the proxy used to connect to the license server.
    --licenseproxypassword
    The password for authenticating to the proxy used to connect to the license server.
    --sslkeysfolder
    The name and path of the folder containing either the keystore (TWSServerKeyFile.jks) and/or truststore (TWSServerTrustFile.jks) files (only on UNIX operating systems), or certificates in .PEM format:
    • Only on UNIX operating systems, if you provide the keystore and truststore files, these files are used to configure SSL communication using the passwords you provide with the --keystorepassword and --truststorepassword respectively.
    • If you provide .PEM certificates, the installation program generates the keystore and truststore files using the password you specify with the --sslpassword parameter.
    This parameter is required if you set the --dbsslconnection parameter to true.
    --sslpassword
    If you provide .PEM certificates with the --sslkeysfolder parameter, this is the password for the certificates automatically generated by the installation program. This parameter is mutually exclusive with the --keystorepassword and --truststorepassword parameters, which apply when you provide the keystore and truststore files using the --sslkeysfolder parameter.
    Note: The values for the following parameters must match the values you provided when creating and populating the database:
    • --rdbmstype
    • --dbhostname
    • --dbport
    • --dbname
    • --dbuser
    • --dbpassword
    See Creating and populating the database, then follow the link to the database vendor you are using for more information about command parameters.
    You have now successfully installed the master domain manager and set it up to communicate with the proxy server.