r7 - 2014-02-13 - 07:01:14 - Main.litinghuiYou are here: TWiki >  Deployment Web > CloudDeployment > SDLCRlksMonitor

todo.png Monitoring License usage in the logs

Authors: TingHuiLi
Build basis: IBM Software Delivery and Lifecycle Patterns, version 1.0.1.

Monitoring License usage through Rational License Key Server Logs.

Check lmgrd.log from the log Viewer.

  1. Log on to IBM® Workload Deployer (home page) or IBM PureApplication™ System (Workload Console tab).
  2. Click Instances > Shared Services.
  3. Click IBM Shared Service for Rational License Key Server 1.0.1.0 in the list. Use the filter to constrain the list if necessary. Wait for the details to be loaded into the right pane.
  4. Click Virtual machine perspective
  5. Click Log link
  6. Open the Log Viewer
  7. Select RLKS -> lmgrd.log

Use Green Hat applications in the Rational Test Workbench Virtual Systems and monitor lmgrd.log for license usage

The Token values consumption of Rational Test Workbench is 21 :

10.png

Then Green Hat applications are started and check lmgrd.log.

1. Start Rational Integration Tester, and check lmgrd.log :

1.png

2. Start IBM Rational Performance Tester, and check lmgrd.log :

2.png

3. Start IBM Rational Performance Tester - Full Eclipse, and check lmgrd.log :

Note that extra 3 token licenses are displayed OUT, which is an existing issue and had been followed up.

3.png

4. Stop RIT, and check lmgrd.log :

6.png

5. Stop IBM Rational Performance Tester, and check lmgrd.log :

No log output

6. Stop IBM Rational Performance Tester - Full Eclipse, and check lmgrd.log :

7.png

Related Articles

External links:

Additional contributors: TWikiUser, TWikiUser

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