To complete this task you issue a Java command then follow a series of on screen prompts.
The Java™ sample program EciB3 enables you to verify that the SSL connection between CICS® Transaction Gateway and CICS has been correctly configured. You can optionally complete this task before completing the next task Configuring WebSphere Application Server.
java -DCTG_APPLID=SSLAH com.ibm.ctg.samples.eci.EciB3 local: 2006 ctgclientkeyring.jks MyPassword
The following information
is displayed on the screen:CICS Transaction Gateway Basic ECI Sample 3
Usage: java com.ibm.ctg.samples.eci.EciB3 [Gateway URL]
[Gateway Port Number]
[SSL Keyring
SSL Password]
To enable client tracing, run the sample with the following Java option:
-Dgateway.T.trace=on
The address of the Gateway daemon has been set to local: port 2006
IPIC servers are not listed when running in local mode.
Enter URL of a CICS server, or Q to quit:
Program EC03 returned 5 containers in channel "SAMPLECHANNEL":
[CHAR] CICSDATETIME = 19/05/2010 16:29:31
[BIT] INPUTDATALENGTH = 0000000c
[CHAR] OUTPUTMESSAGE = Input data was: my test data
[CHAR] INPUTDATACCSID = 5348
[CHAR] INPUTDATA = my test data
If the sample program returns CICS server not found, this indicates that the SSL connection has not been established. Check the CICS Transaction Server system log for more information, and ensure that the JKS keyring file name and password are correct (the CICS password you entered is not checked because the IPIC connection is configured with Userauth=Identify).
You have now verified the connection.