Home

	Expand Search

Installation Guide Adaptive Server Enterprise for Linux/Intel

Chapter 3 Sybase Software Asset Management (SySAM)

Chapter 3

Sybase Software Asset Management (SySAM)

This chapter describes licensing concepts that you need to know before you begin installing Adaptive Server.

Sybase recommends that you read through this chapter before beginning the installation of Adaptive Server in the enterprise environment.

This chapter describes important concepts regarding how to license optional Adaptive Server features, add new licenses to existing servers, set up the license manager in a network environment, and set up redundant servers for high-availability and failover using Sybase Software Asset Management (SySAM).

You will need to refer back to this chapter when you begin installing Adaptive Server in a network environment.

SySAM overview

SySAM (Sybase Software Asset Manager) is a licensing mechanism that:

• Provides System Administrators with a means to monitor their site's use of Sybase products and optional features.

• Enables select Adaptive Server 12.5 features.

• Enables failover to other registered installations of Adaptive Server in the event of failure.

Adaptive Server features licensed through SySAM

The Adaptive Server Enterprise license must be registered through SySAM before any of the optional features can be enabled.

Table 3-1 describes the Adaptive Server features that are licensed through SySAM.

The Full-text search engine has been enhanced and now requires a license to install and configure.

If you plan to use Adaptive Server 12.5 with Replication Server, DirectConnect, or OpenSwitch, you must upgrade those products to the latest versions to ensure compatibility with new features from Adaptive Server 12.5.

How SySAM works

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

• One or more Adaptive Server features

• One or more license files

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

Figure 3-1 shows the relationship between these components.

When you start Adaptive Server 12.5, it attempts to locate the license file license.dat located in $SYBASE/$SYBASE_SYSAM/licenses. If the file does not exist, Adaptive Server looks for the license file specified in the environment variable LM_LICENSE_FILE.

The license file contains a pointer to the SySAM software on the primary server known as the license host, or to a remote license host where SySAM is running. SySAM consists of a utility, lmutil, to manage licensing activities, and two daemons--the license management daemon, lmgrd, and the SYBASE daemon. The daemons handle requests to check in or check out licensed features, as shown in Figure 3-1.

Using information in the license file, Adaptive Server connects to SySAM and attempts to check out a license (ASE_SERVER) for the base Adaptive Server product. If the ASE_SERVER license is checked out successfully, Adaptive Server continues to boot and attempts to check out any optional features enabled in server_name.cfg.

If Adaptive Server is configured to use optional features, such as distributed transaction management (ASE_DTM) or Java in Adaptive Server (ASE_JAVA), it attempts to check out licenses for those features during the start-up process. If a license is not available for an optional feature, Adaptive Server still starts, but the feature cannot be used.

Optional features can be turned on or off using sp_configure parameters. Table 3-2 lists the parameters used to configure optional features.

Adaptive Server's support for distributed transaction management protocols: XA and Microsoft DTC protocols, requires configuration parameter enable DTM to be set and also a license to be available.

Distributed transaction management support through Adaptive Server Transaction Coordinator requires configuration parameter enable xact coordination to be set. However, this feature is available with no license requirements.

By default, the configuration parameters for optional features are set to 0 (off). To enable an optional feature, use sp_configure to set its configuration parameter to 1, and restart Adaptive Server.

Some features require additional preparation before you can use them. For more information, see Table 3-2 and the Adaptive Server Configuration Guide.

• For information about configuring Adaptive Server with Distributed Transaction, see Using Adaptive Server Distributed Transaction Management Features.

• For information about configuring Adaptive Server Full Text Search capabilities, see Full Text Search Specialty Data Store User's Guide.

• For information about Java in Adaptive Server, see Java in Adaptive Server Enterprise.

• For information about lightweight directory services, see the System Administration Guide.

• For information about advanced security mechanisms, see the Component Integration Services User's Guide.

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 primary license host, and with multiple, redundant servers across a LAN or a WAN, for back-up and load-balancing purposes.

The procedures for registering licenses depend on which instance of Adaptive Server (primary or secondary license host) you are installing.

Standalone system

In a standalone system all of the SySAM components shown in Figure 3-2 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.

Network system

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

The license files for secondary 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.

