Setting the Connection Type Name

In earlier releases, all web applications that make use of the MultiWorkerTcp subsystem were hard‑coded to use the "JadeHttpToClient" connection name. This was appropriate when all web applications sat in behind IIS, but this is not as useful for web service applications (that is, Direct REST and Direct SOAP web service applications) that connect directly to incoming HTTPS traffic.

The [WebOptions] section of the Jade initialization file provides the ConnectionTypeName parameter that specifies the name of the connection type, to control the SSL configurations used by web-based applications. This parameter enables application‑specific configuration of secure communications.

The JadeMultiWorkerTcpTransport class provides the setConnectionTypeName method that allows users to control which Secure Sockets Layer (SSL) configuration is applied to the web-based application using the JadeMultiWorkerTcpTransport class.

If the ConnectionTypeName parameter does not have a specified connection type name, the value of the JadeMultiWorkerTcpTransport class setConnectionTypeName method defaults to JadeHttpToClient.

The following parameter and value example specifies the connection type name for all web-based applications on the node.

ConnectionTypeName=Milly

However, you can specify the setting in the format <application-name>_ConnectionTypeName to affect only a specific application; for example, to apply the connection type name to a REST application called RestServer, specify the following.

RestServer_ConnectionTypeName=Molly

The connection type names specified in the [WebOptions] section of the Jade initialization file could be as follows.

[WebOptions]
ConnectionTypeName=Milly
RestServer_ConnectionTypeName=Molly
AnotherApp_ConnectionTypeName=Mandy

2022.0.05 and higher