Hi All,
Just to give a quick update on the scenarios we'll be illustrating to
demonstrate the ESB/MB integration, the following are the flows which will
be illustrated as per our discussion during the review meeting,
*(1) http to jms (For Both queue and topic subscriptions)*
~ ESB as a producer/consumer
~ Dual Channel JMS, Quad Channel JMS
*(2) message store, processor*
*(3) cache enable *
*(4) client ack*
Sewwandi is currently progressing on setting up the http to jms flows, and
i am currently in progress of setting up flows to demonstrate message
stores and processors, we're hoping to merge both the configurations to a
single proxy the, following is the plan we have for a proxy service which
will cover (1) and (2) of the areas above,
There will be mainly 4 proxy services and 1 sequence which will be created
1) first the user will invoke the HTTP_Invocation_Proxy this will place the
message in the JMSMessageStore,
*HTTP_Invocation_Proxy -----> JMSMessageStore (This will also depict
HTTP-JMS)*
2) Message processor would read from the store and will send the message to
a BE_HTTP_Service_Proxy
*JMSMessageProcessor --------> BE_HTTP_Service_Proxy (This will depict
JMS-HTTP)*
the response from the BE_HTTP_Service_Proxy would be directed to the
BE_Response_Receiver_SEQ
3) BE_Response_Receiver_SEQ will send a message to JMS_Worker_Queue having
the *replyTo* flag set to *Worker_Consumer_Queue*
*BE_Response_Receiver_SEQ -------> JMS_Worker_Queue (HTTP - JMS)*
4) JMS_Worker_Queue_Proxy will consume the message from the queue and will
send the message to JMS_Manager_Queue having the reply-to flag set to
*Manager_Consumer_Queue*
*JMS_Worker_Queue_Proxy -------> JMS_Manager_Queue*
*(JMS-JMS)*
5) JMS_Manager_Queue_Proxy will consume the message from JMS_Manager_Queue
and will write the result to *Manager_Consumer_Queue*
JMS_Manager_Queue_Proxy-----> *Manager_Consumer_Queue **(JMS-JMS)*
6) JMS_Worker_Queue_Proxy will read from *Manager_Consumer_Queue *for the
response
JMS_Worker_Queue_Proxy-----> *Manager_Consumer_Queue **(JMS-JMS)*
7) JMS_Worker_Queue_Proxy will write the result to the
*Worker_Consumer_Queue*
JMS_Worker_Queue_Proxy -------> Worker_Consumer_Queue* (JMS-JMS)*
8) BE_Response_Receiver_SEQ will read the output from *W*
*orker_Consumer_Queue* as response as will log the message
*W**orker_Consumer_Queue --------> *BE_Response_Receiver_SEQ (JMS-HTTP)
Will also update the thread on the plan to demonstrate the topics behavior,
message selectors, caching and client ack capabilities. Please do let know
if there're amendments to be done in the above plan.
Thanks,
Pamod
--
*Pamod Sylvester *
* Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: [email protected] cell: +94 77 7779495
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
