r2 - 2014-03-19 - 09:08:28 - Main.liuzhichengYou are here: TWiki >  Deployment Web > CloudDeployment > TroubleShootingOfRLKSSharedServiceWithFirewallInRelease1000

todo.png Trouble shooting of RLKS Shared Service with firewall in release 1.0.0.0

Authors: SuperWang

When you are using IBM Shared Service for Rational License Key Server, after add and activate license key file from Manage -> Operations, the RLKS is up and running but you just failed to find it from your client application which gonna use this license. Follow the bellow steps to fix:

  1. You need to SSH to the virtual machine which RLKS is running on, if you don't know how, read this: Accessing Shared Services using SSH

  2. Goto /opt/IBM/RationalRLKS/config/LicenseFiles, all license key files you added will be here

  3. Open the license key file you are using or going to use with any text editor like vi, you may see similar format like this:

    SERVER <Your host name> <Your host id> 27000
    VENDOR ibmratl
    VENDOR telelogic
    VENDOR rational

  4. If so, append the following line under the first line:

    DAEMON ibmratl /opt/IBM/RationalRLKS/bin/ibmratl PORT=27001

  5. The final result should look like this:

    SERVER <Your host name> <Your host id> 27000
    DAEMON ibmratl /opt/IBM/RationalRLKS/bin/ibmratl PORT=27001
    VENDOR ibmratl
    VENDOR telelogic
    VENDOR rational

  6. Restart the RLKS Shared Service as usual.

The key message of this fix is about make the license key vendor use a fixed port, 27001 here, rather than a dynamic range or port, and the port 27001 is opened in firewall by default, so your client application can easily connect to it through the fixed port.

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.