Nodelocked Licenses
A nodelocked license allows the use of a product on the particular machine for which the license was created for as long as the license remains valid. Vendors typically use nodelocked licenses for standalone, rather than client/server, applications. A vendor who is enabling a product using nodelocked licenses can choose between two license-enabling models: non-runtime-based and runtime-based. If the vendor chooses non-runtime-based enabling, the license-enabled product will not need the License Use Runtime to be installed. The password for such a product is stored in a file called the nodelock file. The application checks the nodelock file to be sure a valid license is available. If the vendor chooses runtime-based enabling, management of the nodelocked license is performed by the nodelocked license server on the local machine. The nodelocked license server is managed through the BLT, Basic License Tool, which enables you to view and update information about the nodelocked licenses on the machine and get reports about their use. Vendors can enable their products using the following kinds of nodelocked licenses: - Simple nodelocked licenses
- Concurrent nodelocked licenses
- Use-once nodelocked licenses
- Per-server licenses
 Back to top
Simple Nodelocked Licenses  A simple nodelocked license allows an unlimited number of simultaneous uses of the licensed application on the local machine. Simple nodelocked licenses are valid only for vendor-managed use products. A word processor is a typical example of a nodelocked licensed product.
The following picture shows the steps that happen when an end user invokes an application with nodelocked licenses for which the vendor chose non-runtime-based enabling. The licenses must be simple nodelocked licenses. 
Using a Nodelocked License (Non-Runtime-Based Enabling) The end user invokes the application. - The application checks the nodelock file to be sure a license is stored on the local system.
If there is a valid license in the nodelock file, the application runs. If not, depending on how the vendor enabled the application, it may return information to the end user, or it may run even with no license available. Concurrent Nodelocked Licenses  As with a simple nodelocked license, the concurrent nodelocked license is local to the node where the application has been installed. It allows a limited number of simultaneous uses of the licensed application. A typical example of a concurrent nodelocked license is a client/server application, where the application server is able to recognize the number of clients connected to it and ask for a license for each of them.
Vendors can use concurrent nodelocked licenses for both vendor-managed and customer-managed products. If the product is customer-managed, then when you enroll the product, you must specify how many concurrent nodelocked licenses you have acquired for the product. The end user can modify this number at any time. Back to top
Use-Once Nodelocked Licenses  A use-once nodelocked license permits a single use of a particular licensed product on a particular machine within the period for which the license is valid. Every time the product is started, one license is consumed.
A typical use of use-once nodelocked licenses is to distribute promotional or demonstration versions of software. Vendors also provide use-once nodelocked licenses to supplement concurrent nodelocked licenses during times when user demand for those products exceeds the number of available concurrent nodelocked licenses. The vendor designs the product so that when all concurrent nodelocked licenses for the product are in use, a user can request an available use-once license. Vendors can use use-once nodelocked licenses for both vendor-managed and customer-managed products. If the product is customer-managed, then when you enroll the licenses, you must specify how many use-once nodelocked licenses you have acquired for the product. The end user can modify this number at any time. The following picture shows the steps that happen when an end user invokes an application with nodelocked licenses for which the vendor chose runtime-based enabling. The licenses can be simple nodelocked, use-once nodelocked, or concurrent nodelocked licenses.
Using a Nodelocked License (Runtime-Based Enabling) The end user invokes the application. - The application requests a license from the nodelocked license server on the local system.
- The nodelocked license server checks that there is a valid license on the machine and that this user is authorized to use it.
If there is no nodelocked license but the application uses concurrent nodelocked licenses and implements the soft stop policy, the nodelocked license server checks for a soft stop license and checks the user file for authorization. - The nodelocked license server returns the status of the license request to the application.
If a license was found and granted, or if a soft stop license was granted, the application runs. If no license can be granted, depending on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available. Per-Server Licenses  Per-server licenses are exactly like concurrent nodelocked licenses, except that at any time, you can change them into per-seat licenses (see "Per-Seat Licenses").
Vendors use per-server/per-seat licenses to enable client/server applications constructed for multiple-server solutions. Both per-server and per-seat licenses make it possible for the server of a licensed client/server application to request licenses on behalf of its clients without the need for the application clients to be license-enabled. With per-server licensing, each application server license is associated with a specific number of application clients, representing the maximum number of application clients that may concurrently request services from that application server. The application client licenses are stored locally on the application server machine and are granted temporarily to requesting application clients. Multiple application servers grant licenses independently of one another; if the same application client connects to more than one application server, the application client is granted more than one license. Therefore it is recommended to use per-server licenses only in an environment where: - Each application client connects to only a single application server, or
- Each application client uses the application infrequently for brief periods.
When your environment grows in such a way that application clients are connecting to multiple application servers, you will probably want to convert your per-server licenses to per-seat. With per-seat licensing, unused application client licenses are kept in a central repository, which all the application servers share. They also share a central list of application clients to which a license has been assigned. When a license is assigned to an application client, that assignment is permanent. If an application client connects to multiple application servers, it is assigned only one license. Per-server licenses are valid only for customer-managed use products. The following figure shows the steps that happen when an end user invokes an application with per-server licenses when per-seat has not been enabled. In the figure, the application server is license-enabled. 
Using a Per-Server License The application client user invokes the application. - The application server requests a per-server license from the nodelocked license server. This is a license that you have stored on the nodelocked license server.
- The nodelocked license server checks the nodelocked license database for such a license and the user file for authorization.
If no license is found, but the application implements the soft stop policy, the nodelocked license server checks for a soft stop license. - The nodelocked license server returns the status of the request to the application server. If a license was found, or if a soft stop license was granted, the application runs.
If no license can be granted, dependin g on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available. Back to top
Network Licenses Network licenses, rather than being restricted to a single machine, are stored on a network license server and shared among multiple network license clients. Vendors can enable their products using the following kinds of network licenses: - Concurrent licenses
- Concurrent-offline licenses
- Reservable licenses
- Use-once licenses
- Per-seat licenses
Concurrent Licenses  A concurrent license is a network license that can be temporarily granted to run the licensed application on a client.
When the product is running, that license remains unavailable to other users of the product. When the product stops running the license is returned to the server, where it becomes available to other users. Concurrent licenses allow as many users to run a licensed software application simultaneously as there are valid licenses for the product available from the network license servers in your licensing environment. A typical use of concurrent licenses is for products with relatively expensive licenses that each user will use only part of the time. The customer orders fewer licenses than there are users to optimize use of the licenses. Such applications may be client/server applications for which the client is enabled, or non-client/server applications. Vendors can use concurrent licenses for both vendor-managed and customer-managed products. The following figure shows the steps that happen when an end user invokes an application with concurrent licenses. 
Using a Concurrent License The user invokes the application. - The application requests a license from the network license server.
- The network license server checks its license database for an available license and the user file for authorization.
- The network license server returns the status of the request to the application. If a license was found and granted, the application runs.
- If a network license was not found, and the application implements the soft stop policy, the application requests a soft stop license from the central registry license server.
- The central registry license server checks its database for a soft stop license and the user file for authorization.
- The central registry license server returns the status of the request to the application. If a soft stop license was granted, the application runs.
If no license can be granted, depending on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available. Back to top
Concurrent-offline Licenses  The concurrent-offline license allows users to reserve a concurrent license for a certain number of days and to use it on a portable computer disconnected from the network. Only authorized users can exploit this feature. The users must be defined by the license administrator at the customer site. The portable computer can use supported Windows platforms only, excluding Windows Millennium.
A concurrent-offline license is installed on the network license server. It is similar to a normal concurrent license because it can also be used as a normal concurrent license. For the duration of the reservation, the license remains unavailable to other users of the product. The license becomes available to other users when one of the following occurs: - The reservation period expires
- The license is returned to the server from the portable computer
Concurrent-offline licenses can be enrolled and administered only on a server running License Use Management Version 4.6.7 (or later), by means of a Basic License Tool 4.6.7 (or later). When the concurrent-offline license has been reserved for use, a copy is installed on a portable computer connected to the network. This copy of the concurrent-offline license is called an offline-nodelocked license. When the offline-nodelocked license has been installed on the portable computer, the portable computer can be disconnected from the network. The following figure shows the steps that happen when an end user invokes an application with concurrent-offline licenses. 
Using a Concurrent-offline License The user invokes the application. - The application looks for an offline-nodelocked license in its nodelocked file. If a license is found and is valid, the application runs.
- If the application does not find a license in the nodelocked file and the portable computer can reach a License Use Management network license server, the application requests a concurrent-offline license from it.
- The network license server checks if the license has an authorization for the user, group, or for the target ID of the machine, and validates the password provided by the user.
- If the authorization is for a concurrent-offline license, the server creates an offline-nodelocked license and copies it to the nodelocked file of the portable computer. The license is marked as in use on the server.
- The application checks that the nodelocked file contains a valid license and the application starts. The application can now run without a connection to the License Use Management network license server (that is, the application can run on a portable computer).
Note: At the end of the reservation period, the copy of the license stored in the nodelocked file of the portable computer expires (the license can also be returned by the user before the reservation period expires). The license can be used by another user both as a normal concurrent license and as a new offline-nodelocked license. Back to top
Reservable Licenses  A reservable license is a network license that you can reserve for the exclusive use of a user, a group, or a node. The reservation is for a specified time period. A reservable license that has been reserved is called a reserved license. A reservable license that has not been reserved is called an unreserved license.
When a reserved license is granted from the network, the license is stored on the workstation where the licensed application is running. Thereafter, the license can be used on the workstation, even if the workstation is disconnected from the network, until the reservation expires. A typical use of reservable licenses is for the client part of a client/server application that is likely to run on a portable computer that is often disconnected from the network. Another typical use is for a compiler being used in software development. During a build process involving many compilations, it is more efficient to reserve a compiler license for a day or two than to make a separate request for a compiler license for every compilation. You can reserve some of the reservable licenses for an application and leave others unreserved. Unreserved licenses are treated like concurrent licenses. Vendors can use reservable licenses for both vendor-managed and customer-managed products.
 Using a Reservable License The user invokes the application. - The application requests a reserved license from the nodelocked license server.
