Integration Server 10.3 | Publish-Subscribe Developer’s Guide | Publishing Documents | Impact of Universal Messaging Changes to Shared Durables on Document Delivery
 
Impact of Universal Messaging Changes to Shared Durables on Document Delivery
 
Client IDs for Triggers and the Destination ID in pub.publish:deliver* Services
In Universal Messaging version 10.0 the implementation of shared durables was rewritten to improve stability and performance. However, these changes were not compatible with the pub.publish:deliver* services which relied on the previous implementation of shared durables to ensure that delivered documents were routed by Universal Messaging to the intended destination. As of version 10.3 (and in fixes delivered on earlier releases), Universal Messagingimplemented subscriber name filtering for its durable subscriptions. In subscriber name filtering, when a publisher designates a message for a specific subscriber, Universal Messaging routes the message to a consumer whose durable subscription name matches the designated subscriber name in the message. For Integration Server, the subscription name filtering requires some modifications, specifically:
*Enable the subscription name filtering feature on Universal Messaging To enable the feature through Universal Messaging Enterprise Manager, navigate to the realm and select the Config tab. In the realm server configuration panel, click Show Advanced Config. Expand Advanced Configuration - Durable Config, and set Durable Name Filtering to true.
*Change the destID input parameter value in invocations of pub.publish:deliver and pub.publish:deliverAndWait, if necessary. This may only be necessary when the trigger to which the message is to be delivered contains an underscore in its name. For more information about client IDs for triggers and how this change may impact existing services that invoke pub.publish:deliver*, see Client IDs for Triggers and the Destination ID in pub.publish:deliver* Services.