How NLS Works

The following figure illustrates how NLS Works.

The following list describes how License Service Providers (license service providers) handle requests from NLS clients by interacting with the eDirectory database.

1. An application issues a request to the NLS client.

   In NetWare, for example, the server requests a license unit on behalf of the user that is connecting to the server. The server issues this request to the NLS client.

2. The NLS client library packages the request from the application and submits it to an license service provider.

   In NetWare, for example, the NLS client communicates with the license service provider on that server.

3. The license service provider examines the request and determines whether it can fill the request. It does this by checking the eDirectory context of the requesting client for the specific information or license unit being requested.

   In NetWare, for example, the license service provider searches the user's context for a NetWare license unit.

4. If the requested resource is available, the license service provider fills the request. If the license service provider cannot fill the request, it searches for a resource. Where an license service provider starts its search for a resource depends on what the requesting application has specified.

   The license service provider can check the next-higher context in eDirectory for the requested resources. The license service provider continues to search until it reaches the [Root] or Tree of the partition or the top of the tree, depending on how the license service provider is configured.

   In NetWare, for example, the license service provider starts in the user's context and searches up the eDirectory tree for a user license.

   The following figure illustrates how an license service provider searches for a license certificate in the User Access Licensing model.

   
   

   In this example, the user accesses the network from context .E.C.A. To search for a license unit, the license service provider begins its search in the user's context---.E.C.A The license service provider searches up the tree to context A and finds an available license unit.

5. The license service provider returns status to the client library.

   In NetWare, for example, if the license service provider finds a NetWare license unit, it returns a successful status to the library. Otherwise, it returns an error code.

6. The library returns status to the application.

   In NetWare, for example, the library returns licensing status to the server.

7. The application determines action based upon the status of license units.

   In NetWare, for example, the server determines an action. If the status is successful, the server allows a connection to the server. Otherwise, the server allows a grace connection if one is available, or denies service if a grace connection isn't available.