Saurabh.Tyagi 270005CY2K Visits (4260)
IBM Rational Jazz token license configuration on Jazz team server
Token based licensing is an option, along with floating and authorized user licensing, within the Rational portfolio. Technically, the basis of token licensing is on the traditional floating license mechanism and process. However, when it comes to how the license check out (consumption) works, it has a different behavior.
In a token environment, each product consumes a predefined token value, not a predefined quantity as it does in a traditional floating licensing environment. The license key has a pool of tokens from which the license server automatically calculates the tokens being checked in and out across users and products.
Lets discuss how a token based licensing model can be implemented for Jazz-based products.
Jazz-based products use IBM Rational Common Licensing (RCL) token service provider, which is an extension of the Jazz Team Server (JTS) that forwards token requests to an IBM Rational License Key Server (RLKS). Jazz-based products and non Jazz-based products can share tokens from same pool of tokens.
How to generate Jazz tokens?
Log into the Rational license key center and follow the below steps to get the required Jazz tokens
You can also refer to the technote links below which will guide you in accomplishing this task:
To configure these Jazz based licenses, from a licensing perspective pre-requisites are:
The following picture shows a high level single server topology deployment of RTC using token licensing.
Once you have successfully configured your flexlm license server with token file, you downloaded from IBM Rational license key center (license.dat), Import the Jazz Keys (Jazz.Token.zip file) on the Jazz team server.
Post successful import of Jazz keys on the Jazz team server you will find an entry very similar to the below diagram
The above screen confirms that the Jazz tokens are successfully imported on the Jazz team server and we can now proceed to configure this Jazz Team Server to communicate with the Rational License Key Server that you installed and configured earlier.
In the Floating License Server section of the License Key Management page of your Jazz team server click the radio button next to IBM Rational Common Licensing Token Service to enable the service.
Hover over the icon in the Actions column until you see the edit hover. Click the icon to view the Server Configuration dialogs shown in following picture.
Configure the following two properties in the above dialog:
If the Jazz Team Server is able to connect to the Rational License Key Server, you'll see a green checkmark on the IBM Rational Common Licensing Token Service line as shown in following picture.
AcdntlPoet 2700019V2G Visits (1869)
Using the Sandbox Practice Environment for Rational DOORS Next Gen v4.0.5+ This video illustrates how to use a sandbox on Jazz.net as your practice environment for completing the Getting Started tutorial.
Saurabh.Tyagi 270005CY2K Visits (2921)
All about Rational Developer Licensing
Rational Developer is a batch offering from IBM which has unique functionalities than a normal IDE available. Let’s get introduced to the Rational Developer versions available for usage.
I welcome you to get an in depth understanding about the Rational Developer licensing.
What you should know about Rational Developer Licensing?
There are four broad categories of licenses for Rational Developer, viz.
IBM Rational Developer for AIX and Linux has these subset of licenses which can be used:
Rational Developer for System i licenses are imported only on Windows PCs, where System i and System z are the iSeries and zOS hosts that the client is connecting to. IBM Rational Developer for i has these subset of licenses which can be used:
IBM Rational Developer for Power Systems Software C/C++ Dev Studio for AIX v7.6
Rational Developer for Power Systems Software includes four separately licensed features:
Rational Developer for System z licenses are imported on Windows PCs, where System z are the zOS hosts that the client is connecting to for development purpose. IBM Rational Developer for z has these subset of licenses which are highlighted below:
IBM Rational Developer for System Z V7.1 Activation Kit
IBM Rational Developer with Java v8.0 Floating License Key
IBM Rational Developer for AIX and Linux version 8 are not displayed in the license key center list as v8.5 was called Rational Developer for Power systems and from v9.0, it is addressed Rational Developer for System i.
Versions of IBM Rational Developer for SOA Construction include 7.5, 8 and 8.5 versions, though license key center does have only versions 7.1 and 7.5. Variants of licenses include :
SOA (Service Oriented Architecture) v7.5 and below was a bundle of products and not just one product, which included licenses of RDp (Rational Developer for Power Systems), HATS (Host Access Transformation Services), and RBD (Rational Business Developer).
SOA v8 and above is split into individual products RDp, HATS, and RBD (Rational Business Developer) to be individually licensed.
Why is the Rational Developer with EGL v8.5 not available to be generated on license key center, though our account is under maintenance?
Do I have a chance to try out a trial before a license purchase?
I have a Rational Developer for I RPG and COBOL and modernization tools license. However I get a “No license available” for RPG and COBOL plug in on the software. How do you explain that?
How does RPG and COBOL development plugin license requirement in Rational Developer for Power Systems?
See you folks. Let’s get together with my next blog.
AcdntlPoet 2700019V2G Visits (1612)
Different Types of reports in the RLKS Admin and reporting tool:
Reports display valuable statistics about how users are using the assets and repository.
Managing software assets goes beyond submitting them to a repository and managing them through consumption. Over time, looking at the changing elements, the models and trends of asset details, consumption use cases, and users information can help companies evaluate the needs of their current business strategies.
Lets understand the different types of reports available and the insights they provide...
Peak usage : This metric represents the maximum number of license requests that were granted by the selected license servers for the selected products. If more than one license type is selected in the report definition (floating and token as license type), the peak usage report shows multiple numbers in the bar graphs. The following example shows a peak distribution report with two counts per bar.
Peak denial : This metric represents the maximum number of license requests that selected license servers denied for the selected products during the specified time.
Note: In certain reporting scenarios, the tool can report inaccurate license denials. For more information, see the "Known limitation in license denial report" technical document.
License usage per user : This metric presents information about product usage by a user from a license server at a specified time. This list includes the user and the host server name for the selected products for the specified duration.
Available Licenses : This metric presents the total number of licenses for a product that are available in the license files that are used to start the license server.
License expiration : This metric presents the expiration date of licenses for each of the selected products. This information is collected from the license file.
Token distribution : This chart presents the number of token licenses that are issued in the specified time for various products in an organization.
Chargeback report : This metric represents a simple chargeback policy for product licenses that are used in an organization. The report for this metric is like an invoice, where the number of licenses that are used by each user during a specified time is listed. The number of license hours is multiplied by the unit costs that are associated with each license hour of that kind of license for that product. This product gives the value in currency to be charged for that user.
Note: For the Collaborative Lifecycle Management (CLM) products, the following metric types are supported: