SFTP Host Key Checking field in the SFTP User Alias Advanced Settings screen Allows Integration Server to verify the host key of SFTP server during connection.

Create JMS administered objects on demand. Integration Server can create administered objects in the JNDI namespace automatically when the lookup for the object fails. This functionality, which is controlled by the Create Administered Objects On Demand option for a JMS connection alias, is available only when Universal Messaging is the JMS provider and the JNDI provider.

Support for using volumes when running an Integration Server image in a Docker container. Docker volumes can be used for externalizing the contents of the logs directory for the Integration Server instance and the Integration Server profile as well as the config directory for the Integration Server instance running in the Docker container.

The is_container.sh script, which facilitates interaction with Docker, now provides an option for specifying a base image. When using the createDockerFile or createLeanDockerfile command to create a Docker image for Integration Sever, specify a base image using the argument Dimage.name.

Support for using an Integration Server running in a Docker container as the local development server for the local service development feature in Designer. When using the createDockerFile or createLeanDockerfile command to create a Docker image for Integration Sever, specify that the Integration Server will be used as the local development server using the argument Dtarget.configuration=localdev

New flag, useAlternateNameForSegment, added in the WmFlatFile package. useAlternateNameForSegment: Determines whether the flat file parser uses an alternate name for segments if an alternate name is provided.

Support for RFC 7662, OAuth 2.0 Token Introspection Access tokens generated by an external authorization server can be used to access resources in Integration Server. Access tokens generated by an Integration Server authorization server can be used to access resources in a resource sever that is not an Integration Server.

Support for RFC 7009, OAuth 2.0 Token Revocation Access tokens generated by Integration Server can be revoked.

Support for REST V2 resources Integration Server provides a flexible way of defining resources for REST requests. In the Service Development perspective, a developer can define a REST V2 resource with operations that include the following:

The format of the URL that REST clients must follow when sending requests to Integration Server acting as the REST server.

The HTTP methods supported by the resource operation.

The flow service associated with a resource operation.

Support for JWT authentication Integration Server provides support for JSON Web Token (JWT) authentication. JWT provides a secured means of exchanging claims between two parties.

HTTP Interceptor Integration Server provides a framework for creating and registering an HTTP interceptor. An HTTP interceptor intercepts all received HTTP requests and outbound HTTP responses. Integration Server makes the raw HTTP request and response, including the HTTP header information, accessible to the HTTP interceptor.

Serial JMS triggers supported with Universal Messaging. When using a connection factory configured for a durable subscriber, Integration Server now supports the use of serial JMS triggers with Universal Messaging.

Additional client side queue (CSQ) logging. When facility code 134 is set to debug or trace levels, Integration Server provides additional logging when CSQ errors occur.

Integration Server now supports migration when source and target version are same. The migration utility can now be used for migration where the source and target versions of Integration Server are the same. This can be useful for data center or machine moves

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

Archived stats.log file name format. Integration Server now uses the following naming format for the archived stats.log files: stats.yyymmdd_hhmmss.log where the timestamp indicates the time at which Integration Server archived the log file. Previously, the archived stats.log name did not include the time portion which caused a naming conflict that prevented successful log rotation if Integration Server attempted to rotate the stats.log more than once on the same day.

Manage Destinations check box The Manage Destinations check box for a JMS connection alias is now named Enable Destination Management with Designer.

Share Client Prefix check box The Share Client Prefix check box for webMethods messaging connection aliases is now named Client Prefix Is Shared. The field name now includes the text “prevents removal of shared messaging provider objects” in parentheses to clarify the purpose of the option.