Configuring Integration Server to Handle Native Broker Events
By default, Integration Server encodes and decodes data it passes to and from the Broker as follows:
When
Integration Server sends a document to the
Broker, it first encodes the document (IData object) into a
Broker event.
When
Integration Server receives a document from the
Broker, it decodes the
Broker event into an IData object.
In some situations, you may want to bypass this encoding or decoding step on Integration Server and instead send and receive “native” Broker events to and from the Broker. These situations are when you:
Migrate Enterprise business logic to
Integration Server.
Use custom
Broker clients written in Java, C, or COM/ActiveX.
You configure Integration Server to handle native Broker events by setting server parameters.
To configure
Integration Server to handle native
Broker events
1. Open the Integration Server Administrator if it is not already open.
2. Go to Settings > Extended.
3. Locate the watt.server.publish.usePipelineBrokerEvent parameter and change its value to true.
If the watt.server.publish.usePipelineBrokerEvent parameter is not displayed, see webMethods Integration Server Administrator’s Guide for instructions on displaying extended settings.
4. Locate the watt.server.publish.validateOnIS parameter and change its value to never.
5. If Integration Server is retrieving documents from the Broker on behalf of a trigger, locate the watt.server.trigger.keepAsBrokerEvent parameter and change its value to true.
6. Click Save Changes.
7. Restart Integration Server.
Note:
If you set the watt.server.trigger.keepAsBrokerEvent parameter to true and the watt.server.publish.validateOnIS parameter to always or perDoc, you will receive validation errors.