r1 - 2013-12-11 - 09:14:40 - Main.litinghuiYou are here: TWiki >  Deployment Web > CloudDeployment > HowToUpgradeRLKSSharedServiceFrom10To101

todo.pngHOW-TO upgrade RLKS Shared Service from to

Authors: TWikiUser, TWikiUser
Build basis: Products, editions, or versions that apply to the content. If no build basis applies to this content, set the build basis to None.

Before you begin

Let’s assume that you’ve already: * Have permissions to deploy and manage shared service instances on IBM Pure Application System or IBM Workload Deployer; * Have an instance of Rational License Key Server Shared Service v1.0; * Uploaded several license key files to the shared service;


1. Prepare SSH access to the existing instance of License Key Share Service

For security reason, you only allowed to access the virtual machine behind the shared service instance using account virtuser via SSH key-based connection with an RSA key pair. If you didn’t set the SSH public key during the deployment, please refer to “Managing virtual application instances” > “Configuring SSH key-based access” topic in the PureApplication™ System information center. After done, follow the commands below to navigate to the home directory of RLKS in 1.0:

  1. Open a Terminal.
  2. Type ssh virtuser@ and press Enter.
  3. Type cd /opt/IBM/RationalRLKS and press Enter.

2. Backup license key files

2.1 Different types of license key file

There are mainly two kinds of license key files, one works for single server node only and the other one can work on multiple servers. If you open one license key file using any text editor like vi, you may found the following text in the head:

SERVER this_host ANY 27000

This indicates that the license key file is wild opened and can be used on other license key server nodes. And if you see some text like this:

SERVER 27000

This means the license key file can only works on specified host and may not work on new instances of RLKS Shared Service because the hostname, IP or host ID can possibly change during deploy new instances. In this case, you need to request new license key files for new instances.

2.2 Locate the license key files and do the backup

Basically, all license key files added by user from RLKS Shared Service Operations are stored under /config/LicenseFiles. The default value of RLKS_HOME is /opt/IBM/RationalRLKS, and you are safe backup the whole folder and copy it somewhere out of the VM. But be aware of the license key files which only work on single node, they won’t work in new instances of RLKS Shared Service, remove them first before restore.

3. Remove the old instance and deploy RLKS Shared Service

Now you can remove the old instance of RLKS Shared Service by doing this from Workload Console:
  1. Go to Instance > Shared Service.
  2. Find the instance of RLKS Shared Service which need to be upgraded.
  3. Click the Delete button on the top right corner of the details panel.
  4. Wait until it finished.
Then, please refer to “Installing” > “License server shared service” > “Installing the license server shared service” in the IBM Software Delivery and Lifecycle Patterns 1.0.1 information center to install the RLKS Shared Service

4. Restore license key files

Restore license key is pretty simple, you can use the Add License operation to add the license key files from the backup to the new instance of RLKS Shared Service, and activate one as your main license key.

For more detail, please refer to “Administering” > “Working with the deployed license server shared service” > “Managing the license server shared service” topic in the IBM Software Delivery and Lifecycle Patterns 1.0.1 information center.


IBM Shared Service for Rational License Key Server is online and running with your own license keys.

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: TWikiUser, TWikiUser

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: 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.