License Administration Tasks

As an alternative to typing a server name, you may click Browse to display a list of network servers from which to select. Click the server for which you want to administer database licenses, then click OK.

Click Connect (or press Enter).

License Administrator accesses the specified server to determine the type of license required.

•

If you are not logged in to the server, a dialog appears to log in to the operating system (not the database engine).

On the login dialog, type the name of an operating system user for User Name. The user must have administrative privileges for the database engine. For Password, type the appropriate password for the user name you specified. Click Login. The server name appears in the License Administrator title bar and in the Server Name field.

Note: For servers running a previous version of PSQL, use the license utility provided with that version of the product.

►

To Authorize a Key

Note that the GUI License Administrator can be used for online authorization of a local machine connected to the Internet, and for remote authorization of the database engine on a machine not connected to the Internet.

Ensure that the server name in the title bar is the server for which you want to authorize a database engine key. If not, select a different server as described in To Select a Server for License Administration.

Enter the key in the Key field.

Lowercase letters are automatically converted to uppercase.

Press Enter or click the button to authorize the key.

The Key field is cleared if the key is successfully authorized.

Verify the new license information that appears in the License Information list. (If necessary, press F5 to refresh the list.)

The license is now active. You do not have to restart the database engine.

Note: When authorizing an increase key for user count, session count, or data in use, a permanent license must already exist. The vendor ID of the increase key must match the vendor ID of the permanent key.

Tip: Product authorization is tied to your machine’s hardware configuration. After you have authorized a product key on a machine, changes to certain hardware configuration items could disable the key. If you need to change hardware configuration, deauthorize the key first. Deauthorizing the key disassociates the product key from the unique hardware configuration. After you complete the hardware configuration changes, you can again authorize the product key.

►

To Display Remaining Authorizations

Ensure that the server name in the title bar is the correct server for this operation. If not, select a different server as described in To Select a Server for License Administration.

Click Remaining Authorizations.

The number of remaining authorizations displays for all product keys.

►

To Hide Expired Licenses

Ensure that the server name in the title bar is the server for which you want to hide expired licenses. If not, select a different server as described in To Select a Server for License Administration.

Click Hide Expired, if it is not already selected.

The list of licenses changes to exclude all expired licenses.

Note: The Hide Expired checkbox is selected by default and can be selected or cleared as needed.

►

To Deauthorize a Key

Note: Temporary licenses cannot be deauthorized. They expire at the end of their evaluation period.

Ensure that the server name in the title bar is the server from which you want to deauthorize a database license. If not, select a different server as described in To Select a Server for License Administration.

Click a Product name in the License Information list.

You can select multiple keys by holding down the Shift or Control keys and clicking the desired product names.

Click the button to deauthorize the key.

Note: You cannot deauthorize a key in a failed validation state. Either rectify the issue before deauthorizing or call PSQL support for assistance.

Tip: When you deauthorize a product key, all increase keys for user count, session count, or data in use associated with that product key are automatically deauthorized as well.

►

To Repair a Key

Tip: After you have applied a product key on a machine, changes to the hardware configuration can cause a key to fail validation or become disabled, requiring a repair. To avoid the need for a repair, deauthorize the key before changing the hardware configuration and authorize the key again after the new configuration is complete.

Ensure that the server name in the title bar is the server for which you want to repair a key. If not, select a different server as described in To Select a Server for License Administration.

In the License Information list, click the Product name of the product with the key you want to repair.

Click Repair.

In the dialog box that opens, confirm that this is a genuine copy of the software product. When the repair is done, a completion message is displayed.

►

To Display License Information

Ensure that the server name in the title bar is the server for which you want to administer database licenses. If not, select a different server as described in To Select a Server for License Administration.

View the information for the authorized licenses in the License Information list.

Note: You must first authorize a key to display information about the associated license, such as user count, session count, data in use, license type, expiration date and so forth. Once authorized, if the license is not what you want, you may deauthorize it provided the license it is not a temporary license. Temporary licenses expire on their own and cannot be deauthorized.

See To Authorize a Key and To Deauthorize a Key.

►

To Determine a Total User Count

Ensure that the server name in the title bar is the server for which you want determine a database user count. If not, select a different server as described in To Select a Server for License Administration.

For a particular product, total the user count values that appear in the License Information list in the “User Count” column. Exclude any values for expired temporary licenses.

For example, total all values for the PSQL Server product for the permanent license, all user count increases, and any temporary licenses that have not expired.

The sum is the total number of users who can concurrently connect to the database engine on the server.

Note: An easier way to determine the total user count is with Monitor. See Monitoring Resource Usage in Advanced Operations Guide. The “Maximum” value for User Count is the total user count for the permanent license, all user count increase licenses, and any temporary licenses that have not expired.

►

To Determine the Session Count Limit

Ensure that the server name in the title bar is the server for which you want determine a session count limit. If not, select a different server as described in To Select a Server for License Administration.

For a particular product, total the session count values that appear in the License Information list in the “Session Count” column. Exclude any values for expired temporary licenses.

For example, total all values for the permanent license, all session count increases, and any temporary licenses that have not expired. The sum is the total number of sessions that can concurrently connect to the database engine on the server for that particular product (the session count limit).

Note: An easier way to determine the session count limit is with Monitor. See Monitoring Resource Usage in Advanced Operations Guide. The “Maximum” value for Session Count is the session count limit for the permanent license, all session count increase licenses, and any temporary licenses that have not expired.

►

To Determine the Data in Use Limit

Ensure that the server name in the title bar is the server for which you want to determine a data in use limit. If not, select a different server as described in To Select a Server for License Administration.

For a particular product, total the data in use values that appear in the License Information list in the “Data In Use GB” column. Exclude any values for expired temporary licenses.

For example, total all values for the permanent license, all data in use increases, and any temporary licenses that have not expired. The sum is the maximum permitted amount in gigabytes for all concurrently open data files for that particular product.

Note: An easier way to determine the data in use limit is with Monitor. See Monitoring Resource Usage in Advanced Operations Guide. The “Maximum” value for Data in Use MB is the data in use limit for the permanent license, all data in use increase licenses, and any temporary licenses that have not expired.

Be aware that License Administrator uses gigabytes (GB) as the units because that is how data in use is associated with a key. Monitor uses megabytes (MB) as the units for resource usage and kilobytes (KB) for the size of an individual file. The different contexts require units appropriate for each context.

►

To Refresh the License Information List

Ensure that the server name in the title bar is the server you want. If not, select a different server as described in To Select a Server for License Administration.

Press the F5 key.

The information for applied licenses is re-displayed, and any information is cleared from the Key field.

The Server Name field is cleared then displays the machine name to which License Administrator is currently connected. For example, suppose License Administrator is connected to PVSW1 and you attempt to connect to PVSW2, which does not have a database engine running. License Administrator displays a message that it could not connect, and PVSW2 is displayed in the Server Name field. After you click the F5 key, PVSW1 is displayed in the field.

►

To Display Help

Click Help from the menu bar of the License Administrator. The License Administrator Graphical User Interface section opens. It enables you to identify and understand the purpose of the objects on the GUI.

To consult other areas of documentation about the License Administrator, access the Table of Contents for the documentation and click the desired area:

•

License Administration Concepts — to understand the basics of License Administrator

•

License Administrator Command Line Interface — to understand the options and parameters for the CLI

•

License Administration Tasks — to perform activities with License Administrator.

CLI Tasks

Note: All of the following tasks use the 32-bit clilcadm command. On 64-bit Windows systems, the name is w64clilcadm. On 64-bit Linux and OS X systems, it is clilcadm64, but clilcadm also works because it calls clilcadm64.

►

To Display Information about a Key

To display information about all keys, enter the following command:

clilcadm -i

To display information about a specific key, enter the following command:

clilcadm -i key

See License Administrator Command Line Options and Parameters for the columnar information returned by the -i option.

►

To Perform a Validation

To perform a validation, enter the following command:

clilcadm -t

Tip: To determine the product key postvalidation state and date, use the -i option to display information about the specific key.

►

To Display Remaining Authorizations

To display the remaining authorizations for all product keys, enter the following command:

clilcadm -n

To display the remaining authorizations for a specific key, enter the following command:

clilcadm -n key

Tip: To determine a product key, use the -i option to display information about all keys. See To Display Information about a Key.

►

To Authorize a Key

Enter the following command:

clilcadm -a key

Tip: When you authorize an increase key for user count, session count, or data in use, a permanent product key must already exist. The vendor ID of the increase key must match the vendor ID of the permanent key.

►

To Deauthorize a Key

Enter the following command:

clilcadm -d key

Tip: When you deauthorize a product key, all increase keys for user count, session count, or data in use associated with that product key are automatically deauthorized as well.

►

To Remove Keys Without Deauthorizing

Circumstances can occur for which you need to remove a key and its associated increase keys for user count, session count, or data in use without deauthorizing the product. This action is called “clearing” a key.

To clear a specific key, enter the following command, where key is the individual key you want to clear:

clilcadm -c key

To clear all keys, enter the following command:

clilcadm -c

With either command, you can include the “force” parameter if you want to suppress the clear confirmation message.

Example: clilcadm -c force

►

To Repair a Key

Enter the following command:

clilcadm -e key

The command window displays a message asking you to confirm that this is a genuine copy of the software product. Enter “A” to confirm. After the repair is complete, the command window displays a message confirming the repair.

►

To Display Help

Enter either of the following commands:

clilcadm -<help | h>

clilcadm ?

Alternative Authorization Tasks

PSQL provides some alternate ways to authorize and deauthorize your PSQL product. If possible, however, authorize PSQL using online authorization. If the machine where PSQL is installed has only remote internet access, you can authorize remotely.

Tip: See To Authorize a Key for information on online authorization.

►

To Authorize a Key Remotely

Note that the GUI License Administrator can also be used for remote authorization if you connect to a remote database engine.

At a command prompt, enter the following command:

clilcadm -a key -<server|s> servername -<username|u> username -<password|p> password

If the machine where PSQL is installed does not have internet access, offline authorization is available.

►

To Deauthorize a Key Remotely

At a command prompt, enter the following command:

clilcadm -d key -<server|s> servername -<username|u> username -<password|p> password

Tip: When you deauthorize a product key, all increase keys (user count, session key, or data in use) associated with that product key are automatically deauthorized as well.

►

To Authorize a Key Offline

Only consider offline authorization if the machine on which you are running PSQL does not have internet access. Offline authorization involves three tasks using two machines. For example, machine A needs to authorize the PSQL product but has no Internet connectivity. Machine B has no PSQL installation but has Internet connectivity.

Task 1 - Generate Authorization Request Data

On machine A, enter the following at a command prompt:

clilcadm -<generate|g> product_key output_filename.ath

Save the file to a portable storage device or in a location that can be easily accessed by the machine that has Internet connectivity.

Tip: If the machine with Internet connectivity does not have PSQL installed, you must also copy the licgetauth.exe file from the PSQL \bin folder to the portable storage device or remote location.

Task 2 - Transmit Authorization Request Data and Retrieve Authorization Key Data

On machine B, connect to the portable storage device or access the location where you saved the Authorization Request Data file.

Enter the following at a command prompt, where output_filename.ath is the file you created in step 1 of task 1:

licgetauth.exe output_filename.ath

The above command retrieves the Authorization Key Data used to authorize the key and the product. The authorization key data is saved as a .pky file to the same location where you saved the authorization request file.

Tip: If you saved the Authorization Request Data and Authorization Key Data files to a hard drive, you will need to copy these files to either a portable storage device or a remote location.

Task 3 - Install Authorization Key Data

Back at machine A, connect once more to the portable storage device or access the location where the authorization key data was saved.

Enter the following at a command prompt, where authorization_filename.pky is the file created in step 2 of task 2:

clilcadm -a authorization_filename.pky

PSQL is now authorized.

►

To Deauthorize a Key Offline

Deauthorizing a key offline requires that you contact PSQL Support.

Telephone Authorization

In the event that it is not possible to authorize keys online, remotely, or offline, you can authorize PSQL Server, PSQL Vx Server, or Workgroup using telephone authorization.

Telephone authorization requires that you have completed a successful installation of PSQL Server or Workgroup and have a valid product key. If you do not have a product key, you can obtain one from Actian Corporation or your software vendor. Telephone authorization is available by calling 1.800.287.4383 toll-free in the United States or 00800.1212.3434 toll-free in Europe.

To authorize a key via telephone authorization, you can use the command-line utility or the PSQL Phone Authorization Wizard. The Phone Authorization Wizard is available on Windows, Linux, and OS X and guides you through the steps necessary to authorize your PSQL product.

Tip: When authorizing the Workgroup Engine, you need to elevate the privileges of the database engine before authorizing a key with a licensing utility.

►

To Authorize a Key Using the PSQL Phone Authorization Wizard

Ensure that you have completed a successful installation of PSQL Server or Workgroup and a have a valid product key. See also Telephone Authorization.

At a command prompt on the machine where the engine is installed, type guipaadm.

►

To Authorize a Key Using the Command-line Phone Authorization Utility

Ensure that you have a valid product key. See To Display Information about a Key. If you do not have a product key, you may obtain one from Actian Corporation.

At a command prompt on the machine where the engine is installed, type the utility name appropriate for your platform:

•

clipaadm.exe (Windows 32-bit)

•

w64clipaadm.exe (Windows 64-bit)

•

clipaadm (Linux or OS X)

At the prompt, enter the product key you want to authorize.

The PSQL Phone Authorization Utility returns an authorization code you will use to complete telephone authorization.

Perform one of the following actions to complete telephone authorization:

•

If you obtained your product key from Actian Corporation, call 1-800-287-4383 (U. S. toll-free) or 00800.1212.3434 (Europe toll-free) to complete telephone authorization with Actian Corporation personnel. We will provide you with an authorization key data string which you will enter as the final step of authorization.

•

If you did not obtain your product key from Actian Corporation, contact the vendor or original equipment manufacturer (OEM) from whom you obtained the key. The vendor or OEM personnel will assist you to complete telephone authorization.

Telephone Deauthorization

Telephone deauthorization is not available. If you authorized PSQL using telephone authorization, you must call Actian Corporation to deauthorize.

Notification Viewer

The Notification Viewer is a utility for displaying messages logged by the licensing components. The purpose of the utility is to inform you of noteworthy licensing messages in a noticeable but unobtrusive manner. Although not part of License Administrator, Notification Viewer is mentioned here because of its allied purpose pertaining to licensing.

►

To View Licensing Messages in Logging Repositories

See the following topic in Advanced Operations Guide for the repository in which you are interested:

•

Notification Viewer

•

Operating System Event Log

•

PSQL Event Log (pvsw.log)