Enhanced messaging logging Integration Server writes detailed log entries when sending or receiving and processing messages. The detailed logging makes it possible to track an individual message across your Integration Servers from the time the message is published through the time a trigger receives, processes, and acknowledges the message. Enhanced logging includes the introduction of the messaging audit log.

WebSocket support Integration Server enables development of applications using the WebSocket protocol. The WebSocket protocol provides simultaneous two-way communication between a client endpoint and server endpoint over a single TCP connection.

Whitelist filtering To prevent Integration Server from deserializing untrusted Java objects, Integration Server now performs whitelist filtering and includes a whitelist of classes that can be loaded and deserialized in Integration Server.

Support for default scope for Integration Server acting as the OAuth resource server When configuring an external authorization server, you can specify a default scope in the Default Scope field.

SSL field on the About page of Integration Server Administrator To help troubleshoot connectivity issues, the About page of Integration Server Administrator, the Software section now contains an SSL field that displays one of the following:

The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it.

The JCE Unlimited Strength Jurisdiction Policy File was found

Support for security response headers To enhance the security of response headers, Integration Server now supports the following HTTP response security headers:

X-Content-Type-Options

X-XSS-Protection

Strict-Transport-Security

Improved support of REST multipart messages Integration Server provides Java API that enables you to register your own services along with the associated coders for multipart content handler.

Support for strong password polices To enhance the security, Integration Server now supports stronger password policies for user accounts. To achieve this, Integration Server now covers the following aspects of password security:

Stronger password requirements

Password expiration requirements

Account locking

Circuit Breaker The circuit breaker feature provides the ability to configure a circuit breaker for any service residing on a Microservices Runtime or an appropriately licensed Integration Server.

Any field type support for Digital Event Services An Object or Object List with a Java wrapper type of UNKNOWN is included in the Digital Event Servers event type definition as an Any or Any field. Previously, an Object or Object List field with an UNKNOWN Java wrapper type were not included in the corresponding Digital Event Services type definition. Additionally, IS document types can be used to define the structure and content for an Any field in a document published to Digital Event Services.

Map field type support for Digital Event Services An empty inline document variable configured to allow unspecified fields in a publishable document type is now represented as Map field in the corresponding Digital Event Services type definition.

Synchronizing document types with Digital Event Services automatically Document types can be set to automatically synchronize with a corresponding Digital Event Services event type definition in the Digital Event Services repository upon save. Set this property to true for a document type that may be used to define the structure and content for the value of an Any field in a document that is published to Digital Event Services.

Migration Utility handles updates for hostname Prior to release 10.2, if you upgraded your Integration Server by installing the new release on a different machine, you had to update the database components below to reflect the host name of the new machine, as follows:

If you had scheduled tasks that executed on Integration Server on specific machines in your old installation, you had to update database component ISInternal, table IS_USER_TASKS, column TARGET.

If you wanted to be able to resubmit services that ran before you upgraded, you had to update the following:

Database component ProcessAudit, table WMRULEDIST, column SERVID.

Database components IS CoreAudit, ProcessAudit; tables WMDOCUMENT, WMSERVICE, WMSERVICE4X, MSERVICEACTIVITYLOG, WMSERVICEASSOC, WMSERVICECUSTOMFLDS; column SERVERID.

If you wanted to be able to resubmit processes and process steps that ran before you upgraded, you had to update database component ProcessAudit, table PRA_PROCESS_STEP, SERVERID column.

No support for host-based name format. Integration Server does not support the host-based name format to specify the Service Principal Name Format when adding or editing an HTTP(s) port.

updateLanguagePack command for is_instance script. Provides an option to specify the package and/or feature list to which to apply the language pack installation.

create command for is_instance script. Provides an option for specifying a default IP address to which to bind ports on the new Integration Sever instance.

Server log entries can be written to the console, a file, or both. Previously, Integration Server could write server log entries to a file or the console (STDOUT). Now, the -log switch includes the both option to write server log information to the computer screen (STDOUT) and to the destination specified by the watt.debug.logfile parameter.

Docker container for an Integration Server Docker image writes the server log to the console (STDOUT). When running a Docker image of Integration Server in a Docker container, Integration Server writes the server log to the console as well as to the server.log file. Many container deployment solutions provide the ability to view the console log STDOUT for a container.

Repeating tasks scheduled to execute in the Daylight Savings Time (DST) overlap. If a task includes an hours mask (e.g., "1:15" for running every date at 0115), then the task will run only once, at the pre-overlap ("first") matching time. However, if a task does not have an hours mask (e.g., "hh:15", meaning run at 15 minutes past each hour), then the task will run at the pre-overlap time (the "first" 1:15), and also at the overlap time (the "second" 1:15). Previously, the absence of an hours mask did not result in the task executing twice.

Diagnostic collector To help with debugging, the Integration Server diagnostic collector returns information regarding whether or not the JCE Unlimited Strength Jurisdiction Policy File is applied to the JVM in the config\ServerAbout.txt file.

Digital Event Service type definition With the introduction of support or Any fields and Map fields for Digital Event Services, the Digital Event Type definition generated for a publishable document type changes in the following ways:

An Object or Object List with a Java wrapper type of UNKNOWN is included in the Digital Event Servers event type definition as an Any or Any field. Previously, an Object or Object List field with an UNKNOWN Java wrapper type were not included in the corresponding Digital Event Services type definition

An empty inline document variable in a publishable document type is now represented as Map field in the corresponding Digital Event Services type definition. Previously, an inline document variable became an empty nested event.