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.
|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 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).
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.
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.
|Enabling Client Access to Run-time Servers|
|Server Configuration Files|
|Associating Tasks with Run-time Servers|