How do I install a master domain manager to reach the license server with no Internet connection?
How to install a master domain manager to reach the license server with no Internet connection.
About this task
Managing your licenses requires an Internet connection, but your master domain manager must be installed on a network without Internet access. In this case, you can install a Local License Server (LLS).
To install HCL Workload Automation to communicate with the LLS, perform the following steps:
Procedure
- Set up the LLS according to the specifics of your environment.
- Log in as root or Administrator to the workstation where you plan to install the master domain manager.
- Browse to the folder where the serverinst command is located in image_location/TWS/interp_name.
-
Start the installation specifying proxy details in additional 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 --licenseserverid <license_server_ID> --sslkeysfolder <certificate_files_path> --sslpassword <keystore_truststore_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 --licenseserverid <license_server_ID> --sslkeysfolder <certificate_files_path> --sslpassword <keystore_truststore_password>
- --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.
- --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)?
- --sslkeysfolder
- The name and path of the folder containing either certificates in
.PEM format or the keystore
(TWSServerKeyFile.jks) and/or truststore
(TWSServerTrustFile.jks) files (only on
UNIX operating systems):
- If you provide .PEM certificates, the installation program automatically generates the keystore and truststore files using the password you specify with the --sslpassword parameter.
- 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. Note: When installing using the keystore and truststore files, you are required to manually configure these files prior the installation setup. For this reason, this procedure is not recommended.
- ca.crt
- The Certificate Authority (CA) public certificate.
- tls.key
- The private key for the instance to be installed.
- tls.crt
- The public part of the previous key.
You can optionally create a subfolder to contain one or more *.crt files to be added to the server truststore as trusted CA. This can be used for example to add to the list of trusted CAs the certificate of the LDAP server or DB2 server. Additionally, you can store here any intermediate CA certificate to be added to the truststore. The subfolder must be named additionalCAs.
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
You have now successfully installed the master domain manager and set it up to communicate with the proxy server.