Redundant servers

As part of a failover plan or a load-balancing system, you can have multiple servers running the same Adaptive Server configuration, using a redundant licenses 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.

SySAM in the network environment

Before you begin installing additional Adaptive Servers in a network system, the license manager must be installed and running on the license host. To verify that the license manager is running, see "SySAM administration".

To install Adaptive Server on secondary servers, you need to have your Sybase License Certificate available. Also, you need to know:

• The host name of the license host.

• The port number on the license host where the asset manager listens for connections.

• The asset management software installation directory on the license host.

When installing Adaptive Server on secondary servers, the license manager prompts you for licenses after the installer has installed the products on to the hard drive.

1. The license manager prompts: "Do you have Sybase Software Asset Management Certificates to register?"

   Click No.

2. Next, it prompts: "Have you registered Sybase Software Asset Management Certificates at a central license host?"

   Click Yes.

3. Enter the following information about the license host from which this machine will be checking out Adaptive Server licenses:

   • License Manager Host is the host name of the license host on which you installed the asset management software.

   • License Manager Port is an unused port number on the License host. The local Adaptive Server uses this port number to contact the primary network node when checking out licenses.

4. Click OK.

   Continue with the installation procedures described in Chapter 4, "Installing Sybase Servers ."

   See the Chapter 6, "Installing Sybase PC-Client Products " if you need help configuring client products.

As part of a failover plan or a load-balancing system, you may have multiple servers running the same Adaptive Server configuration, using redundant licenses across all servers. The redundant servers can be connected by LAN or by WAN.

To configure redundant servers:

1. Follow the instructions in this guide to install Adaptive Server on each of the servers in the redundant system.

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

3. For each machine in the redundant system, when the license manager prompts for license information, enter:

   • Order Number

   • Feature Name

   • Feature Count

   • Software Version

   • Authorization Code

   The certificate information is provided in your Adaptive Server package on a printed Sybase Software Asset Management Certificate.

4. Click Done when you have entered all licenses.

   Complete the installation of Adaptive Server. See Chapter 4, "Installing Sybase Servers ".

5. After the installation is completed, and for each server 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 first server in the license list is the first server queued by the licensing software.

SySAM administration

If you are installing servers in a network environment, SySAM must be installed and running on the license host before installing Adaptive Server on additional servers. This section describes how to start SySAM manually or as an automatic service, and other SySAM administration information.

Verify the software is running

To verify that the software is running:

When the lmgrd daemon starts, it automatically starts up the SYBASE daemon. To verify that the license management software is running on the system. Use:

$SYBASE/SYSAM-1_0/bin/lmutil lmstat -c

Make sure that both lmgrd and SYBASE are running, i.e. "up" before you continue the installation or start Adaptive Server.

If the SySAM software is not running, see Starting the software manually.

Starting the software manually

If the license manager is not running, you must start the license manager manually.

• Use the UNIX command:

  $SYBASE/$SYBASE_SYSAM/bin/lmgrd -c 
  $LM_LICENSE_FILE &

• Alternatively, run the startd.sh script in the bin directory:

  $SYBASE/$SYBASE_SYSAM/bin/startd.sh $SYBASE/$SYBASE_SYSAM

Adding feature licenses

This section describes how to update the license file to enable Adaptive Server features.

To add features for which you have licenses:

1. Enable the new feature. See "Starting Adaptive Server with optional features".

2. Shut down Adaptive Server. See Chapter 7, "Starting and Stopping Servers."

3. Verify that the license manager software is running. See "SySAM administration".

4. Log on to the machine where the license manager is installed (license host).

5. Launch the license manager:

   $SYBASE/$SYBASE_SYSAM/bin/lmgr

6. Click Yes when prompted: "Do you have Sybase Software Asset Management Certificates to register?" The SySAM License Manager screen prompts you for:

   • Order Number

   • Feature Name

   • Feature Count

   • Software Version

   • Authorization Code

7. Click More until you have entered all licenses.

8. Click Done.

   The new license is appended to the end of the license.dat file.

   If you encounter problems with new licenses, check the lmgrd.log file in the $SYBASE/$SYBASE_SYSAM/log directory to see that there were properly appended to the license file.