Open the Table of Contents

You are here: About the RMS License Manager > The License Authorization Process

# The License Authorization Process

The license authorization process is broken into nine steps listed below:

Step 1: License Manager Configuration

Refer to the topic Configuring License Manager for more details.

Step 2: Load License Codes

After configuration, the License Manager reads the license file. The name and location of this file can be set using the License Manager options. The License Manager reads the file from start to finish, processing each license code in order.

All additive and aggregate license codes add to the licensing rights already processed. All exclusive codes override all previously read codes and any future additive codes. Aggregate licenses which have start dates set in the future can still be loaded onto the License Manager, however, they cannot be requested or aggregated until their start date has been reached.

If the License Manager cannot find the license file, it will continue to run. When a License Manager is running it can also accept license codes across the network from other programs such as lslic. The License Manager will process each received code as if it has just been read from the license file. The License Manager will also add the license code to the end of the license file if this was requested.

Step 3: Client Identifies License Manager

If the application supports network licensing, it looks for a license server:

- On the same system
- On a specific system in the network
- Via network broadcast for a License Manager

In most of the cases, this will be taken care by the licensed application. However, your vendor may instruct you to set the specific License Manager host using the LSFORCEHOST environment variable or traverse through various License Managers using the LSHOST environment variable.

See Client - Commonly Used Variables for more details.

Step 4: Client Issues License Request

Once the application has identified the License Manager, it issues a request for one or more licenses to the License Manager. The host name is translated to the network address of the License Manager computer. The application sends a license request to this address and the License Manager’s port.

Step 5: License Manager Responds

When a License Manager receives a license request, it checks to see if a license can be granted based upon the current license codes. If it can, then an authorization is sent back to the client computer. Otherwise, the request is rejected and a denial is sent back to the client computer.

In both cases, the activity may be logged to a file if this capability has been enabled.

Step 6: Client Renews License

Each license code specifies the maximum time period that a license may be held by an application without renewal. After a client has received a license, it must periodically request a license renewal from the license server.

Forcing a license to be renewed allows a License Manager to reclaim a license when there is a problem with an application or a client computer. If the application does not renew its license within the allowed time, it loses its license and the server may grant it to another user.

This action is handled by the application and is transparent to the user on the client computer.

Step 7: License Manager Responds

The License Manager responds to a license renewal request in the same manner as the initial license request as discussed in Step 5.

Step 8: Client Returns License

When an application ends, it sends a message back to the License Manager indicating that the license is no longer needed. This lets the license server immediately reclaim the license and make it available to another user.

### Tip:

Usually, the license will be released automatically after some time if the licensed application does not send an update to the License Manager for long or faces a network issue. This will help in making the licenses available for further requests.

Step 9: License Manager Releases License

When the License Manager receives the license authorization back, it makes it available again to another user.