Enabling Client Access to Run-time Servers

If you are building a server-based application to run on the same server where the run-time service is installed, after setting your class path, no additional configuration is necessary.

However, if you plan to run your applications on a computer other than the one on which the run-time service is installed, you need to provide the necessary client support files for your environment on all of the computers you will use. The Client Support option, available from the installation program, installs the tools (the CICSClient and all its support JARs) that your application needs to run its host access tasks.

Note Alternatively, you could use setup.exe, from the root of the CD in the clientinst directory, which also runs the Client Support option.

When you install Services Builder for CICS on a Windows platform, along with other component install options, you can select to install the client support JARs and properties files required for Java clients and the COM interface required for NativeWin32 clients. You are also prompted to install CICS Connector Proxy Service, a Windows service that is required for .NET Web services and other stateless Win32 clients.

When you install Services Builder for CICS in a UNIX environment, you have the same option to install the necessary client support files.

Once the client installation is finished, a CICSClient directory is created as follows, which includes CICSConnectorProxyService.exe, CICSConnector.dll, and the JARs required for the client to run CICS tasks:

install_directory\Attachmate\EAI\CICSClient

Editing your Class Path

In addition to installing the appropriate client support files, you need to make sure that the following files, which are installed by the Client Support install option, are in your class path on the computer on which you will compile your applications, and from which they will be served.

Additional Configuration

Two types of connectivity protocols are available: SNA and TCP/IP. (For installation and system requirement information about the TCP/IP option, see Using the TCP/IP Connectivity Feature.)

For SNA, the modes SNASVCMG and APPCPCLM must be defined in your server configuration XML file. The host CP (control point) LU uses the SNASVCMG mode to negotiate the Number of Sessions for the application; the CPMI program uses the APPCPCLM mode for ECI-type conversation.

Services Builder for CICS works with independent LUs. Therefore, these modes need to be configured for at least 2 sessions.

Related Topics
Bullet Configuring Your Run-time Environment
Bullet Associating Tasks with Run-time Servers
Bullet Starting and Stopping the Runtime Service
Bullet Manually Configuring the Client Environment
  Attachmate