Replicating Runtime Servers

In Solaris environments, after installing and configuring the Runtime Service, you can replicate the installed runtime so that you can run multiple instances on a single computer. This is known as runtime stacking. Runtime stacking can be useful in an environment where different user groups need to run separate instances of the runtime on the same server.

Pool configuration is done on the original installation, and pools are shared among the deployed runtimes. Because each deployed instance runs completely independently, there are several options to consider for avoiding login conflicts between sessions. You can:

To replicate a Runtime Service
  1. Using the regular installation procedure, install the Runtime Service.

    For information about installing the Runtime Service in a Solaris environment, see Installing in UNIX.

  2. In MCS, add the new Runtime Service, and configure session pools and logging options. For information, see Configuring Your Runtime Environment, Overview.

  3. Verify that the installed runtime is operating as expected.

  4. Change to the install directory/Attachmate/EAI/ScreenConnectors/replication directory, run the script archive.sh, and respond to the prompts. To use the default values supplied, press ENTER.

    Running this script configures the runtime for deployment and creates a tar ball.

    Note Each Runtime Service must listen on a unique RMI port. Although you will specify an RMI port during replication, you must change this value each time you deploy an instance of the service on the same computer.

    For a description of the prompts that are displayed, see Replication and Deployment Prompts.

To deploy the replicated Runtime Service
  1. To start the deployment script, type:

    ./deploy.sh

  2. Respond to the subsequent prompts, which are similar to the prompts displayed by the replication script.

    To use the default values supplied, press ENTER.

  3. When asked if you would like to configure this runtime, respond Yes, unless you plan to deploy the runtime only once on a given computer.

  4. Assign a unique RMI port to use for this instance of the runtime service.

  5. Assign a unique Runtime ID Name so that you can filter events based on the runtime that generated them when viewing logged events in MCS.

  6. Repeat the deployment process for each instance of the Runtime Service that you want to run on this computer.

Note If you copy the archive created by the replication process and the install directory/Attachmate/EAI/ScreenConnectors/replication/deploy.sh file to a different computer, you can run the deployment script on multiple systems. When deploying on a different computer, ensure that the MCS service agent is also installed. If necessary, you can manually install the service agent. For installation instructions, see Installing the MCS Service Agent.
Related Topics
Bullet Installation, Overview
Bullet Installing in UNIX
Bullet Configuring Your Run-time Environment, Overview
Bullet Replication and Deployment Prompts
Bullet Installing the MCS Service Agent
  Attachmate