WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Securing the connection to CICS Transaction Server for z/OS by using SSL
Configure the CICSRequest node to communicate with CICS® Transaction Server for z/OS® over the Secure Sockets Layer (SSL) protocol by updating a CICSConnection configurable service or the CICSRequest node to use SSL.
Before you start:
Ensure that
you have completed the following tasks:
- The CICSRequest node does not support a separate truststore, so the keystore file must provide both personal and signer certificates. If client-authentication (CLIENTAUTH) is enabled in the TCPIPSERVICE in CICS, the broker keystore file must also contain a personal certificate that is trusted by CICS. To set up a public key infrastructure (PKI) at broker or execution group level, follow the instructions in Setting up a public key infrastructure.
- Define the COMMAREA data structure as a message set, as described in Defining a CICS Transaction Server for z/OS data structure.
- Configure IP InterCommunications (IPIC) protocol on CICS, as described in Preparing the environment for the CICSRequest node.
To configure the CICSRequest node to use SSL, complete the following steps:
Next: When you have configured
the broker or the CICSRequest node
to use SSL, develop a message flow that contains a CICSRequest node by following
the steps in Developing a message flow with a CICSRequest node.