Ibm rational license key administrator 8.1.1 - Free Download
E dit A ttach P rintable. JaneBalin , MichaelAfshar Build basis: Collaborative Lifecycle Management 4. Peak Usage report definition Example: Peak Usage report Token Distribution report Example: Token Distribution report User Based report Example: User Based report Chargeback report Example: Chargeback report Other capabilities Downloading, installing, and system requirements.
The Rational License Key Server Administration and Reporting Tool provides out-of-the-box license usage reports and capability to download your license usage data into more customizable formats. The tool supports reporting on both floating and token license models.
The tool does not track license usage for Atria licenses and node-locked licenses. The solution is based on a linked data model: High-level architecture of reporting CLM reports: Peak Usage, Token Distribution, User Based, and Chargeback Peak Usage reports provide details on the maximum usage of product licenses over a given period of time.
The following parameters and variables are defined for these reports: How often the data is sampled. Typically customers like to see daily peak usage reports. The period of time over which the customer wants to see the usage data. The set of products on which the report is based. The various license types for which a report is needed for example, floating or tokens.
The report indicates the count of licenses, which is a sum of the selected types. Users can select the license servers to report against. The report indicates the highest number of licenses used for each selected product from across the specified license servers.
Peak Usage report With Peak Usage reports, a license administrator can identify usage patterns and thereby reduce license procurement costs. The following examples show a Peak Usage report definition and a chart of the Peak Usage report definition results. Peak Usage report Token Distribution report Token Distribution reports show the usage of tokens across products. This report is based on the total number of tokens consumed across a specified set of products for a selected period of time.
Token Distribution report User Based report User Based reports give information on the duration that product licenses are used by a defined set of users. The License Hours column data shown in the following example of a User Based report is determined by multiplying the number of specific product licenses that a user has checked out by the total amount of time the licenses were checked out, and then dividing by For example, if a user has checked out two licenses for a specific product and has kept each license checked out for a total of 90 minutes, the license hour calculation would be the following: The aggregation of the license usage data per product, per user is advantageous because it results in less data to store in the LQE database.
User Based report Chargeback report Chargeback reports associate license consumption with cost. A license administrator can charge different departments in the organization for the licenses that they consume. The Chargeback report enables organizations to move to an environment in which licenses are consumed and paid for on a pay-per-use basis.
The following chart shows an example of a Chargeback report based on the rate settings noted in the above figure. Chargeback report Other capabilities The Rational License Key Server Administration and Reporting Tool also provides the capability to schedule reports and save the scheduled reports. Future plans for the tool include the ability to email scheduled reports.
This capability enables administrators to create custom reports and to provide license consumption data to other reporting tools, including Microsoft Excel, for further customization. Finally, the user-management side of the tool enables integration with two types of user realms or databases that store user account details: This functionality is employed for validating user access and access privileges to the tool.
By default, a predefined set of users are created during the installation. The user IDs, passwords, and access privileges are as follows: User ID Password Role description rcladmin rcladmin Administrator privileges are assigned to this user with access to all the features of the application.
Downloading, installing, and system requirements To download and install the tool, see the Rational License Key Server 8. You do not need to download the Rational License Key Server 8. As long as you are at version 4. Although not a requirement, if you are using tokens for your CLM products, you might want to download and install the 8.
Create a new task in the RTC Deployment wiki project. Administrator privileges are assigned to this user with access to all the features of the application. User privileges are assigned to this user with access to the reporting feature of the application.
The installation log of Rational License Key Server Administration and Reporting Tool package shows error messages after the package is installed. This section provides information related to the impact of this release to allow you to assess how your environment may be affected. RLKS server starts with error: Known problems This section contains a link to the known problems open defects identified at the time of this release. Check here to start a new keyword search. Click the Fix List link in the table of contents above to review a list of the problems solved in this release. To use most IBM Rational software products, a specific license key is required. After you uninstall the previous version, the data in the installation directory remains.
User Based report Chargeback report Chargeback reports associate license consumption with cost. If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support. The period of time over which the customer wants to see the usage data. Typically customers like to see daily peak usage reports. To resolve this issue, see the technical document for detailed steps. Why can't I launch trial version of Modeler? The server administration capability is for administering the license servers to generate license usage reports. United States English English. An error in the Maintenance Delivery Vehicle MDV that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed. This functionality is employed for validating user access and access privileges to the tool.
This release is a maintenance release of Rational License Key Server 8. Installation instructions The Installation instructions section provides the installation instructions necessary to apply this release into your environment. You will be directed to individual links to each platform. For more details, see Creating a report definition. This section provides information related to the impact of this release to allow you to assess how your environment may be affected. Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community. Please read the following disclaimer. This is a fixpack release. Impact assessment The How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected. To save time, know the answers to these questions:. For example, if a user has checked out two licenses for a specific product and has kept each license checked out for a total of 90 minutes, the license hour calculation would be the following: This section provides the direct link to obtain the download package for installation in your environment. Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. Finally, the user-management side of the tool enables integration with two types of user realms or databases that store user account details: