Saurabh.Tyagi 270005CY2K Visits (2406)
IBM Rational ClearCase is a software configuration management solution that provides version control, workspace management, parallel development support, and build auditing. You can integrate Rational ClearCase with other IBM solutions, including IBM Rational Team Concert, IBM Rational ClearQuest, IBM Rational Asset Manager, and IBM Rational Application Developer for WebSphere Software.
Rational ClearCase Atria licenses uses a proprietary floating license scheme. To use ClearCase, you must obtain a license, which grants the privilege to use ClearCase on any host served by the same license server. The license server component is installed with a Rational ClearCase server installation; it cannot be installed separately or as a license server only. The full installation of ClearCase is required in order to serve out ClearCase licenses, and there is no separate license server program.
To request new or additional ClearCase (or ClearCase MultiSite) licenses, go to Rational Support Licensing, and then select the Rational License Key Center. If you obtain additional licenses, review this Technote for specifics related to modifications made to the ClearCase license server. The considerations for moving ClearCase licenses to a new server are outlined in Technote
If you obtain additional licenses, review this Technote for specifics related to modifications made to the ClearCase license server. The considerations for moving ClearCase licenses to a new server are outlined in Technote
The considerations for moving ClearCase licenses to a new server are outlined in Technote
For more information, refer to IBM Rational ClearCase Administrator's Guide -> Licensing and License Administration. If you need a soft copy, the cc_admin.pdf is available on any host with ClearCase installed located by default in: UNIX or Linux: /opt Windows: C:\Program File Now it is time to help resolve or avoid the common (ClearCase) errors in our day to day activities without relying on anyone else. You may follow the technical documentation written by experts from Rational Licensing team to save time:
For more information, refer to IBM Rational ClearCase Administrator's Guide -> Licensing and License Administration. If you need a soft copy, the cc_admin.pdf is available on any host with ClearCase installed located by default in:
UNIX or Linux: /opt
Windows: C:\Program File
Now it is time to help resolve or avoid the common (ClearCase) errors in our day to day activities without relying on anyone else. You may follow the technical documentation written by experts from Rational Licensing team to save time:
Author: Saurabh Tyagi
Robert_Stephen 270005GQ3U Visits (6476)
It's always good to have options!
Let's discuss the options a license administrator has to use for a license. The options file is a plain text file that allows a floating license administrator to control user access to specific features or versions of licensed software. Users are identified by their username, hostname, IP address, or project.
For concurrent (floating) licenses, the license administrator can:
This looks good but your next question will likely be: "How can I create an options file?"
For example: VENDOR /etc/test [opt
Let’s create an options file assuming Peter, Matt, and Steve are all part of a team named 'Licensing' in an organization. We can create a group named 'Licensing' and have these users added into the group. The syntax would be: GROUP Licensing Peter Matt and Steve
Subsequently this group can be included to allow access to IBM Rational product license. Hence the final syntax in the Options file would appear as follows:
GROUP Licensing Peter Matt and Steve
INCLUDE RPE_PUBLISH GROUP Licensing ( considering the .opt file is for RPE )
If the system usernames in your organization have a space OR comma in them, then the names need to be enclosed within double quotes.
Example: Let's assume the usernames are <USER A>, <USER B> and <USER C>. Then the Options. opt file would have: INCLUDE RPE_PUBLISH USER "USER A" "USER B" "USER C" Alternatively, you can utilize the same concept of adding all the users into a GROUP and then specifying the name of the GROUP in the INCLUDE line of the options file.
Also, if you have only one USER_BASED license for IBM RPE in your license file, you would be able to specify only one user's name in the Options file. Once the Options. opt file has been updated as per the format of the system usernames, please save the same while making sure that the file is saved as "Options. opt" and doesn't have a .txt extension.
Open the License.dat and add the complete path of the newly created Options. opt file at the DAEMON line. The DAEMON line should be the next line (one soon after the) SERVER line in the license.dat file. If you don't have a word DAEMON instead have Vendor, please perform the following changes in the License.dat file.
SERVER LicenseServerName 12AcDe 19353
DAEMON telelogic "C:\Program File
After performing the above changes, save the License.dat file while making sure it's saved with only (.dat) extension.
Launch LMTOOLS and click on "Start/Stop/ReRead" tab. Stop the server, restart it, and wait until it says "Server Started successfully".
After the server has started successfully, please click on "ReRead License File" and wait until it displays: "ReRead license file completed". Once the message is displayed, click on "Server Status" and click on "Perform Status enquiry" and check if there is any error with the RPE_PUBLISH license. Ideally there shouldn't be any.
Any changes that are made to the Options file gets read either by doing a re-read or stopping and starting of the license server. The ability for vendor daemon to participate in rereading of its option file is introduced in the version 8.0 vendor daemon. If the License server is stopped and started the license file and option file are automatically read.
Now before proceeding we need to understand the most commonly used syntax of the options file:
Now we know how to create an options file lets use the options file to reserve or deny licenses. IBM Rational provides the least restrictive licensing environment possible. By default, the server does not restrict access to a client requesting a license key. This configuration works best for most customers. For a more controlled license environment, use the options file to reserve or deny licenses for certain users, hosts, displays, groups, or IP addresses. You can also limit the number of licenses each user or group can access.
The options file is a case-sensitive text file that sets the options for the license server. The options file can be used with the different types of floating licenses keys: temporary, evaluation, or permanent licenses keys. Your options file is located in the rational_dir\common directory and might have the name ibmratl.opt. If you do not have an options file, you can create one.
Options file that reserves licenses:
You have 10 floating licenses for IBM Rational ClearQuest®. You want to ensure that users Greg and Michelle always have a license of ClearQuest available for their use. Configure the options file as follows:
RESERVE 1 ClearQuest USER greg
RESERVE 1 ClearQuest USER michelle
Options file that excludes users from accessing a license:
You have 10 floating licenses for IBM Rational ClearQuest. You want to ensure that user Sally does not have access to a ClearQuest license. Configure the options file as follows:
EXCLUDE ClearQuest USER sally
How to configure USER_BASED license:
Common features used in the FLEXlm Licensing options file:
image credit: (cc) Some rights reserved YourRightMoveLLC
Author: Robert V Stephen
@Sharma~Pankaj 270001DHR3 Visits (2316)
For a Rational License server ( version v 8.1.2 or above ) to work properly using IPv6 addresses, all systems in an enterprise (including the network hardware and software) must be configured properly to support communication using IPv6 addresses.
Before testing or deploying a Rational Common Licensing-supported or -based application that supports IPv6 or IPv4/IPv6 dual communication, make sure that all systems on the network can communicate successfully. If the license server will run under any of the following operating systems, it can communicate with clients using either IPv4 or IPv6 (as long as the network is configured properly).
Because these operating systems support dual-layer communication, both IPv4 and IPv6 enabled clients can communicate with an IPv6 license server. Moreover, IPv6 clients can communicate with an IPv4 license server using the IPv4 address, as seen below:
In the case of a license server hosted on Windows XP or Windows Server 2003 operating systems, there are certain drawbacks because of limited dual-layer support on these operating systems.
Author: Pankaj Sharma