Configure the allowed protocols for JSSE on a per port basis Integration Server now provides the ability to specify the allowed protocols for JSSE on a per port basis.

Out of the box support for Content-Type application/xml. Integration Server content handler named ContentHandler_XML now includes support for the content type application/xml.

Kerberos authentication for outbound service requests. The pub.client:http service now includes Kerberos-related parameters that you can use to acquire a Kerberos ticket for inclusion in the outbound service request.

Java API Classes for working with XMLData in Java services A set of classes in com.wm.data for manipulating XMLData in Java services. For a list of classes, see the Added APIs for the Release 9.10 in section 11.0 Added, Removed, Deprecated, or Changed APIs

Universal Messaging connection alias can now be configured to connect to an SSL-enabled port on a Universal Messaging realm server When configuring a Universal Messaging connection alias, you can specify SSL as the client authentication and provide the truststore and keystore information needed for Integration Server to establish an SSL connection with the Universal Messaging realm server. Previously, to establish a secure connection to the Universal Messaging realm server, you needed to configure the javax.net.ssl properties in the JVM used by Integration Server.

A queue on Universal Messaging can be used as the audit logging queue Integration Server provides the option of using a Universal Messaging queue instead of the internal queue as the audit logging queue on a per logger basis.

Follow the master for webMethods messaging connections to Universal Messaging server Integration Server now uses the Universal Messaging client setting “follow the master” which indicates that the client session always connects to the master realm server. The follow the master behavior takes precedence over the behavior indicated through the use of a comma-separated or semicolon-separated list of realm servers in the Realm URL field for a Universal Messaging connection alias.

EventBus predefined JMS connection alias The EventBus alias is no longer available as a predefined JMS connection alias. That is, new Integration Server installations will not include this predefined JMS connection alias. However, if you migrated to Integration Server version 9.10 or later from an earlier version, then you might still have the EventBus alias.

EventBusJndiProvider predefined JNDI provider alias The EventBusJndiProvider alias is no longer available as a predefined JNDI provider alias. That is, new Integration Server installations will not include this predefined JNDI provider alias. However, if you migrated to Integration Server version 9.10 or later from an earlier version, then you might still have the EventBusJndiProvider alias.

WmTomcat Package Existing web applications based on the WmTomcat package can be moved to webMethods Application Platform.

Client queue window size The Universal Messaging window size for the client queue that corresponds to webMethods messaging trigger is now set to the sum of the Capacity and Max execution threads trigger properties. Previously, Universal Messaging determined the window size.

Filters in a webMethods messaging trigger must be identical if the conditions subscribe to the same publishable document type. If more than one condition in the webMethods messaging trigger specifies the same publishable document type and the trigger receives messages from Universal Messaging, the provider filters must be identical in each condition but the local filters can be different. Specifically, the contents of the Provider Filter (UM) column must be identical for each condition that subscribes to the publishable document type. The contents of the Filter column can be different.

Integration Server Administrator The HTML-based utility used to administer the webMethods Integration Server has a new look and feel. Menu and screen locations have not changed.

Internal Server ports that use the HTTPS protocol can now be configured using the “Use JSSE” option. Internal Server ports that support TLS 1.1 or TLS 1.2 protocol can now be configured using the “Use JSSE” option in the Edit Internal Server Configuration screen of Integration Server Administrator. Previously, this option was not available.

OAuth Errors now returned in the content type specified in the client request Previously, Integration Server always returned OAuth errors as HTML. Now, Integration Server returns OAuth errors in the content type specified in the client request.

Reply messages for webMethods messaging routed through Universal Messaging. Integration Server now always encodes reply message as IData even when the encoding type of the reply document type is protocol buffers.