Caché System Administration Guide - InterSystems Documentation

More documents

Recommendations

Info

Using Multiple Instances of Caché The special considerations for multiple instances are: • Each instance must be version 4.0 or later of Caché. For example, Caché 5.1 and 3.2.1 cannot run on the same machine at the same time. • Multiple instances can share the same multiserver key, but if they do, they must use the same license server or set of license servers. Each system running an instance of Caché under the auspices of one or more license servers must have a local copy of the authorizing license key file installed in every instance. • Multiple instances can be networked. • Protection is included against simultaneous database use (that is, each instance must have its own databases and cannot access or modify another instance’s databases). • Only one instance per NIC (network interface card) can use DDP (Distributed Data Protocol) or DCP (Distributed Cache Protocol) over Ethernet. DDP and DCP are older distributed data protocols that are supported for interoperation with legacy applications. If a machine has more than one NIC, each instance must point to a unique NIC. This restriction does not apply to DCP over UDP (User Datagram Protocol). • Each instance must have unique port numbers. See the next section for information on how to Set Port Numbers. Note: Please see the Multiple Caché Installation Issues section of the Caché Installation Guide for important facts when installing multiple instances of Caché on the Windows platform. 9.4.1 Set Port Numbers For a standard, single instance of Caché, the SuperServer port number is 1972 by default. For multiple instances of Caché 4.0 and later on a single machine, each must have a unique port number. During installation, subsequent instances are assigned the next available port if you choose to set it automatically, or you can manually enter port numbers during the installation. A standard installation sets the following port numbers for your Caché instance as follows: • SuperServer port number — 1972 or the first available subsequent number equal to or higher than 56773 • Web server port number — 57772 or the first available subsequent number • Telnet port number — 23 You most likely do not need to change the SuperServer or Web server port numbers because of the way the Caché installation assigns them. However, you do need to assign each instance a unique Telnet port number. You can change the SuperServer port value after installation from the [Home] > [Configuration] > [Memory and Startup] page of the System Management Portal, and you can change the Web server and Telnet port values after installation from the [Home] > [Configuration] > [Startup Settings] 96 Caché System Administration Guide
Configuring Multiple Caché Instances and [Home] > [Configuration] > [Device Settings] > [Telnet Settings] pages, respectively, of the System Management Portal. Note: If you frequently use and manage multiple instances of Caché on one machine, verify that each is assigned unique port numbers. The assignment of unique port numbers avoids confusion when using the Caché Cube tools on multiple instances from one Windows client. Caché System Administration Guide 97
Page 1 and 2:
Caché System Administration Guide
Page 3 and 4:
Table of Contents About This Book .
Page 5 and 6:
6.3 Managing Caché ...............
Page 7:
List of Tables System Administratio
Page 11 and 12:
1 Using the System Management Porta
Page 13 and 14:
Starting the Portal Only Unauthenti
Page 15 and 16:
Navigation Bar Throughout the Syste
Page 17 and 18:
Portal Functions Overview Menu Item
Page 19 and 20:
2 Configuring Caché A Caché confi
Page 21 and 22:
Configuring Data Menu Item NLS Sett
Page 23 and 24:
Configuring Namespaces 2.2.1 Create
Page 25 and 26:
Configuring Namespaces (1) ("A") (1
Page 27 and 28:
Configuring Namespaces a. Click New
Page 29 and 30:
a platform whose Endianness is diff
Page 31 and 32:
Configuring Databases • Read Only
Page 33 and 34:
Configuring System Information •
Page 35 and 36:
Configuring Task Manager Email Sett
Page 37 and 38:
Configuring NLS Settings • Using
Page 39 and 40:
Configuring NLS Settings 2.6.1.2 Im
Page 41 and 42:
Cluster Settings • Config.NLS.Tab
Page 43 and 44:
3 Managing Caché This chapter expl
Page 45 and 46:
Maintaining Local Databases 3.1.1.1
Page 47 and 48:
Maintaining Local Databases c:\MyCa
Page 49 and 50:
3.2 Controlling Caché Processes Co
Page 51 and 52:
Controlling Caché Processes Proces
Page 53 and 54: Controlling Caché Processes 3.2.2
Page 55 and 56: 2. Click Details in the row of the
Page 57 and 58: Using the Task Manager • Descript
Page 59 and 60: Using the Task Manager 3.3.4 View T
Page 61 and 62: 4 Managing Caché Licensing This ch
Page 63 and 64: in alphabetic format (mycomputer.my
Page 65 and 66: You can also check the license erro
Page 67 and 68: 4.3.2 Methods to Show License Serve
Page 69 and 70: Identifying Users • Username Lice
Page 71: Identifying Users is considered a
Page 74 and 75: Using Caché on Windows When you cl
Page 76 and 77: Using Caché on Windows To start Ca
Page 78 and 79: Using Caché on Windows Command css
Page 80 and 81: Using Caché on UNIX, Linux, and Ma
Page 90 and 91: Using Caché on OpenVMS where instn
Page 92 and 93: Using Caché on OpenVMS 4. Click Se
Page 94 and 95: Connecting to Remote Servers When c
Page 96 and 97: Connecting to Remote Servers CSP Se
Page 99 and 100: 9 Using Multiple Instances of Cach
Page 101 and 102: Controlling Caché Instances 9.3 Co
Page 103: Configuring Multiple Caché Instanc
Page 108 and 109: Achieving High Availability Caché
Page 110 and 111: Achieving High Availability 10.4.1
Page 112 and 113: Achieving High Availability logical
show all

Caché System Administration Guide - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?