GraphQL support GraphQL is a query language designed to build client applications by providing a flexible syntax and system for describing their data requirements and interactions. Using GraphQL service, you can query a specific data to the server and get the response in a predictable way. Integration Server acts as a GraphQL service provider and supports GraphQL version 9.X.

JSON Schema support Integration Server provides native support for JSON Schema in which a developer can create a JSON document type from a JSON schema and then use the JSON document type to validate a JSOON payload.

Enhanced support for Swagger 2.0 standard while creating REST APIs Integration Server supports Swagger constructs like tags, external docs and basic security definitions while creating APIs using resource first or swagger first approaches. Integration Server supports Swagger files that reference other files.

Support for Universal Messaging horizontal scalability Universal Messaging horizontal scalability feature can be used with webMethods messaging connection alias that connects to Universal Messaging.

Enhancements for Enterprise Gateway Server while communicating with ICAP server for virus scanning or content filtering. Enterprise Gateway supports both REQMOD and RESPMOD methods based on the ICAP server response to the OPTIONS method.

Support for AMQP protocol using QPID JMS client libraries Integration Server is certified to communicate with JMS providers that support AMQP protocol using QPID JMS client libraries. Integration Server supports the "Qpid JMS AMQP 0-x 6.3.3" JMS client libraries.

Lifecycle management settings for sockets. Integration Server now includes server configuration parameters to control how long a socket is kept in the pool (watt.net.clientKeepaliveAgingLimit) and how many times it can be used (watt.net.clientKeepaliveUsageLimit ). If either limit is exceeded, Integration Server will not return a socket to the pool. The new parameters are tuning parameters that will need to be adjusted based on use case and usage patterns.

WmVCS package and VCS Integration feature Use the local service development feature (Local Version Control Integration) to check package elements and their supporting files into and out of a version control system directly from Designer.

Web services implementation introduced in Integration Server 7.1. The current web services stack. Web service descriptors can be changed to work with the web services stack by changing the Pre-8.2 compatibility mode property to false. A bulk change of web service descriptors can be accomplished using the built-in service pub.utils.ws:setCompatibilityModeFalse.

The ability to run in pre-8.2 compatibility mode.

The Pre-8.2 compatibility mode property.

The Integration Server WS-Security facility which provides support for WS-Security by associating built-in WS-Security handlers to web service descriptors.

Any behavior specific to the web services implementation introduced in 7.1.

The Fail-Fast Mode Enabled and Currently In Fail-Fast options do not appear when editing the CentralUsers functional alias. Fail-fast cannot be used with the CentralUsers functional alias definition. Consequently, the Fail-Fast Mode Enabled and Currently In Fail-Fast options do not appear when editing the CentralUsers functional alias.

is_container script contains a parameter for specifying when the default truststore store should be overwritten. The is_container script now includes the Dtarget.configuration parameter which must be set to wmcloud when creating a Docker image for an Integration Server that will be lifted and shifted into Integration Cloud. When this parameter is set to wmcloud, the is_container script overwrites the default truststore with the truststore required by Integration Cloud.

Allow and Deny Lists for ports The port access control feature can now specify service URIs that are not part of the Integration Server namespace. Though any service URI can now be included in port access control, Integration Server only validates and enforces web service URIs as part of this change.

File-based audit logs can use character sequence delimiters. The fields for an entry in a file-based audit log can now be fixed length or character delimited. Using character-delimited entries may reduce the size of the log.

JMSMessageID When sending a JMS message to Universal Messaging, Integration Server sets the JMSMessageID.

Namespace preservation when decoding an xsd:any element Integration Server now preserves all namespace declarations when decoding an xsd:any element. Previously, when decoding a SOAP request or response that includes an xsd:any element, Integration Server preserved only the namespace declarations (xmlns attributes) in the top level element of an xsd:any element. An xsd:any element may have any number of nested elements. Integration Server should not remove he namespace declarations in nested elements.

Resource Owner Password Credentials (ROPC) grant type can be used with public clients. Integration Server now supports use of the ROPC grant type with public clients.