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 message flows by using SSL configuration
You can secure message flows by configuring nodes within the message flows to use SSL and certificates.
After you establish a public key infrastructure configuration for your whole broker or for some of its execution groups, you can use the configuration within your message flows. For information on establishing a public key infrastructure, see Setting up a public key infrastructure. When you configure message flow nodes that make or accept TCP connections, you can set SSL encryption and certificates on those connections.
For more information about using SSL and certificates to secure
your message flows, see:
- Configuring the broker to use SSL with JMS nodes
- Configuring SOAPInput and SOAPReply nodes to use SSL (HTTPS)
- Configuring SOAPRequest and SOAPAsyncRequest nodes to use SSL (HTTPS)
- Configuring HTTPInput and HTTPReply nodes to use SSL (HTTPS)
- Configuring the HTTPRequest and HTTPAsyncRequest nodes to use SSL (HTTPS)
- Enabling SSL on the WebSphere® MQ Java™ Client
- Securing the connection to CICS® Transaction Server for z/OS® by using SSL
- Securing the connection to IMS™ by using SSL
- SSL and the TCP/IP nodes
- Using security exits