Configurations which will demonstrate the above mentioned flows can be found in [1]. Also configurations to validate the behavior of ESB as a publisher/subscriber to a topic also could be found in the same location. You could test it through invoking the following services,
1) In order to test the message flows of the queues which will take you through the process mentioned above can be achieved through invocation of the service "_UserJMSMessageStoreForwardProxy" as a result you would see logs printed for each phase in the following manner, LogMediator STATE : = MESSAGE INSERTED TO QUEUE (MessageStore) HTTP-JMS LogMediator STATE : = MESSAGE CONSUMED FROM QUEUE (Through Message Processor) JMS-HTTP LogMediator STATE : = MESSAGE CONSUMED FROM QUEUE TO INVOKE_SVC_2 JMS-HTTP LogMediator STATE : = MESSAGE SENT AS DUAL CHANNEL HTTP-JMS LogMediator STATE : = MESSAGE CONSUMED FROM DUAL CHANNEL QUEUE_SVC_2 JMS-HTTP LogMediator STATE : = MESSAGE SENT TO QUAD CHANNEL JMS-JMS LogMediator STATE : = MESSAGE CONSUMED FROM DUAL QUADCHANNEL PROXY JMS-JMS LogMediator STATE : = MESSAGE SENT AS QUAD RESPONSE PROXY JMS-JMS LogMediator STATE : = MESSAGE RECIVED FROM QUAD CHANNEL JMS-JMS LogMediator STATE : = MESSAGE RESPONSE RECEIVED IN DUAL CHANNEL JMS-JMS Through the single invocation it will demonstrate, message stores/processors, ESB as a message consumer/producer, dual channel JMS and quad channel JMS flows. 2) In order to test the flows related to the topics, invocation of the service _UserTopicInvoke would result in ESB acting as a producer to the topic as well as a subscriber. Currently we're in progress of compiling a business use case to map with the above functionality. Also we're in progress of creating services to demonstrate message caching and client acks. Please do review the above flows and do let know if there're any additions for it. [1] https://svn.wso2.org/repos/wso2/scratch/pamod/mb_esb_flows/esb_arifacts Thanks, Pamod On Wed, Apr 23, 2014 at 9:27 AM, Pamod Sylvester <pa...@wso2.com> wrote: > 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: pa...@wso2.com cell: +94 77 7779495 > -- *Pamod Sylvester * * Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: pa...@wso2.com cell: +94 77 7779495
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
