![]() | ![]() |
Home |
|
|
Installation Guide Adaptive Server Enterprise for HP-UX |
|
| Chapter 3 Sybase Software Asset Management (SySAM) |
Chapter 3
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 (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.
You must register the Adaptive Server Enterprise license through SySAM before you can enable any of the optional features.
Table 3-1 describes the Adaptive Server features that are licensed through SySAM.
Feature name | License name | Description |
Adaptive Server | ASE_SERVER | The basic Adaptive Server Enterprise product, without optional features. |
High availability | ASE_HA | Adaptive Server failover capabilities for high availability environments. |
Java in Adaptive Server | ASE_JAVA | Java and XML support in Adaptive Server databases. |
Advanced security mechanisms | ASE_ASM | Network-based authentication and encryption using DCE and CyberSafe. |
Distributed transaction management | ASE_DTM | Distributed transaction management support for XA and Microsoft DTC protocols. |
Enterprise JavaBean Server | ASE_EJB | A transaction server provides the framework for creating, deploying, and managing middle-tier business logic in the form of EJBs in a multi-tier environment. |
LDAP directory services | ASE_DIRS | Lightweight directory services. |
Enhanced Full-Text Search | ASE_EFTS | Enhanced full-text search specialty data store. |
External file system | ASE_XFS | Management of non-relational Web content. |
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.
Adaptive Server 12.5 features that are not yet supported with these complimentary products include:
Extended row and column size limits
Lightweight directory services (LDAP)
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.
Figure 3-1: SySAM components
Adaptive Server check-out procedureWhen 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 start 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 high availability (ASE_HA), 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.
Starting Adaptive Server with optional featuresYou can use sp_configure parameters to turn on or off optional features. Table 3-2 lists the parameters used to configure optional features.
Feature name | License name | Configuration parameter |
High availability | ASE_HA | enable HA |
Distributed transaction management | ASE_DTM | enable DTM |
Java in Adaptive Server | ASE_JAVA | enable java |
Advanced security mechanisms | ASE_ASM | use security services enable ssl |
Enterprise JavaBean 32-bit platforms only | ASE_EJB | enable enterprise java beans |
LDAP directory services | ASE_DIRS | n/a |
Enhanced full-text search | ASE_FTS | enable full-text search |
External file system | ASE_XFS | enable file access |
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 Configuring Adaptive Server Enterprise.
For information about configuring Adaptive Server as a companion server in a high availability system, see Using Sybase Failover in a High Availability System.
For information about configuring Adaptive Server with distributed transaction, see Using Adaptive Server Distributed Transaction Management Features.
For information about Java in Adaptive Server, see Java in Adaptive Server Enterprise.
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 backup and load-balancing purposes.
Depending on which instance of Adaptive Server (primary or secondary servers) you are installing, the procedures for registering licenses vary.
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.
Figure 3-2: Standalone system without optional features
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.
Figure 3-3: Network system
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.
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 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.
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.
The installer prompts: "Do you have Sybase Software Asset Management Certificates to register?"
Click No.
The installer prompts: "Have you registered Sybase Software Asset Management Certificates at a central license host?"
Click Yes.
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.
Click OK.
Continue with the installation procedures described in Chapter 4, "Installing Sybase Servers ."
See 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:
Follow the instructions in this guide to install Adaptive Server on each of the servers in the redundant system.
As you install the software, make a 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 during the installation process.
For each machine in the redundant system, when the Studio Installer 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.
Click Continue Install.
Complete the installation of Adaptive Server. See Chapter 4, "Installing Sybase Servers ."
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.
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.
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 before you continue the installation or start Adaptive Server.
If the SySAM software is not running, see "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
This section describes how to update the license file to enable Adaptive Server features.
To add features for which you have licenses:
Enable the new feature. See "Starting Adaptive Server with optional features".
Shut down Adaptive Server. See Chapter 7, "Starting and Stopping Servers."
Verify that the license manager software is running. See "SySAM administration".
Log on to the machine where the license manager is installed (license host).
Launch the license manager:
$SYBASE/$SYBASE_SYSAM/bin/lmgr
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
Click More until you have entered all licenses.
Click Done.
Because you are adding licenses to an existing configuration, you must notify the license daemons of the changes by issuing a reread command.
Run the license management utility lmutil lmreread from the $SYBASE/$SYSAM/bin/directory.
$SYBASE/$SYBASE_SYSAM/bin/lmutil lmreread
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.
|
|