Caché System Administration Guide - InterSystems Documentation

More documents

Recommendations

Info

Using Multiple Instances of Caché• help — print the help message and exit• restart — start Caché after a successful shutdown (for stop function only and not availableon Microsoft Windows platforms)Any other value is taken as a .cpf configuration file nameYou may have your own procedures that involve using the scripts cstart and cstop, amongothers. Caché can accommodate these procedures. These scripts, in fact, are invoked byccontrol. Invoke the ccontrol help command to obtain the most recent description of theinterface with these scripts.For an example of creating user start and stop procedures, see the Use of the ^%ZSTARTand ^%ZSTOP Caché Routines article.5.4 Configuring Multiple Caché InstancesYou can install and simultaneously run multiple instances of Caché 4.0 and later on a singlemachine. Install Caché as for a single installation, giving each configuration a unique name,a unique installation directory, and a unique port number for the SuperServer, Telnet, andthe License Manager.The special considerations for multiple instances are:• Each instance must be version 4.0 or later of Caché. For example, Caché 5.0 and 3.2.1cannot run on the same machine at the same time.• Multiple instances can share the same multiserver key, but if they do, they must use thesame license manager or set of license managers. Each system running an instance ofCaché under the auspices of one or more license managers must have a local copy of theauthorizing license key file installed in every configuration.• Multiple instances can be networked.• Protection is included against simultaneous database use (that is, each instance must haveits own databases and cannot access or modify another instance's databases).• Only one configuration per NIC (network interface card) can use DDP (Distributed DataProtocol) or DCP (Distributed Cache Protocol) over Ethernet. DDP and DCP are olderdistributed data protocols that are supported for interoperation with legacy applications.If a machine has more than one NIC, each configuration must point to a unique NIC.This restriction does not apply to DCP over UDP (User Datagram Protocol).18 Caché System Administration Guide
Configuring Multiple Caché Instances• Each instance must have unique port numbers. See the next section for information onhow to Set Port Numbers.Note:Please see the Multiple Caché Installation Issues section of the Caché InstallationGuide for important facts when installing multiple instances of Caché.5.4.1 Set Port NumbersFor a standard, single configuration of Caché, the SuperServer port number is 1972 by defaultand is set automatically during installation. Do not change this unless you are running multipleinstances on the same machine.For multiple instances of Caché 4.0 and later on a single machine, each must have a uniqueport number.If an existing instance is running on port number 1972, either change its port number beforeinstalling a new configuration, or stop it, install the new instance, and change the port numberof the new instance before restarting the existing one.To change the port number on a new installation:1. From the Caché Cube of a Windows client, point to Preferred Server and click Add/Editto add a remote server connection to the new Caché configuration. Enter 1972 for thePort of this new installation.2. Point to Remote System Access from the cube, point to Configuration Manager, and thenclick the appropriate connection server name you entered for this configuration.If configuring a local instance, choose LOCALTCP as the preferred server or chooseConfiguration Manager directly from the cube menu.3. On the Advanced tab of the Configuration Manager, expand the section for General settings.4. Change the value for Default Port Number from 1972 to a unique number. A restart ofCaché is required to activate this change.5. After restarting, point to Preferred Server and click Add/Edit to edit the remote serverconnection to the newly installed Caché configuration. Change the port number on theremote server to match the unique port number you assigned this configuration in theprevious step. This ensures that the Caché GUI tools connect to the correct Caché instance.Caché System Administration Guide 19
Page 7 and 8: 1IntroductionThis book is an introd
Page 9 and 10: Release lever3When the travel lever
Page 12 and 13: Using Caché on Windowsaccess the B
Page 15 and 16: 3Using Caché on Linux and UNIXThis
Page 17: Stopping Caché6. If you answer Yes
Page 21 and 22: 5Using Multiple Instances of Caché
Page 23: Controlling Caché Instances5.3 Con
Page 27 and 28: 6Connecting to Remote ServersYou ca
Page 29 and 30: 7Configuring CachéA Caché configu
Page 31 and 32: Caché databases dynamically expand
Page 33 and 34: Configuring Namespaces5. Click Fini
Page 35 and 36: Configuring Namespaces1. From the N
Page 37 and 38: Configuring Namespaces2. Select Glo
Page 39: Configuring License ManagersFrom th
Page 42 and 43: Managing CachéControl Panel Functi
Page 44 and 45: Managing CachéColumn HeadingGlobal
Page 46 and 47: Managing Caché8.1.3 Stopping a Pro
Page 48 and 49: Managing CachéTo broadcast a messa
Page 50 and 51: Managing CachéIn most cases, the o
Page 52 and 53: Managing CachéIf you have any trou
Page 54 and 55: Achieving High Availability9.1 Surv
Page 56 and 57: Achieving High Availability9.2.1 Co
Page 58 and 59: Achieving High Availability3. Resta
Page 60 and 61: Achieving High AvailabilityThe valu
Page 62 and 63: Achieving High Availabilityserve up
Page 64 and 65: Achieving High Availabilityinformat

Caché System Administration Guide - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?