Configuring HCL Z and I Emulator for Web with Flexera
This document describes the procedure to acquire a license for using the product ‘HCL Z and I Emulator for Web’ and to configure the product for connecting to a host.
Follow the instructions detailed in each of the below steps :
Step-1 : Download the Product and License Server (CLLS) from FlexNet Operations.
Step-2 : Extract the installers (for the Product and License Manager)
Step-3 : Configure the License Manager and the Product for usage :
Copy the below link and paste it in a browser address bar to access the FlexNet login page.
https://hclsoftware-fno.flexnetoperations.com/flexnet/operations/logon.do?logoff=true
Figure 1: Flexera Login
Enter the authorized login credentials to access the Producer Portal Home page.
Under QuickSearch, select “Products” under Search and “All Products” under For and provide the relevant keywords for finding the required products.
The
below image shows a keyword entered in the search field, to find the
“HCL ZIE Family products”.
Figure 2 : Producer Portal Home (QuickSearch for Products)
If the Search is successful, all the product packages relevant to the entered keyword will be displayed in the Search results.
Figure 3 : Package Products (Search Results)
Select the required Product package from the list (HCL Z and I Emulator for Web 1.0).
In the “Create A product” panel that follows, click on the “Download Packages” tab to view and download the required packages.
The below image shows the options selected for downloading ‘HCL ZIE for Web’ and ‘HCL_CLLS’.
Figure 4 : Package Products (Download Packages)
Click on HCL_CLLS to download the ‘HCL Common Local License Sever 1.0’ package to a User defined location.
Click on HCL_ZIE_for_Web_1.0 to download all the packages related to ‘HCL ZIE For Web v1.0’ to a User defined location.
Open the downloaded package.
For the product HCL Z and I Emulator for Web (ZIEWeb), the downloaded package ‘HCL_ZIE_for_Web_1.0’ will have the following folder structure,
Figure 5 : HCL ZIE for Web product package
Extract the following components:
The ZIEWeb Product Installer from the ZIEWEB folder.
The License Manager Installer (.war and .ear) files from the License Build folder.
In the HCL_CLLS package that is selected, the zipped packages shown in the below image are present. Download the relevant installer, based on your OS specification to connect to the Flexera License server.
Figure 6 : Installer Packages in HCL CLLS
For Windows users, download the HCL_CLLS_WIN_1 package.
For Linux users, download the HCL_CLLS_LNX_1 package.
After the download is completed, extract the package which contains the required jars and .bat files.
The flexnetlsadmin.bat file that is used to connect to the Flexera License server is present in : [Extracted CLLS package]\enterprise.
Once the installers are available, follow the steps given in the below link to configure the Flexera License Server.
Note : You can choose the Server deployment mode as Local or Cloud while setting up the license server.
Figure 7 : Server deployment mode
After completing the License server deployment, you will get a custom Flexera URL.
Use your custom URL to replace the following link given in the upcoming procedures.
<https://[license server host]/api/1.0/instances/[license server ID]>
For further queries related to Flexera setup, contact the HCL Customer support team using the following link : https://hclpnpsupport.hcltech.com/csm
To configure HCL ZIE for Web with the License Server, follow the below steps.
Install any open source key tool (like Open SSL or Java key tool) in the machine for key-pair generation.
Below is the detailed procedure to Configure ZIEWeb with Flexera server using Open SSL:
After installing Open SSL, copy the open SSL folder under C:\ drive.
Configure the Open SSL path in the system environment variables as shown:
Figure 8 : Configuring the Open SSL under system environment variables
The Public/Private key pair generated is used for secure communication. The key pair should be in "RSA 2048-bit" format. The private key format should be "pksc8", and that of the public key should be "DER" format.
The following is the procedure to generate key-pairs using OpenSSL:
(Note: if your using any other third party tool for key-pair generation, you need to follow the instructions provided by them.)
Generate private key.
Open Command Prompt as an Administrator and enter the Open SSL path to change the path from the root directory (C:\OpenSSL\bin). Enter the below command, to generate the private key under C:\OpenSSL\bin,
openssl genrsa -out private_key.pem 2048
Get the public key.
After the private key is generated, enter the below command to generate the public key also in the same path.
openssl rsa -in private_key.pem -pubout -outform DER -out public_key.der
Convert private key to pkcs8 format to use it.
The private_key.pem file should be converted into pcks8 format for strong encryption. To do this conversion, enter the below command,
openssl pkcs8 -topk8 -inform PEM -outform PEM -in private_key.pem -out private_key_pkcs8.pem -nocrypt
Figure 9 : Generated keys under C:\OpenSSL\bin
To connect to the Flexera server, the Extracted CLLS package should be available in the local machine. Navigate to the Flexera folder in the local machine. (D:\ [Extracted CLLS package]\enterprise)
Open the Command Prompt and enter the below command,
flexnetlsadmin.bat -server <https://[license server host]/api/1.0/instances/[license server ID] -authorize admin [license sever admin password] -uploadPublicKey [local path to public key (in DER format)]>
For example:
flexnetlsadmin.bat -server https:// hclsoftware.compliance.flexnetoperations.com/api/1.0/instances/FED321CBA -authorize admin adminpwd -uploadPublicKey C:\temp\public_key.der
If the public key is successfully uploaded to the Flexera server using the above command, user will receive an acknowledgement as “Client public key has been uploaded successfully” from the Flexera server.
(For any queries related to the Flexera setup, contact the HCL Customer support team using the following link : https://hclpnpsupport.hcltech.com/csm)
Enter the below Flexera server command to check the feature description and the total no. of licenses configured for that feature.
C:\Users\Admin\Desktop\Flexera\Others\[Extracted CLLS package]\enterprise\flexnetlsadmin.bat -server <https://[license server host]/api/1.0/instances/[license server ID] / -authorize <username> <password> -licenses -verbose>
For example:
C:\Users\Admin\Desktop\Flexera\Others\[Extracted CLLS package]\enterprise\flexnetlsadmin.bat -server https:// hclsoftware.compliance.flexnetoperations.com/api/1.0/instances/FED321CBA -authorize admin adminpwd -licenses -verbose
Figure 10 : Flexera server command to check Feature description & count of configured licenses
A supported Application server (like WAS or Tomcat) must be installed in the machine.
Deploy the License Manager .ear or .war file in the Application server.
The below image shows the deployment of License Manager using WebSphere Application sever’.
Figure 11 : Deploying License manager file (.ear/.war) in Application server
Click and Open the deployed License Manager application
Configure the context root for the License Manager under: General PropertiesWeb Module Properties Context Root for Web Modules.
Figure 12 : Configuring context root for License Manager (in Web Module Properties)
Configure the Flexera parameter details (in the below panel) for ZIEWEB, under General PropertiesWeb Module Properties Initialize Parameters for servlets.
Figure 13 : Configuring Flexera details (in Web Module Properties)
Provide your custom Flexera URL that was generated in the step detailed in section 3.1.
For example:
https://[license server host]/api/1.0/instances/[license server ID]
Flexera server Private key path for ZIEWEB:
The path where the converted private key in pkcs8 format is stored.
For example:
D:\Flexera\private_key_pkcs8.pem
User Directory:
Path for creating the User Directory, automatically after configuration. This directory will contain all the License Manager related files and Database file.
For example:
D:\LM
After the configuration is completed, launch the HCL ZIE License Manager from a browser using the below URL format
http://<server ip>:<server port no>/<context-root>/LicenseLogger
For example:
http://localhost:9080/ws/LicenseLogger
Figure 14 : HCL ZIE License Manager Login
Note : If you cannot see the HCL ZIE License Manager login page, restart the License Manager application on the Application server where it is deployed.
Login to the License Manager with the default credentials (username: “admin”, password: “password”), and check the Total Active license count. The count will be shown as 0 initially since the downloaded product (ZIEWeb) is not yet configured with the license manager.
Figure 15 : Active License count in License Manager (without configuring License Manager)
The product (HCL ZIE For Web) must be installed in the machine.
Navigate to the product installation directory : C:\Program Files\HCL\ZIEForWeb\ZIEWeb.
Open the config.properties file from the installed path.
Figure 16 : config.properties file in product installation directory
Remove the # symbol before the licenseserverurl parameter, to un-comment the statement and modify the given path with the <application server url:port/context path/LicenseLogger> as highlighted below, to configure the License Server URL.
Figure 17 : Enabling and configuring licenseserverurl in config.properties
Restart the HCL ZIE for Web service manager from Services.
Open the Deployment Wizard and Create a session.
Figure 18 : Create session using Deployment Wizard
Launch the session and check the License count in the License Manager.
Figure 19 : Launch the session from Deployment Wizard
Figure 20 : Updated Active License count in License Manager (after configuring License Manager)
Provide the below Flexera command (same as the command entered previously to upload the public key to Flexera server) and check the acquired licenses as per the session launched from different machines.
C:\Users\Admin\Desktop\Flexera\Others\[Extracted CLLS package]\enterprise\flexnetlsadmin.bat -server <https://[license server host]/api/1.0/instances/[license server ID] -authorize <username> <password> -licenses -verbose>
The Flexera window will also show the Client device information from where the sessions are launched, and licenses are acquired.
Figure 21 : Flexera server command to check acquired licenses
