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

210 CICS Transaction Gateway V5
► If the keystore cannot be found by the Java application, the message will state
java.io.FileNotFoundException, will give the file name specified for the
keystore, and will state (The system cannot find the file specified).
Check that the filename specified for the keystore is correct.
CCL6668E: Initial handshake flow failed
This error message appears on the Java client application when the SSL
handshake with the CICS TG fails.
► If the message is [javax.net.ssl.SSLHandshakeException: unknown
certificate], then the signer certificate of the key used in the CICS TG
server is not present in the keystore used by the client Java application. This
happens if you try to use the SSL-only keystore jsseclientsslonly.jks to
connect to the System SSL protocol handler, or if the self-signed CICS TG
certificate is not imported into the client keystore. iKeyman or keytool can be
used to view the certificates present in a keystore.
► If the message states [ERROR_CONNECTION_FAILED], check that the CICS TG
protocol has been specified as ssl:// and not tcp://. Using the TCP
protocol to connect to an SSL protocol handler will generate this error.
► If the message contains [javax.net.ssl.SSLProtocolException: end of
file], check that the application has specified an SSL protocol handler and
not a TCP protocol handler. Trying to connect to a TCP protocol handler using
ssl:// will also result in this error. Also, check that the Gateway daemon
certificate has not expired. Using an expired System SSL certificate will
generate this error on the client application.
iKeyman error message when loading a keystore
When loading a keystore into iKeyman the window in Figure 8-11 might appear.
This can be caused by specifying the wrong password at the password prompt.
The same window is caused when the keystore is corrupt, if it was transferred
using FTP in ASCII mode for example.
Figure 8-11 iKeyman loading error message