Reliable Adapter Endpoints

Replies to This Discussion

Permalink Reply by Neuron Admin on September 25, 2015 at 1:24pm

The only way to solve this is to use either MSMQ or Rabbit MQ based topics since they provide the store and forward.

if you can only use msmq, and the messages are greater than 4MB in size (hopefully not that much bigger.....), then you will have to store and retrieve them before they are published.

for example, create a Business Process in our designer and attach it to the OnPublish event of the publisher.  In the process, you'll intercept the message...if its greater than 4MB, write it out to a folder and then reset the esbmessage so that it just contains the url location of the data that you just wrote out.

Next, create a Business Process in our designer and attach it to the OnReceive event of the subscriber.  In that process, you'll look for whatever meta data you add to our message to determine if the message contains the data...or just the url to the data.  if the url, then within the process, read the data in back into our message and let the process continue.  the original message data will then be forwarded to the adapter endpoint. 

• ▶ Reply

Permalink Reply by Gihan Attanayake on September 27, 2015 at 9:25pm

Hi Admin,

Thanks for your reply. 

Is there a way I can create a Business Process, so that when WebSphere MQ adapter pick the message, it first checks the is subscriber available. If not, keep the message (or put back) in WebSphere MQ instead of deleting it from there? That way WebSphere MQ can be used as a store instead of MSMQ. Is this possible in ESB?

Is there any property I can set on WebSphere MQ adapter, so it pick a copy of the messages from WebSphere MQ?

Cheers,

Gihan

• ▶ Reply