Frontmatter

©March 1999, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.

This document is published by The Open Group under the terms and conditions of its agreement with GUIDE International, Inc., and the XSLM working group participants:

BC Government/ISM-BC
Boole & Babbage
Compuware Corporation
IBM Corporation
Isogon Corporation

Under this agreement, such permission is hereby granted to GUIDE International, Inc. and the XSLM working group participants.

This specification has not been verified for avoidance of possible third party proprietary rights. In implementing this specification, usual procedures to ensure the respect of possible third party intellectual property rights should be followed.

Any comments relating to the material contained in this document may be submitted to The Open Group at:

The Open Group
Apex Plaza
Forbury Road
Reading
Berkshire, RG1 1AX
United Kingdom

OGSpecs@opengroup.org

Preface

The Open Group

The Open Group is the leading vendor-neutral, international consortium for buyers and suppliers of technology. Its mission is to cause the development of a viable global information infrastructure that is ubiquitous, trusted, reliable, and as easy-to-use as the telephone. The essential functionality embedded in this infrastructure is what we term the IT DialTone. The Open Group creates an environment where all elements involved in technology development can cooperate to deliver less costly and more flexible IT solutions.

Formed in 1996 by the merger of the X/Open Company Ltd. (founded in 1984) and the Open Software Foundation (founded in 1988), The Open Group is supported by most of the world's largest user organizations, information systems vendors, and software suppliers. By combining the strengths of open systems specifications and a proven branding scheme with collaborative technology development and advanced research, The Open Group is well positioned to meet its new mission, as well as to assist user organizations, vendors, and suppliers in the development and implementation of products supporting the adoption and proliferation of systems which conform to standard specifications.

With more than 200 member companies, The Open Group helps the IT industry to advance technologically while managing the change caused by innovation. It does this by:

• Consolidating, prioritizing, and communicating customer requirements to vendors

• Conducting research and development with industry, academia, and government agencies to deliver innovation and economy through projects associated with its Research Institute

• Managing cost-effective development efforts that accelerate consistent multi-vendor deployment of technology in response to customer requirements

• Adopting, integrating, and publishing industry standard specifications that provide an essential set of blueprints for building open information systems and integrating new technology as it becomes available

• Licensing and promoting the Open Brand, represented by the "X" Device, that designates vendor products which conform to Open Group Product Standards

• Promoting the benefits of the IT DialTone to customers, vendors, and the public

The Open Group operates in all phases of the open systems technology lifecycle including innovation, market adoption, product development, and proliferation. Presently, it focuses on seven strategic areas: open systems application platform development, architecture, distributed systems management, interoperability, distributed computing environment, security, and the information superhighway. The Open Group is also responsible for the management of the UNIX trademark on behalf of the industry.

Development of Product Standards

This process includes the identification of requirements for open systems and, now, the IT DialTone, development of Technical Standards (formerly CAE and Preliminary Specifications) through an industry consensus review and adoption procedure (in parallel with formal standards work), and the development of tests and conformance criteria.

This leads to the preparation of a Product Standard which is the name used for the documentation that records the conformance requirements (and other information) to which a vendor may register a product.

The "X" Device is used by vendors to demonstrate that their products conform to the relevant Product Standard. By use of the Open Brand they guarantee, through the Open Brand Trade Mark License Agreement (TMLA), to maintain their products in conformance with the Product Standard so that the product works, will continue to work, and that any problems will be fixed by the vendor.

Open Group Publications

The Open Group publishes a wide range of technical documentation, the main part of which is focused on development of Technical Standards and product documentation, but which also includes Guides, Snapshots, Technical Studies, Branding and Testing documentation, industry surveys, and business titles.

There are several types of specification:

• Technical Standards (formerly CAE Specifications)

  The Open Group Technical Standards form the basis for our Product Standards. These Standards are intended to be used widely within the industry for product development and procurement purposes.

  Anyone developing products that implement a Technical Standard can enjoy the benefits of a single, widely supported industry standard. Where appropriate, they can demonstrate product compliance through the Open Brand. Technical Standards are published as soon as they are developed, so enabling vendors to proceed with development of conformant products without delay.

• CAE Specifications

  CAE Specifications and Developers' Specifications published prior to January 1998 have the same status as Technical Standards (see above).
  

• Preliminary Specifications

  Preliminary Specifications have usually addressed an emerging area of technology and consequently are not yet supported by multiple sources of stable conformant implementations. They are published for the purpose of validation through implementation of products. A Preliminary Specification is as stable as can be achieved, through applying The Open Group's rigorous development and review procedures.

  Preliminary Specifications are analogous to the trial-use standards issued by formal standards organizations, and developers are encouraged to develop products on the basis of them. However, experience through implementation work may result in significant (possibly upwardly incompatible) changes before its progression to becoming a Technical Standard. While the intent is to progress Preliminary Specifications to corresponding Technical Standards, the ability to do so depends on consensus among Open Group members.
  

