MQSeries.net :: View topic - Version Control in Message Flow

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Version Control in Message Flow

Version Control in Message Flow

« View previous topic :: View next topic »

Author

Message

pottas

Posted: Mon Jun 23, 2008 7:03 am Post subject: Version Control in Message Flow

Disciple

Joined: 27 Oct 2005
Posts: 185
Location: South Africa

Guys,
I have the following design question around handling different versions of WSDLs in Message Broker.
I will try to sketch the scenario for you:

WSDLContract[1]:

Quote:

SOAPInput --> Compute --> SOAPRequest[1] --> Compute --> RCD(WSDLContract[1]) --> SOAPReply

...now I introduce a second version of the WSDLContract to the flow. So in my SOAPRequest[1] and RCD, I would like to dynamically reset to the WSDLContract[2]. The message follows the same route (might be that I tweak the Compute Nodes to handle the New WSDL as well), but I want to use a different SOAPRequest and a different RCD in the same flow.

..my modified flow should look like:
WSDLContract[2]:

Quote:

SOAPInput --> Compute(mod) --> SOAPRequest[1] or SOAPRequest[2] --> Compute(mod) --> RCD(WSDLContract[1] or WSDLContract[2]) --> SOAPReply

The point I want to get to is have a flow that will work for multiple versions of the WSDL without a heck of a lot of regression testing. As regression testing is a swearword in the bank I work for...

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Version Control in Message Flow

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP