Caché Instances
Caché Instances
There are many ways to connect to a Caché instance. Two of the most common are through the Caché Launcher (only on Windows platforms) and from the command line of the console.
Each Caché instance installed on a Windows machine has its own launcher. All of the launcher utility functions operate within the context of the instance associated with that launcher.
As you install each instance of Caché, you give it an instance name. To perform command-line procedures on a particular instance of Caché, use this name. You can start, stop, and maintain each of these instances independently. The following table shows the most common commands to manipulate Caché instances.
| Action desired | Caché command |
|---|---|
| Starting a Caché instance |
ccontrol start instname |
| Connecting to a Caché instance |
csession instname |
| Stopping a Caché instance |
ccontrol stop instname |
These commands are described in detail in Connecting to a Caché Instance (csession) and Controlling Caché Instances (ccontrol).
From the Caché Launcher, you can also control multiple remote Caché environments. Caché allows you to create and edit all Caché data on remote systems. This includes, but is not limited to, running remote backups, editing remote instances, and creating and compiling remote objects and routines. See the chapter “Connecting to Remote Servers” in this guide for more detailed information.
On Windows platforms, you can also start, stop, and restart a Caché instance by using the Windows Services administrative tool to start, stop, and restart the Caché Controller service for the instance. However, you cannot use this method to start an instance configured for startup with interactive encryption key activation (see Configuring Startup with Interactive Key Activation in the “Managed Key Encryption” chapter of the Caché Security Administration Guide) because it does not allow you to enter the required credentials.
On UNIX® platforms, when a Caché instance is stopped, restarted, or forced down, the instance will wait for all processes to detach from shared memory for a maximum of 30 seconds. After 30 seconds, the instance will close. If there are still processes attached to the shared memory after the instance has closed, restarting the instance will fail.
