CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

9.2 Configuration
The directory /opt/ctg/bin contains the following files, all of which can be browsed
using the command more:
CTGSAMP.INI Sample CTG.INI configuration file.
ctgcfg Shell script to start CICS TG X-Windows graphical
Configuration Tool.
ctgstart Shell script to start the Gateway daemon.
ctgikey Shell script to start the SSLight tool iKeyman.
220 CICS Transaction Gateway V5
The other files in the directory are executables and cannot be viewed.
The /opt/ctg/classes directory contains the following Java class libraries of note:
ctgclient.jar CICS TG Java class library.
ctgserver.jar CICS TG classes for use by Gateway daemon.
ctgsamples.jar CICS TG Java samples library.
The contents of these can be listed with the command jar -tvf . The
ctgsamples.jar file contains compiled versions of all the non-J2EE samples. We
found this useful for testing because we could execute the samples easily using
just this JAR file and the CICS TG Java class library JAR contained in
ctgclient.jar.
In this section, we detail how we configured the software components on
Windows 2000, Linux, and z/OS for this scenario.
To listen for requests, we needed to enable the TCP protocol handler. We did this
using the Configuration Tool. To run the Configuration Tool on Linux, we ran an
X-Windows server on our Windows 2000 workstation, and specified the address
of the X-Windows server in the DISPLAY environment variable on Linux. The IP
address of our Windows 2000 machine was 9.1.39.10 in this case. We then ran
the Configuration Tool, as shown in Example 9-9.
Example 9-9 Setting Linux to use the Windows 2000 X-Server for the Configuration Tool
root@vmlinux1:/opt/ctg/bin > export DISPLAY=9.1.39.10:0
root@vmlinux1:/opt/ctg/bin > ctgcfg
Tip: The Configuration Tool can also be used on Windows to create the
configuration file. This is detailed in “Using Windows to configure the CICS TG
on Linux” on page 222.