HP OpenVMS Systems
HP Advanced Server for OpenVMS
If the file server offers server-based licensing, and a sufficient number of server-based licenses are available, the client computer needs no special software for requesting and storing the Advanced Server license. However, if the licenses are managed as client-based licenses, the client computer must have PATHWORKS client licensing software to request and store Advanced Server licenses.
The PATHWORKS client licensing software is automatically installed and configured as part of the PATHWORKS client software installation procedure. Therefore, if the client is running HP PATHWORKS 32, no additional client licensing software is needed.
If the client computer is not running PATHWORKS client software (for example, on a retail Windows XP workstation), the PATHWORKS client licensing software components (Client License Requester and Client License Transponder) must be loaded and set up on the client computer to request and store Advanced Server client-based licenses.
These client components are available on the file server system after you install the file server software. For information about loading and customizing the client software for client-based licensing, refer to the README.TXT file provided with the Advanced Server PWLICENSE share on the file server.
The PATHWORKS 32 system license PWXXWINAT07.nn:
The License Server included with the Advanced Server will not issue or manage PATHWORKS for OpenVMS (NetWare) licenses. If you have clients using NetWare networking software, maintain the existing version of the License Server on a different system from the one that is running Advanced Server.
In either case, the license required to access each version of the file server is listed in Table 1-1, File Server Licenses.
|To access this file server...||The client needs this Client Access license...|
|PATHWORKS for OpenVMS (Advanced Server)||
One of the following:
|Advanced Server V7.2 for OpenVMS||
One of the following:
|Advanced Server V7.3B for OpenVMS||PWLMXXXCA07.03|
These licenses can be configured to be used as either client-based licenses, as server-based licenses, or as a combination of both.
Clients currently using client-based licenses to access PATHWORKS V6 for OpenVMS (Advanced Server)
servers need not be changed. These clients will continue to access
PATHWORKS for OpenVMS (Advanced Server) servers using their client-based license. However, to
access the Advanced Server for OpenVMS, they must obtain a new client-based license
or a server-based license must be available for them on the file server
1.2.1 Server-Based License Management
Server-based licensing grants a specific number of clients connected to
a file server (on a first-come, first-served basis) the right to use
server software on a single server and allows clients access to file
and print services resident on the server.
220.127.116.11 When to Use Server-Based License Management
Server-based licensing is best suited for clients that need access to file and print services on a single server, or for a large number of clients that need occasional access to file and print services. Server-based licenses:
On a file server that is not running the License Server, Client Access licenses loaded into LMF are automatically used as server-based licenses. From a license management point of view, this is the simplest form of management and does not require use of the PATHWORKS client licensing software, or performing management tasks with the License Manager. License management consists of loading the appropriate Client Access PAKs information into LMF on the file server node.
When a client connects to the file server, one server-based license is consumed and the client is granted access to the file server. If there are no server-based licenses available when the client requests a connection to the file server, the connection request is denied.
After a server-based license has been used to grant a client access to a file server, the client is licensed to access resources on that server until the client disconnects from the file server.
When the client disconnects from the file server, the license assigned to that client is released (except with Windows clients, as noted below), the number of available server-based licenses is incremented, and the license becomes available for another client.
In addition to the session that the client establishes when a share is initially mapped, Windows client systems typically establish a second session with the file server. This session uses a null (blank) user name and connects to the IPC$ share. While this second session will not cause the client to consume two server-based licenses, it might prevent the client from releasing the server-based license when the user disconnects all mapped drives. Use the ADMINISTER SHOW SESSIONS command to view client sessions on the file server. If necessary, terminate the client session, using the following ADMINISTER command, where computer-name is the computer name of the Windows NT client:
When using server-based licenses for access to file and print services in an OpenVMS Cluster environment, HP recommends that clients connect to the cluster using the Advanced Server cluster alias, if this option is available. Clients connecting using the alias consume one server-based license. Clients connecting directly to specific cluster members consume one server-based license for each connection to a different cluster member.
A client can map multiple drives and printers to a single server while
consuming a single server-based license.
1.2.2 Client-Based License Management
A client-based license is assigned on a per-workstation basis. A client-based license for accessing OpenVMS file servers allows a client to access multiple file servers with the single license. Client-based licenses are managed using LMF, the License Server, and the License Manager.
After a client-based license has been assigned to a client, the license applies only to that client until it is revoked or released. After a license has been revoked, it is available for assignment by the License Server. To revoke a client license, use the License Manager.
A license PAK is loaded in the LMF database on the system running the
License Server. The License Server assigns a client-based license upon
request for a license by a client. After the client receives the
license, it is stored on the client.
18.104.22.168 How Client-Based License Management Operates
These interactions require no specific actions on the part of a user
once a client is configured to use client-based license management.
1.2.3 Combining Server-Based and Client-Based License Management
Appropriate client-based licensing assures access to file servers.
Clients that do not have client-based licenses may access a file server
if sufficient server-based license capacity exists.
22.214.171.124 How Combined License Management Operates
In a combined-license environment, licenses are loaded in the LMF
database on the system running the file server and the License Server.
Client Access licenses loaded into LMF are automatically loaded by the
License Server. When the licenses are first loaded by the License
Server, they are allocated to the Default license group to be used as
client-based licenses. The License Manager allows you to allocate any
number of these licenses to the Server-Based license group so that they
can be used for server-based licensing. The remaining licenses, those
in the Default group, or allocated to other license groups, are managed
as client-based licenses.
1.3 License Management Tasks
If the licensing environment consists of only server-based licensing, it is not necessary to use the License Manager. When the licensing environment includes client-based licensing, or a combination of client-based and server based licensing, the License Manager is an invaluable tool for managing the licensing software.
The tasks you perform with the License Manager include:
To organize client-based licenses into groups, you must take additional steps when configuring your client software. Specifically, you must configure your clients to request a license from a particular license group. See Chapter 5, Configuring Client Software, for more information.
License management can be nearly transparent to both system administrators and users. However, the License Manager provides optional capabilities that allow you to configure your server in a way that best supports your computing environment. This configuration may include client-based licensing, or a combination of client-based and server-based licensing.
This chapter describes how to set up the Advanced Server for server-based licensing, for client-based licensing, and for a combination of client-based and server-based licensing. It also provides a set of examples of licensing setup. In addition, this chapter includes information about configuration parameter values in effect when the License Server and License Registrar are running. All this information is presented in the following sections:
When the License Server is not configured to run with your file server,
the file server assumes that any Client Access licenses found on the
system are to be used as server-based licenses for licensing client
access. After you start the file server, unlicensed clients connecting
to the file server will be licensed without any further setup or
2.1.1 Setting Up Server-Based Licensing Only, for Performance Gains
$! Define_sys PWRK$Lr_Disable_Client_Ping 1 ! Disable Client license checking
If this logical is not defined or given the default value of 0, even if only server-based licensing is configured, the License Registrar first checks whether a client attempting to connect to the file server has a valid client-based license. Defining this logical with a nonzero value, as in the example, prevents the License Registrar from checking for a client-based license. Instead, it attempts immediately to assign a server-based license. This can improve performance.
This logical does not affect or change the number of licenses assigned to the server-based group, the default client-based license group, or any user-defined license groups.
With this setup the client-based license of any connecting client is ignored. If you do not use client-based license on your network, then the above setup is the preferred configuration.
For a configuration that supports client-based licensing, there are additional steps required for setting up the system. This configuration requires the use of the License Server and loading client software. If you decide to configure the OpenVMS system to run the License Server, the default is to allocate all Client Access licenses on the system as client-based licenses.
Follow these steps to support client-based licenses:
2.3 Setting Up Combined Client-Based and Server-Based License Management
For a configuration that supports both client-based and server-based
licensing, you must use the License Manager to specify how many
licenses are to be used as server-based and how many are to be used as
Follow these steps to configure the License Server to support both client-based and server-based licensing: