Installing and managing floating client access license keys

You can install and configure floating client access license (CAL) keys through the License Key Management section in the Administration page of the Jazz™ Team Server.

Before you begin

If you are using a Jazz Team Server as a stand-alone floating license server, you must know which Jazz Team Server application is the floating license server that has the CAL keys installed and which server is the Jazz Team Server that assigns the floating CAL.

You must be logged in to the Administration page of the Jazz Team Server and be a member of the JazzAdmins group.


  1. Install the floating CAL keys (on the Jazz Server operating as a floating license server):
    1. On the Administration page, click the Server tab.
    2. In the Licensing pane, click License Key Management.
    3. On the License Key Management page, in the Floating License Server area, click Add.
    4. In the Upload License Files dialog, in the Upload License Activation key field, click Choose File and navigate to the location of the floating client access license activation key.
    5. Select the key file.
    6. In the Purchased field, enter the number of licenses purchased.
    7. Click Next.
    8. Optional: On the Connect To Floating Licenser Server page, to configure the floating capabilities on this server, select the check box next to Yes, I want to allow users on this server to be able to acquire the floating licenses on this license server.
    9. Accept the terms in the license agreement and the click Finish.
  2. Configure other Jazz Team Servers to point to the floating license server:
    1. Before you can configure your Jazz Team Server to point to a floating licensing server, you must add friend relationship between the two servers and create a functional user ID that is associated with the friend operation. You can use the -createFriend repotools command to create the friend relationship and associate a functional user ID. For more information about the usage of the repotools command, see Repository tools command to create a friend relationship.
    2. On the Administration page of the Jazz Team Server, click the Server tab.
    3. In the Licensing pane, click License Key Management.
    4. In the Server Information section, hover over the Floating License Server row and click the Configure floating license server icon.
    5. In the Configure Floating License Server dialog box, in the Floating License Server field, type the path to the server. For example, http://floating-license-server:9443/jts, where floating-license-server must be replaced with the fully qualified host name of your server.
    6. To test the server connection, click Test Connection.
    7. Click Finish.
  3. Optional: To modify the purchase counts for licenses:
    1. In the Floating License Server area, click Edit
    2. In the purchased field for a license, type a number of purchased licenses.
    3. Click Finish.
  4. Optional: To change the floating license default timeout:
    1. On the Administration page, click the Server tab.
    2. In the Configuration pane, click Advanced Properties.
    3. Search for
    4. In the License checkout time field, change the default value.
      Note: The default timeout for floating license is 3600 seconds (60 minutes) and the default timeout for token license is 1800000 milliseconds (30 minutes). The minimum amount of time that can be set for both floating and token licenses timeout is 30 minutes, 1800 seconds for floating and 1800000 milliseconds for token. Note that the timeout is measured differently for these licenses. Floating license timeout is measured in seconds and token license timeout is measured in milliseconds.


The Jazz Team Server is now configured so that floating CALs can be assigned to users. The floating CALs are automatically checked out from the floating license server when users require them.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki