Configuring Integration Server to Connect to an SSL-Enabled Port on Universal Messaging

Running Business Processes and Composite Applications : webMethods Integration Server Administrator’s Guide : Configuring Integration Server for webMethods Messaging : Configuring Integration Server to Connect to an SSL-Enabled Port on Universal Messaging

Configuring a Universal Messaging Connection Alias for One-Way SSL

Configuring a Universal Messaging Connection Alias for Two-Way SSL

If Integration Server uses the Universal Messaging connection alias to connect to a secure socket protocol port on the Universal Messaging server, you must configure the alias to use SSL. You specify truststore and possibly keystore information in the alias. This allows communication between Integration Server and Universal Messaging to be secured through secure socket layers (SSL).

A Universal Messaging port uses SSL if the port specifies an interface protocol of NSPS or NHPS. Depending on how the Universal Messaging port is configured, you need to configure one-way SSL or two-way SSL.

In one-way SSL, the Integration Server acting as the client, connects to a Universal Messaging port, supplies the CA certificate used by the Universal Messaging port, but does not supply a client certificate.

Configure one-way SSL if the Universal Messaging port specifies NSPS or NHPS and the Enable Client Cert Validation option is not selected for the port.

For more information, see Configuring a Universal Messaging Connection Alias for One-Way SSL

In two-way SSL, the Integration Server acting as the client, connects to a Universal Messaging port, provides a client certificate, and supplies the CA certificate used by the Universal Messaging port.

Configure two-way SSL if the Universal Messaging port specifies NSPS or NHPS and the Enable Client Cert Validation option is selected for the port.

For more information, see Configuring a Universal Messaging Connection Alias for Two-Way SSL.

Note:

Use Universal Messaging Enterprise Manager to view the protocol and Enable Client Cert Validation option selected for the port.

Note:

When using Integration Server versions 9.8 and 9.9, for Integration Server to connect to an SSL-enabled port on Universal Messaging, you needed to set javax.net.ssl* system properties in the JVM used with Integration Server. As of Integration Server version 9.10, you configure the information needed to establish an SSL connection in the Universal Messaging connection alias. Specifically, you provide the truststore alias and possibly keystore alias and key alias in the connection alias. This allows the use of different truststores and keystores for each connection alias.

Contact Support | Community | Feedback