Run multiple instances of SharePlex from separate installations
Important! This topic assumes that there is no active configuration. It assumes you are configuring multiple instances of sp_cop as part of an initial setup of the replication environment.
This method provides a one-to-one relationship between the binaries and the variable-data directory. This procedure creates autonomous SharePlex instances, with nothing in common between them. You start, control and maintain each SharePlex instance separately, and there are no special setup requirements.
This method has the following benefits:
The disadvantages are:
- You must install and upgrade each installation separately.
- More disk space is required to store the product files.
- In startup and shutdown scripts, and other places where you must map environment variables to SharePlex components, you must map them for each installation.
To set up multiple instances of SharePlex in this configuration:
- Install each one separately. There should be one product directory and one variable-data directory per installation.
- Install each one on a different TCP/IP port number.
- Important! Make certain to create a different database account for each installation.
To install SharePlex, see the SharePlex Installation Guide.
Run multiple instances of SharePlex from one installation
Important! This topic assumes that there is no active configuration. It assumes you are configuring multiple instances of sp_cop as part of an initial setup of the replication environment.
This method provides a one-to-many relationship between a set of binaries and two or more variable-data directories. In this configuration, you create multiple variable-data directories and link each one to a unique port number, each running a separate instance of sp_cop. This method has the following benefits:
- You install and upgrade only one installation of SharePlex. Maintenance procedures are performed for only one installation.
- You conserve disk space, because you only store one set of SharePlex binaries and installed files.
- The customization of the SharePlex monitoring scripts only need to be done once, in one place.
- Startup and shutdown scripts only need to be created and run for one set of binaries.
The disadvantages are:
- Processes must be directed to each instance. You must set environment variables for each instance, start sp_cop with the correct identifier for each instance, and set a port connection in sp_ctrl to ensure that commands are directed to the correct instance.
- Upgrades apply to all instances of SharePlex.
- All sp_cop instances are the same version of SharePlex.
How to run multiple sp_cop instances
To run multiple instances of SharePlex on the same Windows machine, you install and run a SharePlex service for each instance, each with a different port number and variable-data directory.
1. Install the instances
- Install SharePlex on the source and target systems according to the directions in the SharePlex Installation Guide. This creates your initial instance of SharePlex.
-
Repeat the installation procedure for each SharePlex instance that you want to create, with the following differences:
- Use the same product directory for each instance.
- Select or create a different variable-data directory for each instance.
- Select a different port number for each instance. The installation program locates available ports, which you can override if necessary.
- When prompted for a license key, use the same license key for all instances. Make certain to select the correct port each time.
- When you run the Database Setup utility, use the correct port number for the instance, and use a different name for each database account.
2. Start the SharePlex instances
All instances are controlled from the SpUtils utility.
- Log onto Windows as a SharePlex Administrator (member of the spadmin group).
- Run the SpUtils utility.
- Select the SharePlex Services tab.
- Select the port number for the instance of SharePlex that you want to start.
- Under SharePlex Service Status, click Start. This starts the service for that instance.
- When the Current State text box shows that the service has started, you can start another instance of SharePlex.
- Run Sp_Ctrl for the instance.
-
In Sp_Ctrl, use the port command to set the session to the port number of the sp_cop instance you want the commands to affect.
sp_ctrl > port number
Execute commands in sp_ctrl
Execute commands in sp_ctrl
This chapter contains instructions for using the sp_ctrl command interface to execute commands that configure, control, and monitor SharePlex. The sp_ctrl program resides in the bin sub-directory of the SharePlex product directory.
Note: See the SharePlex Reference Guide for more information about the commands shown in this topic.
Contents
How to run sp_ctrl
You can run sp_ctrl on any machine where SharePlex is installed. The sp_cop program must be running in order to run sp_ctrl; otherwise it displays an error message similar to this:
Your tcp port is not set properly or “sp_cop” is not running.
Start sp_ctrl
There are two ways to run sp_ctrl:
-
from the command shell of the operating system to issue one command, for example:
$ /productdir/bin/sp_ctrl command [on host]
-
by running the sp_ctrl command interface to issue one or more commands, for example:
$ /productdir/bin/sp_ctrl
sp_ctrl>command [on host]
where:
- productdir is the SharePlex product (installation) directory.
- command is the SharePlex command.
- on host represents one of the command options that allow you to issue a command on the local machine to control SharePlex on a remote machine (if supported by the command), as shown in the following example.
$ /productdir/bin/sp_ctrlstatus on host:port
On Windows systems, you can run sp_ctrl from the Sp_Ctrl desktop shortcut or Windows Programs menu.
The sp_ctrl command line allows a total of 256 characters, including spaces.
sp_ctrl prompt
The sp_ctrl prompt appears in one of two ways, depending on whether or not you set a default host and port number.
| sp_ctrl> |
Basic sp_ctrl prompt |
| sp_ctrl(this_host:3304) > |
Prompt when a default system and port are set by issuing the host and port commands |
Exit sp_ctrl
To exit the sp_ctrl command-line interface, issue the exit or quit command.
On Windows systems, you can simply close the sp_ctrl command prompt window.
The exit or quit command only closes the sp_ctrl session. It does not stop the SharePlex replication processes.
