Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Configuring the Jazz Team Server's Floating License Server

 I currently have two Jazz Team Servers on the network: JTS1 and JTS2.

JTS1 has a Rational License Key Server (RLKS) and JTS2 also has a RLKS. So every three years when my tokens expire I have to get some new tokens for JTS1 and some others for JTS2. <o:p> </o:p>

 

If I want to change it so that I only use the one License Server (on JTS1)  what do I have to do? <o:p> </o:p>

On the JTS2 server’s “Advanced Properties” I can see two items that look like they may be relevant: <o:p> </o:p>

(i)               Core Repository Component
com.ibm.rational.common.token.licensing.RL.SLicenseService
IBM Rational License Key Server = 27000@JTS2

<o:p> </o:p>

(ii)             com.ibm.team.repository.service.internal.license.LicenseService
Floating license server = https://jts2:9443/jts/ <o:p> </o:p>

I am guessing that I have to change these values, or is there more to it than that? <o:p> </o:p>

Thanks <o:p> </o:p>

                Peter <o:p> </o:p>

0 votes



One answer

Permanent link
In this case your JTS servers are actually doing double duty as both a JTS and as a Jazz License Server. You can actually set up a separate JTS as just a License server if you want but the process is the same regardless.

For the host that you have defined as the Jazz License server, load up all your Jazz Floating License Token activation keys, and then set the Advanced Property com.ibm.rational.common.token.licensing.RLSLicenseService to point to your RLKS where the tokens are.

Then for all the other JTS servers, make sure they have no license activations loaded, or the property above set, and then set their Advanced Property com.ibm.team.repository.service.internal.license.LicenseService to point to the Jazz License Server above.

If you are using one of your servers to do both duties, then you simply set up the License server as above on that server, and then set its LicenseService property to point to itself.

0 votes

Comments

Thanks for the reply Davyd. I think I had worked out the bit about com.ibm.team.repository.service.internal.license.LicenseService  but was wondering what I had to do with the com.ibm.rational.common.token.licensing.RLSLicenseService so that's useful : I will make sure that JTS2 does NOT have that value set.

Can you tell me anything about "Friends" ?

At the moment JTS1 (the one that will hold all of the licenses) has an Authorized Key from JTS2:9443/jts, but no friends (ahh!).

JTS2 (the one that will be getting its licenses from JTS1) has got JTS1:9443/jts/rootservices set up as a Friend, but it has no Authorized Key from JTS1.

Do I need to do a bit more ?

The way I have things at the moment I can't change the com.ibm.team.repository.service.internal.license.LicenseService on JTS2 to point to JTS1 because of a CRJAZ2916E error.

Ah yes that changed in 6.0

On the server that's using the remote Jazz License Server you need to set the remote up as a friend. Nothing need to be done on the one that's serving up its own licenses.

Follow this note and you should be right:

 Thanks Davyd, I had worked out how to do most of it but your tip about making sure that JTS2 had no value set for its Core Repository Component/IBM RLKS was useful. And so was the bit about adding a Functional User to the Authorization Key. And I accidentally set my Friendships up the wrong way round the first time I tried but I got there in the end. It's all working now. 

Cheers
            Peter

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,510
× 6,132
× 14

Question asked: Jan 20 '20, 10:57 a.m.

Question was seen: 1,782 times

Last updated: Jan 28 '20, 11:50 a.m.

Confirmation Cancel Confirm