What's new in integration with external applications
New Apache Kafka client for data integration
You can integrate with the Kafka messaging platform to publish and consume messages asynchronously from Kafka. Kafka can be configured as an external message provider that accepts and stores outbound and inbound messages.
The product provides the Kafka messaging client that supports consuming, producing, and browsing Kafka topics. To use Kafka features in the product, you must obtain and configure a Kafka server instance. You can choose any Kafka provider that is compatible with the Kafka 1.1.1 client libraries.New API Key security restrictions
A new system property can limit creating an API key to the logged-in user only.
Learn more about enabling the new API Key security restriction.
New creating API Keys outside of the product
You can use an external system to create the API key and provide the API key value to the integration framework.
New REST APIs instead of RMI batch files
You can use the new REST APIs instead of using Remote Method Invocation (RMI) batch files to work with the product. The REST APIs enable use of API Keys for authentication.
New in the endpoint handler for web services
Now you can add automation scripts to configure SOAP endpoint exits.
New in HTTP endpoint handlers
Now you can code HTTP endpoint exits by using automation scripts. Also, for the HTTP endpoint handler, the HTTP PATCH method is now supported.
New filtering of publish channel events by using conditions
Publish channels now support filtering events by specifying a Maximo® condition. To use this feature, specify the condition identifier in the Event Filter Class field of a publish channel. The event is filtered out if the condition is evaluated as true. The event passes through if the condition is evaluated as false.