HCL ZIE for Windows Licensing

In HCL ZIE for Windows the licensing mechanism is managed by HCL License Manager Server. The HCL License Manager Server administers the license acquisition and release for all of its clients. HCL ZIE for Windows as a client sends the license acquisition and release requests to the HCL License Manager server, which in turn forwards the requests to Flexera server.

To use the HCL ZIE for Windows user must configure the License Manager settings with details of a working HCL License Manager Server setup. To know more about setting up the HCL License Manager Server with ZIEWin refer to the topic, HCL ZIE License Manager.

How Licensing Works:

    It is mandatory to have a License Manager setup and having the settings configured in HCL ZIE for Windows to use the application. When an emulator session or an FTP session is launched, it verifies if the License Manager Settings is configured with a valid URL. If it is a valid URL the application gets launched if not, an appropriate message will displayed and the start-up exits.

    For an emulator session, the first session that connects sends license acquisition request to License Manager Server and only if the license is acquired the session proceeds with the connection. If the license is not acquired, an appropriate error message is displayed to the user and the connection get aborted. The license request status are updated in the application status-bar as the session connects. User can look up the status-bar history for details of license request and the License Manager Server responses. The subsequent sessions from first connected session will verify the license status of the application if it is already acquired it proceeds to connect, if not, it sends the license acquisition request again. Once the license is acquired, the license status is updated at every Interval period as configured in License Manager Settings. During the refresh, the license status of the application may change from Acquired to Unacquired or vice-versa.

    At any point of time the license status for the emulator session is indicated by an icon it is status bar. Below are icons for license status.

    1. License Acquired:
    2. License Unacquired:

    During the disconnect of the last connected session, the emulator session sends the license release request to release the license.

    For an FTP Session, when the connection begin it sends license acquisition request to the License Manager Server, only if the license is acquired the connection proceeds else the connection is aborted. The License Manager Server response is recorded in the status-bar of the FTP client application. User can look up the status-bar history for details of license request and the License Manager Server responses. At every refresh interval, if there is a connected emulator session the license refresh is carried out by emulator session else the license refresh is carried out by the FTP client. The license request and response at refresh interval is logged in the FTP client log, users can verify the log for license request responses. During the disconnect of the FTP session it sends a license release request to License Manager Server and the response is recorded in the status-bar.

How to Trouble Shoot:

    If the license is not acquired on request, please check the error code/return code. The license request can fail because of the network issue between the client and License Manager Server or the connectivity between the License Manager Server and the Flexera Server. Please check the connectivity based on the error code/return code. If there is connectivity issue between the client and License Manager Server, the error code/return code will be returned while validating the License Manager URL and the respective http error code will returned. If the License Manager application is not running it returns License Manager Server Unavailable. If there is a connectivity issue between the License Manager and Flexera Server or there is a licensing limitation the error code/return code is forwarded to the client.

    Flexera server configuration error codes/return codes:

    Error code 0: The License has been released successfully.

    Error code 1: Successfully acquired license.

    Error code 2: Failed to retrieve a private key from the client certificate, for more information refer to the log files from Flexera server and license manager application.

    Error code 3: Failed to receive payload from the Flexera server, for more information refer to the log files from Flexera server and license manager application.

    Error code 4: Failed to decode the payload response, for more information refer to the log files from Flexera server and license manager application.

    Error code 5: Configured feature code is not available, for more information refer to the log files from Flexera server and license manager application.

    Error code 6: Configured feature cannot be started, for more information refer to the log files from Flexera server and license manager application.

    Error code 7: Configured feature has expired, for more information refer log to the files from Flexera server and license manager application.

    Error code 8: Failed to get a license from the Flexera server, for more information refer to the log files from Flexera server and license manager application.

    Error code 9: Configured feature name in the Flexera server is not valid, for more information refer to the log files from Flexera server and license manager application.

    Error code 10: Failed to acquire a license, for more information refer to the log files from Flexera server and license manager application.

    Error code 11: Available License count exceeded, for more information refer to the log files from Flexera server and license manager application.

    Error code 12: License acquire request from an unsupported client.

    Error code NNN: HTTP status error code, for more information refer to the log files from Flexera server and license manager application.

Return to Top