Home

	Expand Search

Enterprise Event Broker Installation Guide

Appendix A Sybase System Asset Management (SySAM)

Chapter 4

Sybase System Asset Management (SySAM)

Introduction

SySAM "checks out" licensed features to users, and checks them back in when they are no longer needed. The basic components of SySAM are:

• Asset management software, which consists of a license management daemon and a Sybase daemon

• One or more license files (license.dat)

• One or more components with SySAM support

If you are upgrading from SEEB 1.0 to 2.0, the old license.dat file can no longer be used for license management. You must use SySAM and the license.dat file that it generates when you register licensed products.

When you start EAServer and Enterprise Event Broker, they attempt to locate the license file, by default, in:

• On Windows NT: %SYBASE%\SYSAM-1_0\licenses\license.dat

• On UNIX: $SYBASE/SYSAM-1_0/licenses/license.dat

For SEEB, the license file location is set using the EAServer property com.sybase.seeb.LicensePath. See Table 2-1 for information about the property.

For EAServer, if the licenses file does not exist, it looks for the license file specified in the environment variable LM_LICENSE_FILE.

The license file contains a pointer to the SySAM software, or to a remote machine on which SySAM is running. SySAM consists of:

• lmgrd - the license management daemon

• SYBASE - the daemon that launches Sybase modules

• lmutil - a utility to manage licensing activities

The daemons handle requests to check in or check out licensed features, as shown in Figure 4-1.

Using information in the license file, EAServer or Enterprise Event Broker connects to SySAM and tries to check out its license. If the license is checked out successfully, EAServer or Enterprise Event Broker continues to boot and enables optional features.

Licensed features enabled through SySAM

Table A-1 describes the features that are enabled through SySAM, and the license names in the license.dat file.

EAServer and Enterprise Event Broker must be registered before any features are enabled.

Types of SySAM systems

The basic components of SySAM can be arranged for a standalone server, for a collection of servers on a network accessing a centralized license host, and with multiple, redundant servers across a LAN or a WAN, for backup and load-balancing purposes.

Standalone system

In a standalone system, all of the SySAM components shown in Figure 4-1 reside on a single machine. The license file points directly to the asset management software, which runs on the same machine. This machine is called the license host.

The instructions in "Installation tasks" assume you are installing EAServer and Enterprise Event Broker on the same machine as a standalone system.

Network system

On a network, the license host runs SySAM, which handles check-in and check-out requests from all secondary servers, as shown in Figure 4-2.

In a network system, the license files for remote servers contain only pointers to the license host. Secondary servers check out licenses from the license host through the SySAM software.

If you are using networked software asset management system, you must install the software on the license host before installing it on secondary servers. See "Using SySAM in a networked environment" for instructions.

Redundant servers

As part of a failover plan or a load-balancing system, you can have multiple servers running the same EAServer configuration, using a redundant license across all servers. The redundant server system can be connected by a local-area network (LAN) or by a wide-area network (WAN).

A redundant server system is an excellent load-balancing mechanism for physically distant servers. The redundant license allows you to specify local servers as the first in the queue, and make remote servers available as backup. The SySAM application attempts to check out a license from a license-file list, starting with the first server. If that server fails for any reason, the second server in the list is contacted, and so on.

The redundant server system also provides failover protection. If one server in the list goes down for any reason, the second server responds to the license request. If that server fails, too, the next server in the list is contacted, and so on.

See "Setting up redundant servers".

Using SySAM in a networked environment

This section describes how to install the SySAM software on the license host before installing it on the second servers.

When you install EAServer and Enterprise Event Broker on secondary servers, you must configure the servers to access SySAM on the license host. This section describes how to register EAServer and Enterprise Event Broker packages with the license host.

The following instructions apply to SySAM installations on to secondary servers, as well.

1. Install EAServer and Enterprise Event Broker using the instructions in Chapter 2, "Installation Instructions."

2. When prompted: "Do you have a Sybase Software Asset Management Certificate to register?"

   Click No.

3. The installer prompts: "Have you registered Sybase Software Asset Management Certificates at a central license host?"

   Click Yes.

4. Enter the following information about the primary server from which this machine accesses EAServer and Enterprise Event Broker:

   • • License Manager Host is the host name of the license host where you installed the SySAM software.

     • License Manager Port is the designated port number used by SySAM on the license host.

   • Click OK to begin the configuration.

     See the instructions in "Post-installation tasks" to complete the configuration.

Setting up redundant servers

As part of a failover plan or a load-balancing system, you may have multiple servers running the same EAServer and Enterprise Event Broker configurations, using a redundant license across all servers. The redundant servers can be connected by LAN or by WAN.

See the following chapters in the Jaguar System Administration Guide for a description of load-balancing and failover options:

• Chapter 3, "Jaguar Clusters and Synchronization"

• Chapter 4, "Load Balancing, Failover, and Component Availability"

1. Follow the instructions in this guide to install EAServer and Enterprise Event Broker on each of the redundant servers.

2. As you install the software, make note of the machine names and the dedicated port number that SySAM uses on each machine.

   The Studio Installer automatically returns the machine name and a valid port number by default.

3. On each machine in the redundant system, enter in the License Manager window:

   • Order Number

   • Feature Name

   • Feature Count

   • Software Version

   • Authorization Code

   The certificate information is provided in your EAServer and Enterprise Event Broker package on a printed Sybase Software Asset Management certificate.

4. Click Continue Install.

   Complete the installation of EAServer and Enterprise Event Broker according to the instructions in Chapter 2, "Installation Instructions".

5. On each machine in the redundant system, set the LM_LICENSE_FILE environment variable to:

   • "port@machine:port@machine:port@machine"

     .

     For example, if you use port 29722 on each machine and the machine names are Huey, Dewey, and Louie, the environment variable that points to the license file would look like this:

     LM_LICENSE_FILE="29722@huey:29722@dewey:29722@louie"

     The redundant license allows you to place a local server first in the license list, making it the first server queued by the licensing software. In this manner, you can place remote servers later in the list so that they are queued only after the local server, facilitating load-balancing across distant servers.

Registering licenses after installation

You must license EAServer and Enterprise Event Broker to enable many of the features. If you elected not to license features during the initial installation, you can restart the license manager and register the features after installation.

1. Start the license manager manually. On Windows NT, select Start | Programs | Sybase | SySAM from the Windows task bar.

   On UNIX, run the lmgr.sh script file in the $SYBASE/SYSAM-1_0/bin directory.

2. This launches the Studio Installer, which prompts: "Do you have a Sybase Software Asset Management Certificate to register?"

   Click Yes.

3. Enter:

   • Order Number

   • Feature Name

   • Feature Count

   • Software Version

   • Authorization Code

   The certificate information is provided in your Enterprise Event Broker package on a printed Sybase Software Asset Management certificate.

4. Click Done.