Sybase 15 manual License usage and enforcement, Managing licenses from multiple vendors

Page 22

Sybase Software Asset Management

3Shut down the earlier individual license servers on each machine and point the software to the new license server. Use the lmpath utility (see “Using SySAM utilities” on page 55) to do this, or edit the license.dat file on each installation by adding these lines at the beginning of the file:

SERVER <network license server hostname> ANY <license server port>

VENDOR SYBASE USE_SERVER

Case 3 If you are not using the network license server for Replication Server version 15.0, no changes are required to the previous software. When fulfilling Replication Server version 15.0 licenses, select the unserved license model and copy the license locally on each installation. The software runs appropriately, however, you lose the asset management functionality in this approach. See “Choosing the appropriate license server configuration” on page 21 for the pros and cons of using a network license server versus using a local license file.

Managing licenses from multiple vendors

If you use software from multiple vendors that use Macrovision’s FLEXnet technology, you can consolidate licenses from all vendors to centrally manage the licenses. See Chapter 3, “Managing Licenses from Multiple Vendors,” in the FLEXnet Licensing End User Guide.”

License usage and enforcement

This section describes the licenses used by Replication Server and other enforcement mechanisms.

License Features Used – when Replication Server starts, it first checks out a license for the base Replication Server, which is REP_SERVER.

Number of licenses used – the number of licenses used for Replication Server depends on the license type under which Replication Server was licensed.

For Replication Server licensed under any of the Server license types such as SR, SV, and so on, one license is checked out per Replication Server. Starting additional Replication Server instances on the same machine does not check out additional licenses.

For Replication Server licensed under any of the CPU license types such as CP,

SF, and so on, the number of licenses used is the number of physical CPUs.

10

Replication Server

Image 22
Contents Replication Server Document ID DC32237-01-1500-03 Contents Contents About This Book Replication Server About This Book Finding the latest information on component certificationsViii Replication definitions, and subscriptions, are in italics One item in square brackets choose it or omit it Your area Xii Introduction Replication Server componentsSybase Software Asset Management Installation task overviewSybase Software Asset Management How SySAM works Using an unserved licenseBefore You Begin Using a network license server Setting up an unserved configurationSetting up a network license server LimitationsUsing multiple network license servers Setting up multiple network serversUsing three-server redundancy Setting up three-server redundancyUsing alternative license file locations Co-existing with earlier versions of SySAMUsing a central license server only for new licenses License usage and enforcement Managing licenses from multiple vendorsLicense availability and grace periods If a SySAM license cannot be acquired Acquiring SySAM licenses during the grace periodPre-installation tasks Read the release bulletinReview system requirements Pre-installation tasksPlan your replication system Review operating system patch requirementsIncrease operating system threads Understand the installation directory structure Configure the operating system for asynchronous I/OBefore You Begin Review the Sybase installation directory contents Set the required environment variable for dsedit utility Perform administrative tasks Creating the sybase user accountSySAM pre-installation tasks Choosing the appropriate license server configurationInstalling a new license server IBM AIXLaunch the Sybase installer program by entering $SYBASE/$SYBASESYSAM/bin b Enter A P T E R 2 Installing Replication Server Using InstallShield for installationUsing InstallShield for installation Installing Replication Server Installing Replication ServerLog out as root Log in as sybase HP-UX Installing Replication Server SySAM License Server window opens and displays this prompt Click Finish. The InstallShield wizard closes Installing in command line mode Installing with a response file Installing in console mode with a response file Installing in silent modeTroubleshooting installation Checking for a valid installationUninstalling Sybase products Uninstalling Sybase products A P T E R 3 Post-Installation Tasks Review the log filesStart the sample Replication Server Start Adaptive Server for the RssdStart Adaptive Server for the Rssd Post-Installation Tasks Set environment variablesSet environment variables Describes the environment variablesP E N D I X a SySAM Administration Managing licensesManaging licenses Using the options file to manage licenses Appendix a SySAM AdministrationStarting and stopping network license servers Starting and stopping network license serversHP-UX Borrowing a license to work offline Borrowing a license to work offlineConnect to the network Shut down Replication Server Enabling the network license server Reportlog file Using SAMreportEnabling the network license server Reportlog file SAMreport system requirements Installing SAMreport Installing the Java Runtime EnvironmentUsing SAMreport Samreport-36-hp700u11.bin -isjavahome JRE directory Post-installation tasks for SAMreport Starting and Stopping SAMreportUsing SySAM utilities Managing and collecting logsUsing SySAM utilities Index Index $SCROOT $SYBROOT $SYBASESYSAM $SYBASEUALog.txt file SYBASE.csh file Vpd.properties file Index