Skip to content

LICENSING – NETWORK LICENSING

August 7, 2009
tags:
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.
They 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.
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.
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.
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).
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.
Using a Reservable License
The user invokes the application.
The application requests a reserved license from the nodelocked license server.
The central registry license server checks its database for a reserved license and the user file for authorization.
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.
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.
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.
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.
Per-seat licenses are valid only for customer-managed use products.
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 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.
Advertisements
No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: