Licensing

This appendix describes how licensing is configured for Publisher. It contains the following sections:

Licensing Overview

In order to function, Publisher requires a valid license key on each Publisher server in the environment. The license file containing this key must be located in the BEA_HOME directory.

Depending on your use case, a different type of license is used. Each license type is defined by the license attributes that govern the behavior of the licensed installation. The following table lists the license types, the most important attributes for each type, and how the license should be obtained.

Table B-1 Use Cases and Corresponding License Types
License Type	Key Attribute	Obtainment Method
Standard Evaluation	Session Limit and Expiration: Standard Evaluation licenses will allow up to 10 concurrent user sessions and the licenses will expire on a specific date.	Standard Evaluation licenses are automatically generated by the Publisher installer.
Extended Evaluation	Expiration: Extended Evaluation licenses expire on a specific date.	Extended Evaluation licenses are obtained by contacting a BEA sales representative.
Production	IP: Product licenses are only valid on a specific IP or within a specific IP range.	Existing customers can obtain Product licenses through elicense.bea.com or licensing@bea.com.

Installation Behavior

By default, the installer attempts to install a Standard Evaluation license file containing a Publisher key in the BEA_HOME directory.

If a license.bea file exists in the specified location, then the installer prompts you to merge a Standard Evaluation license with the existing license, overwrite the existing license with a Standard Evaluation license, or leave the existing license alone. If you elect to overwrite the existing license, then the installer places a backup of the existing license into the BEA_HOME directory.

If you are installing Publisher on a machine with another BEA product on it (for example, BEA WebLogic Server, AquaLogic Interaction, AquaLogic Interaction Analytics, or AquaLogic Interaction Grid Search), choose to merge the license files when prompted by the installer.

Upgrade Behavior

Subsequent installs of a Publisher instance obey the same logic described in the Installation Behavior section. When upgrading to a new major or minor version of Publisher, it is necessary to upgrade the license file. When prompted by the installer during upgrade, choose to merge the license files if there are other BEA products installed on the machine. Choose to overwrite the existing license file with a Standard Evaluation license if only Publisher is installed on the machine. For details on merging license files, see Merging License Keys.

When installing the new Production license key, you do not need to run the installer again to change license keys; you only need to replace the existing license file with the new version’s license file, then restart your Publisher instance. For details, see Upgrading an Existing License.

Upgrading an Existing License

If you are upgrading an existing license to an Extended Evaluation license or a Production license, you can either combine the license keys or replace the existing license file with the new license file.

If you are upgrading a license on a machine with another BEA product on it (for example, BEA WebLogic Server, AquaLogic Interaction, AquaLogic Interaction Analytics, or AquaLogic Interaction Grid Search), you must merge the license keys for both products into a single file. For more information on merging license keys, see Merging License Keys.

Merging License Keys

To manually combine two or more license keys into the license.bea file, either use a text editor or the tool provided in BEA_HOME.

The path to java.exe must be in the PATH variable. Use the following command to execute the tool:

Unix: ./UpdateLicense.sh <new_license_file>
Windows: UpdateLicense.cmd <new_license_file>

Replace <new_license_file> with the name of the file containing the license key you wish to add to license.bea.

Example - License File

The following is an example of a license.bea file with a Publisher Evaluation key:

<?xml version="1.0" encoding="ISO-8859-1"?>

<bea-licenses>

    <license-group format="1.0" product="AquaLogic Interaction Publisher" release="6.4">

        <license

            component="Publisher"

            content_items="100"

            cpus="unvalued"

            expiration="2007-3-16"

            ip="any"

            licensee="BEA Evaluation Customer"

            type="EVALU"

            users="unlimited"

            signature="MC0CFQCydgctZJYaYNa9KLR0uAsQZm1VRwIUe/BGzjzyghfEB/6nF9ZWKCfiYU4="

/>

</license-group>

</bea-licenses>

Installation and Upgrade Guide