Sybase 15 manual License availability and grace periods

Page 23

CHAPTER 1 Before You Begin

Some Windows and Linux machines use technologies such as “Hyper Threading” which presents one physical CPU as two logical CPUs. This is still considered one CPU for counting licenses.

License availability and grace periods

If Replication Server cannot obtain a suitable license, the product does not run. A license is considered unavailable if it cannot be checked out, or if the license cannot be issued during a grace period. Licenses can be unavailable during start-up or heartbeat runtime.

When SySAM detects a checkout failure, the event is logged in the Replication Server error log, which you can use to diagnose any unexpected licensing failures. After the initial checkout failure, periodic events are logged during a grace period.

If a suitable license cannot be found when requested, Replication Server evaluates if a license can be issued during a grace period. There are three types of grace periods:

Install time – when you configure a new Replication Server (or upgrade an earlier version to 15.0), you have 30 days to activate and configure the appropriate license.

Runtime – a runtime grace period is evaluated when one of these conditions occurs:

A license was not checked out at start-up, but there is a history of successfully using the requested license on this machine.

A license that was successfully checked out at start-up becomes unavailable at a later time.

If Replication Server encounters either situation, it enters into a 30-day runtime grace period. If the problem is not resolved within 30 days, Replication Server stops running; however, the user can save any work and exit. If the problem that causes the license to be unavailable is fixed during the runtime grace period, Replication Server automatically picks up the license and no longer operates in the grace period.

Support renewal time – this grace period allows you enough time to update the license after renewing support. The support grace period for Replication Server is one year.

This means that you can install and use EBFs and updates that are released up to one year past the end-of-support date recorded in the license.

Installation Guide for UNIX

11

Image 23
Contents Replication Server Document ID DC32237-01-1500-03 Contents Contents About This Book Replication Server Finding the latest information on component certifications About This BookViii Replication definitions, and subscriptions, are in italics One item in square brackets choose it or omit it Your area Xii Replication Server components IntroductionSybase Software Asset Management Installation task overviewSybase Software Asset Management Before You Begin Using an unserved licenseHow SySAM works Setting up an unserved configuration Using a network license serverLimitations Setting up a network license serverSetting up multiple network servers Using multiple network license serversSetting up three-server redundancy Using three-server redundancyCo-existing with earlier versions of SySAM Using alternative license file locationsUsing a central license server only for new licenses Managing licenses from multiple vendors License usage and enforcementLicense availability and grace periods Acquiring SySAM licenses during the grace period If a SySAM license cannot be acquiredRead the release bulletin Pre-installation tasksReview operating system patch requirements Pre-installation tasksPlan your replication system Review system requirementsIncrease operating system threads Configure the operating system for asynchronous I/O Understand the installation directory structureBefore You Begin Review the Sybase installation directory contents Set the required environment variable for dsedit utility Creating the sybase user account Perform administrative tasksChoosing the appropriate license server configuration SySAM pre-installation tasksIBM AIX Installing a new license serverLaunch the Sybase installer program by entering $SYBASE/$SYBASESYSAM/bin b Enter Using InstallShield for installation A P T E R 2 Installing Replication ServerUsing 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 silent mode Installing in console mode with a response fileChecking for a valid installation Troubleshooting installationUninstalling Sybase products Uninstalling Sybase products Review the log files A P T E R 3 Post-Installation TasksStart Adaptive Server for the Rssd Start Adaptive Server for the RssdStart the sample Replication Server Set environment variables Post-Installation TasksDescribes the environment variables Set environment variablesManaging licenses P E N D I X a SySAM AdministrationManaging licenses Appendix a SySAM Administration Using the options file to manage licensesStarting 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 Using SAMreport Installing the Java Runtime EnvironmentInstalling SAMreport Samreport-36-hp700u11.bin -isjavahome JRE directory Starting and Stopping SAMreport Post-installation tasks for SAMreportManaging and collecting logs Using SySAM utilitiesUsing SySAM utilities Index $SCROOT $SYBROOT $SYBASESYSAM $SYBASEUA IndexLog.txt file SYBASE.csh file Vpd.properties file Index