• Consortium and Technology Specifications

  The Open Group publishes specifications on behalf of industry consortia. For example, it publishes the NMF SPIRIT procurement specifications on behalf of the Network Management Forum. It also publishes Technology Specifications relating to OSF/1, DCE, OSF/Motif, and CDE.

  Technology Specifications (formerly AES Specifications) are often candidates for consensus review, and may be adopted as Technical Standards, in which case the relevant Technology Specification is superseded by a Technical Standard.

In addition, The Open Group publishes:

• Product Documentation

  This includes product documentation-programmer's guides, user manuals, and so on-relating to the Pre-structured Technology Projects (PSTs), such as DCE and CDE. It also includes the Single UNIX Documentation, designed for use as common product documentation for the whole industry.

• Guides

  These provide information that is useful in the evaluation, procurement, development, or management of open systems, particularly those that relate to the Technical Standards or Preliminary Specifications. The Open Group Guides are advisory, not normative, and should not be referenced for purposes of specifying or claiming conformance to a Product Standard.

• Technical Studies

  Technical Studies present results of analyses performed on subjects of interest in areas relevant to The Open Group's Technical Program. They are intended to communicate the findings to the outside world so as to stimulate discussion and activity in other bodies and the industry in general.

Versions and Issues of Specifications

As with all live documents, Technical Standards and Specifications require revision to align with new developments and associated international standards. To distinguish between revised specifications which are fully backwards compatible and those which are not:

• A new Version indicates there is no change to the definitive information contained in the previous publication of that title, but additions/extensions are included. As such, it replaces the previous publication.

• A new Issue indicates there is substantive change to the definitive information contained in the previous publication of that title, and there may also be additions/extensions. As such, both previous and new documents are maintained as current publications.

Corrigenda

Readers should note that Corrigenda may apply to any publication. Corrigenda information is published on the World-Wide Web at http://www.opengroup.org/corrigenda.

Ordering Information

Full catalogue and ordering information on all Open Group publications is available on the World-Wide Web at http://www.opengroup.org/pubs.

This Document

XSLM provides an interoperable solution for managing software licensing, accommodating diverse license management schemes and license certificate formats, in different operating environments. It does this through use of a logically centralized software license use management system. This enables a supplier to ship a single product that will operate under any license use management scheme that a customer may elect to install.

Document Structure

• Chapter 1 explains the context and business reqirements for management of the use of software licenses.

• Chapter 2 describes the licensing process, its workflow, and license types.

• Chapter 3 describes the roles of the Application Broker and the Management Agent in the process.

• Chapter 4 addresses security issues and features that are provided in XSLM for authentication and data integrity.

• Chapter 5 defines the data types and data elements used in XSLM.

• Chapter 6 explains the license certificate format.

• Chapter 7 defines the API function calls, both in the "basic" set and in the "advanced" set.

• Chapter 8 defines the Management API function calls.

• Chapter 9 describes XSLM's recording and logging facilities.

• Chapter 10 describes all the data elements defined in XSLM.

• Appendixes A-D give information on license types, implementation guidelines, functional sets and towers, and future directions.

• Appendix E gives the standard Java bindings for both the basic and the advanced XSLM API.

Typographical Conventions

• Bold font is used in text for options to commands, filenames, keywords, type names, data structures and their members.

• Italic strings are used for emphasis or to identify the first instance of a word requiring definition. Italics in text also denote:

  • Command operands, command option-arguments, or variable names; for example, substitutable argument prototypes

  • Environment variables, which are also shown in capitals

  • Utility names

  • External variables, such as errno

  • Functions; these are shown as follows: name(); names without parentheses are C external variables, C function family names, utility names, command operands, or command option-arguments.

• Normal font is used for the names of constants and literals.

• The notation <file.h> indicates a header.

• Syntax, code examples and user input in interactive examples are shown in fixed width font. Brackets shown in this font, [], are part of the syntax and do not indicate optional items.

Trademarks

Motif®, OSF/1®, UNIX®, and the "X Device"® are registered trademarks and IT DialTone^TM; and The Open Group^TM; are trademarks of The Open Group in the U.S. and other countries.

Acknowledgements

Many members of the Open Group's Management Working Group, and of GUIDE Inyternational, have contributed to this specification, either by providing input material or by reviewing drafts. In particular, thanks are due to:

The X/Open Technical Specification Working Group would also like to acknowledge the valuable input provided by:

Referenced Documents

GUIDE LUM Requirements

A Requirement for Software License Use Management; created by the License Use Management Project of GUIDE International Corporation; August 29, 1996.

IEEE Std 754

ANSI/IEEE Std 754-1985: Standard for Binary Floating-Point Arithmetic.

LCF

NetWare License Certificate Format; Novell, Inc.; December 18, 1995.

LM Standardization

License Management Standardization; The Open Group Systems Management Task Group; July 31, 1992.

LSAPI

License Service Application Programming Interface (LSAPI) Specification V1.1, published by Microsoft and others (available on MSDN CD under Platform SDK|Setup and Systems Management Services|License Service Application Programming Interface, January 28, 1993.

LUM Requirements

Requirements for the Software License Management Work Group; Systems Management Workgroup; UNIX International System Management Workgroup; Revision 3; July 23, 1992.