Overview: Configuring Your Run-time Environment

The run-time environment includes the MCS server, the run-time server, and the client computers. These three areas may be one server (if you are serving your client application from an application server, this counts as the "client"), or you may have separate servers and you may be running your client applications on separate client computers.

Note The client application is the application or Web service that is calling your task. It can be deployed and run on client computers, or served from an application server or Web server.

In most cases, regardless of your network configuration, to correctly configure the run-time environment, you need to take the following steps. In some prototype environments, some of this configuration is handled automatically by MCS.

  1. Add your run-time server or servers in MCS and create session pools to provide host access for your task.

  2. Associate your tasks with with an agent cluster of client computers, and with one or more registered run-time servers, to configure task failover and optional load balancing.

  3. Ensure that your client application has access to the correct JAR files by running it on either a computer where you've installed Runtime Service for Screens or where you've run one of the client installers.

  4. Ensure that the classpath is set correctly on both the run-time servers and the computer on which the client application is running.

Related Topics
Bullet Synapta Services Builder, Overview
Bullet Adding Run-time Servers in MCS
Bullet Creating Session Pools, Overview
Bullet Associating Tasks with Run-time Servers, Overview
Bullet Task Failover and Load Balancing
Bullet Configuring the Client Environment
  Attachmate