Configuring Your Run-time Environment

The run-time environment includes the MCS server, the run-time server, and the client computers. These three components can be configured on one server (if you are serving your client applications from an application server, this is considered the "client"), or you can have separate servers, and run your client application 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.

Workflow

In most cases, regardless of your network configuration, to configure the run-time environment correctly, you need to take the following steps (although in various prototype environments, MCS automatically configures some of these settings).

  1. Add your run-time server or servers in MCS and make the necessary configurations to provide host access for your task.

  2. Associate your tasks 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 a computer either where you've installed Runtime Service for CICS or where, while installing, you ran the Client Support option.

    The necessary client support files are also available from the root of the CD. Open the clientinst directory and run setup.exe on the client computer.

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

The Services Builder for CICS run-time supports both TCP/IP and SNA host connections, and requires minimal configuration. Configuration includes defining a connection (referred to as a "System"), and then mapping Task IDs to Systems (referred to as "Mappings"), which enables tasks to be run.

Both Systems and Mappings are configured using the Management Console, under the Configuration node of each run-time server.

Related Topics
Bullet Enabling Client Access to Run-time Servers
Bullet Server Configuration Files
Bullet Associating Tasks with Run-time Servers
  Attachmate