NikhilBhat 270005V9K6 Visits (1883)
Of late I have come across instances, where license administrators are facing issues related to permanent and temporary licenses. I thought it will be a good idea to provide all the relevant information through this post. Let me start with a description of license key types.
License key type : These are broadly categorized into two parts
Permanent: A license issued to a customer to run products for an indefinite period of time.
To order your permanent floating, named-user floating, or authorized user license keys for most products, use the IBM Rational License Key Center.
To acquire an authorized user license key for IBM Rational products based on the Eclipse framework, purchase and download an activation kit from Passport Advantage. See Requesting license keys for information about ordering keys from the License Key Center.
Temporary (evaluation or emergency): A time-limited license issued to a customer for running IBM Rational products. You can use it on any computer until the specified expiration date.
Temporary license keys can be floating or authorized user.
Temporary keys are generated only for single or multiple license servers. They are not generated for redundant servers.
NOTE : To evaluate a product, ask your sales representative for an evaluation key.
Important : License key files file name with description:
→ rational_temp.dat: Contains all authorized user temporary license keys. Obtain a permanent license key to use your IBM Rational product past the temporary license key expiration date.
→ rational_perm.dat: Contains all authorized user permanent license keys. Go to IBM Rational License Key Center to request permanent license keys.
Now as we know and understand the basics about licenses, we can move ahead to discuss a few issues related with using the licenses in your environment. To start off, I would like to discuss about using a newly generated temp
The figure below shows the contents of a temporary license file
the Host name is “this_host”
the host id is “ANY”
the host-id is “ANY” to signify that this license can be run on any machine irrespective of the license type,
But while configuring these licenses on the license key server you need to make sure that the host name is updated to reflect the the actual Host name of the machine on which the license key server is running.
If this is not done, license checkouts will not happen.
Steps to modify the temporary license file:
1. Open the temporary license file with notepad or any other text editor.
2. Replace this_host with hostname of the machine.
3. Save the changes and exit from text editor.
If the Rational license key server is running on the host ABCD, then the above steps should be followed and the updated file should look like the one below
There may be instances where you have to use both permanent and temporary license. The following discussion focuses on this.
How to serve both permanent and temporary licenses at the same time
As pointed out earlier for temporary licenses, the following files are used
and for permanent licenses, the following files are used
So we have to configure the license server to read two license files instead of one
Steps to make the license server to read two license files
If Rational License Key Server is configured as a Service
1. Open windows registry editor (regedit.exe)
2. Navigate to the following registry key:
Note: On 64-bit Windows 7 platform, please navigate to the following key:
3. Modify the current value, and specify the complete paths to the two license files, separated with a semi-colon “;”.
4. Close the registry editor and restart your Rational License Server.
If the license server was initially started as a process from a command prompt:
1. Stop the license server by using following command
lmutil lmdown -c <pat
2).Restart the Rational License Server process using the following command:
lmgrd -c <pat
Note: The 2 paths are separated by a semi-colon ";".
I would also mention that removing the references to expired temporary licenses is also very important. If not removed, the expired licenses can cause issues while importing new licenses.
To remove expired temporary licenses:
1. Navigate to location of rati
2. Open the file in a text editor.
3. Delete the lines or INCREMENT block(s) corresponding to the expired temporary licenses.
4. Restart the license server.
→ How to serve both permanent and temporary licenses at the same time: http
→ Rational License File Management: http
→ Rational Common Licensing 8.1.4: http
AcdntlPoet 2700019V2G Visits (1484)
What is IBM Event Connect?
Let's us do the work!
Learn more on SlideShare here !
Contact Janet Baum for more information: phone 720.396.2912 or Emai
Sumant Renukarya 270002B42N Visits (1589)
It is possible to export and import the work items from a repository to another. Here was a unique situation, which demanded additional work.
We were trying to export workitems to CSV and import it in to other repository. It is possible to get the XML data entered in an attribute of a work item upon export, if that attribute is of the type wiki or HTML. However we had an attribute of the type largeString, which had XML content as the data for this attribute.
Exporting the work item to CSV in this case did export the attribute but not the XML data to CSV.
==> Here are the steps that we took, to bring the XML content from the attribute of the type large string at the target project area. It makes use of Temporary HTML attribute for this cause.
4. Apply the script to the LargeHTML attribute.
Please note, the use case mentioned here may not be applicable to all users performing an export and import, as this was a unique situation with a non-typical solution.
irenebond 270000P84P Visits (1383)
Flip or Flop, Rehab Addict, Renovation Raiders rest my brain after a long day. When they find an intriguing listing these investors look at the neighborhood comps, zoom to the property and poke around the perimeter attempting to peer into filthy windows. They examine refuse piles as if on an archeological dig, try to gauge the viability of the roof and foundation and then bolt back to their cars. Speeding to the courthouse steps they formulate a bidding strategy and make some wild estimates as to potential return on investment. With a flip of the hand they throw down a few hundred thousand dollars.
Keys In hand they nervously enter the darkened structure and begin to learn just how far out of reach their target ROI is. The sooty smoke detector atop the trash heap – thrown out after a fire gutted the kitchen. Water stained ceilings mean the roof has been leaking a while and hearts sink as they encounter termite trails meandering down the walls. Their margin target has been shot to hell…
It’s fascinating because this buying process is the antithesis of corporate buying decisions. Tangible ROI is the central concern of every client considering the purchase of IBM’
Home renovators all want state of the art kitchens with wide open vistas, but challenges often arise when the contractors start to open up walls. That’s when they discover that without the addition of a big beam, the upstairs bath tub is on its way to becoming a patio planter.
Just as it’s simply not possible to envision what’s inside walls, until we start working together, AVP can’t understand every nuance of your software development environment. Within a matter of weeks your dedicated AVP resource develops that expertise and will be working with you to recommend the right structural reinforcements and IBM resources to enhance process and performance, while being ever mindful of your business goals.
And though we can’t invite you to come and view our new showcase home, while you’re at Innovate we can invite you to meet some of our most important clients and hear their ‘renovation’ stories. They represent companies that invest in AVP year after year, because we make their lives easier and offer solid ROI. Real results delivered in real time.
Interested? Ask us how.
One of the users using IBM Rational Team Concert (RTC) 4.0.1 were planning to move some work items to a different repository.
To do this, they were considering the following options along with some requirements:
a. Move the work items, preserving workitem ID and if possible history also.
b. Export workitems to CSV file and then import it into other repository.
Here is the information that should help users with similar queries:
So those references would break if the work item is moved.