- The nodelocked license server checks its database for a reserved license. This is a license that you reserved for the user and that was granted to the user, and stored on the local machine, in response to a previous request.
- The nodelocked license server returns the status of the request to the application. If a license was found, the application runs.
- If the nodelocked license server does not find a license, the application requests a reserved license from the central registry license server. This is a license that you have reserved for this user, group, or workstation.
- The central registry license server checks its database for a reserved license and the user file for authorization.
- The central registry license server returns the status of the request to the application. If a reserved license was found and granted, it is stored in the nodelocked license server's database, and the application runs.
- If a reserved license was not found, the application requests a reservable license from the network license server. This is a reservable license that you have not reserved for anyone.
- The network license server checks its license database for a reservable license and the user file for authorization.
- The network license server returns the status of the request to the application. If a reservable license was found and granted, the application runs.
- If a reservable license was not found, and the application implements the soft stop policy, the application requests a soft stop reservable license from the central registry license server.
- The central registry license server checks its database for a soft stop reservable license and the user file for authorization.
- The central registry license server returns the status of the request to the application. If a soft stop license was granted, the application runs.
If no license can be granted, depending on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available.
Use-Once Licenses  A use-once license is a network license that permits a single use of a particular licensed product within the period for which the license is valid. Every time the product is started, one license is consumed.
A typical use of use-once licenses is to distribute promotional or demonstration versions of software. Vendors also provide use-once licenses for their products to supplement concurrent licenses during times when user demand for those products exceeds the number of available concurrent licenses. The vendor designs the product so that when all concurrent licenses for the product are in use, a user can request an available use-once license. Vendors can use use-once licenses for both vendor-managed and customer-managed products. The following figure shows the steps that happen when an end user invokes an application with use-once network licenses. 
Using a Use-Once Network License - The user invokes the application.
- The application requests a license from the network license server.
- The network license server checks its license database for an available license and the user file for authorization.
- The network license server returns the status of the request to the application. If a license was found and granted, the application runs, and one license is subtracted from the number of available use-once licenses.
If no license can be granted, depending on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available. Per-Seat Licenses  Vendors use per-server/per-seat licenses to enable client/server applications constructed for multiple-server solutions. Both per-server and per-seat licenses make it possible for the server of a licensed client/server application to request licenses on behalf of its clients without the need for the application clients to be license-enabled.
With per-seat licensing, unused application client licenses are kept in a central repository, which all the application servers share. They also share a central list of application clients to which a license has been assigned. When a license is assigned to an application client, that assignment is permanent. If an application client connects to multiple application servers, it is assigned only one license. You will probably want to use per-seat, rather than per-server, licenses in an environment where application clients connect to multiple application servers. (See also "Per-Server Licenses".). Per-seat licenses are valid only for customer-managed use products. The following figure shows the steps that happen when an end user invokes an application with per-server/per-seat licenses when per-seat has been enabled. In the figure, the application server is license-enabled. 
Using a Per-Seat License The application client user invokes the application. - The application server requests a per-seat license from the nodelocked license server. This is a license that has already been granted to the user on a previous request and stored on the local machine.
- The nodelocked license server checks the nodelocked license database for such a license.
- The nodelocked license server returns the status of the request to the application server. If a per-seat license was found, the application runs.
- If no per-seat license was found on the nodelocked license server, the application server requests a per-seat license from the central registry license server.
- The central registry license server checks whether a license is already being used by the requesting application client, possibly granted through another application server. In such a case the application can start without having a new license granted.
Otherwise, the central registry license server checks whether a per-seat license is available. If so, it grants the license and records the application client identifier. If no per-seat license is found, but the application implements the soft stop policy, the central registry license server checks for a soft stop license. - The central registry license server returns the status of the request to the application server.
- If a per-seat or soft stop license was granted, the application sends a shadow copy of the granted per-seat license to the nodelocked license server.
- The nodelocked license server adds the shadow copy to the nodelocked license database.
- The nodelocked license server returns the status of the request to the application server, and the application runs.
If no license can be granted, depending on how the vendor enabled the product, the application may return information to the end user, or it may run even with no license available. Back to top
| 
