Attachmate Verastream Transaction Integrator Guide

 

Provide Client Access to the Runtime Server

If you plan to run your applications from the same server where the CICSServer or IMSServer is installed, then, after you set the Java classpath, no other configuration is needed. If, however, you are going to run your applications on different computers, then you need to install the client support files for your environment on all the computers you will use.

Before you begin:

Install the CICSClient or IMSClient from the install program, depending on your host program, on each of the computers where you have the runtime server installed.

Basic configuration steps

There are three separate steps involved in providing client access to the runtime server:
  1. Editing your Java classpath
  2. Modifying the client configuration file
  3. Configuring logging and tracing (Optional)

1. Editing your Java classpath

To edit your Java classpath
Add the following client support files to your Java classpath:

In the directory …\Attachmate\Verastream\TransactionIntegrator\<host type>Client:

  • CICSClient.jar
  • xerces.jar
  • common.jar
  • MetaData.jar
  • util.jar

In the directory …\Attachmate\Verastream\TransactionIntegrator\Common\mcs:

  • mcsagent.jar
  • mcs-rpc.jar

2. Modifying the client configuration file

Client access to the runtime servers is handled through the <host type>ClientConfig.xml file, which is created automatically the first time a client operation is run on a remote or client system.

The <host type>ClientConfig.xml file is located in the cfg directory, either in the location you specified as a “System” property (Attachmate.home) or in the Java-provided location, user.home. On a Windows system, this is Documents and Settings\user_login\cfg.

Where:
  • serverAddress specifies the location of the runtime server (default=“localhost”).
  • The default RMI port number for the CICS server is 6800; for the IMS server, 6900. To change the port number, add the port number after the server address as follows, where xxxx is the port number:

    <Property Name> = “serverAddress” Value = “localhost:xxxx”/>

    The value you specify muct match the value found in CICSServer\cics_runtime.properties or IMSServer\ims_runtime.properties.

  • The protocol is TCP/IP.

Specifying the location of a remote server

To specify a remote runtime server to serve applications from the processing runtime server

Open the <host_type>ClientConfig.xml in a text editor and modify as follows:

<Property Name = “serverAddress” Value = “<DNS Name> or <IPAddress>”

Specifying a custom directory for the client configuration file

To specify a custom directory for the client configuration file:
Set the System property "Attachmate.home" on the command line that starts the Java Virtual Machine that is running your interface objects as follows: 
-Dattachmate.home=<c:\mydirectory>

Where:

<mydirectory>= the name of the directory you are specifying

How you pass command line arguments to the Java VM depends on your environment. The Java VM can be part of a Web server for Servlets and JSPs, in a browser for a Java Applet, or a stand-alone process if your interface objects are running as part of a Java application.

Set the System property programmatically from within your application as follows:

System.setProperty(“attachmate.home”,<myDirectory>);

Your application must make the call before you run interface objects, and it must have the necessary permission to modify system properties.

3. Configuring Logging and Tracing

 

As an optional feature, you can set up logging and tracing, both on the server and the client-side.

Related Topics
Bullet Setting Up the Runtime Environment
Bullet Provide Host Access to Client Operations
Bullet Capturing Host Data
  Attachmate