Previous section.

Systems Management: Software License Use Management (XSLM)
Copyright © 1999 The Open Group

Implementation Guidelines

The following sections give examples of the interrelationships between a license management enabled application and a license server. The Named, Concurrent, and Consumptive license types and the Demo terms and conditions are used as examples to illustrate how the data, process and the license entitlement interrelate to affect the behavior of the application. The requests and responses are similar, but they are clearly not identical and their relationship depends largely on the license type. The logic to challenge the XSLM license server and to interpret its response is implementation specific. The application behaviors based on the possible responses are summarized in the last paragraph.

Named License

The following are assumed to exist:

After loading, the application would determine the identification of its current host and issue a query to XSLM requesting authorization to execute. Possible responses would be:

Concurrent License

The following are assumed to exist:

After loading, the application program would issue a query to XSLM requesting authorization to execute. Possible responses would be:

Assuming the application goes into execution, from time to time the application confirms to the license server the fact that the application program is still in operation. When that condition is no longer valid, the authorization at that time assigned to this instance of use of the application is returned to the license server, and becomes available as a positive response to another program-use request.

Consumptive License

The following are assumed to exist:

After loading, the application program would issue a query to XSLM, requesting authorization to execute. Possible responses would be:

Continued checking of operation by the licensing system in conjunction with the application and the license client is not required because the authorization, once granted, cannot be returned for reuse.

Demo License

The following are assumed to exist:

After loading, the program would periodically request authorization to start or to continue executing by issuing a query to XSLM. Possible responses could be:

Summary

In all of the above examples there is a relationship between the response and the application behavior. For the first response in each example, the application will execute its intended functions, the terms of the license agreement having been met. In the other two responses, the application will cause the appropriate messages and logs and initiate actions that support the license terms and conditions. For instance, the application will not go into execution or the application will go into execution but will inform the licensing system of that fact and cause a logging of the excess of entitlement execution.


Why not acquire a nicely bound hard copy?
Click here to return to the publication details or order a copy of this publication.

Contents Next section Index