| Author |
Message
|
| preethalakshmi.s |
 Posted: Thu Nov 29, 2012 12:39 am Post subject: Connecting WMB v7 borker to WMB v8 Broker CompatibilityIssue |
 |
|
Newbie
Joined: 28 Nov 2012
Posts: 2
|
Hi,
We have a scenario where we need to use two ESBs, one Global ESB that runs WMB v7 broker and one Local ESB that uses WMB v8 broker.
Currently we are doing a Risk analysis on this and want to ensure if there would be any compatibility issues in doing simple routing and transformations and connecting between the two versions of broker.
Any pointers on any risk involved in connecting two brokers of different versions will be really helpful.
Many thanks,
Preetha |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Nov 29, 2012 2:53 am Post subject: Re: Connecting WMB v7 borker to WMB v8 Broker CompatibilityI |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| preethalakshmi.s wrote: |
Hi,
We have a scenario where we need to use two ESBs, one Global ESB that runs WMB v7 broker and one Local ESB that uses WMB v8 broker.
Currently we are doing a Risk analysis on this and want to ensure if there would be any compatibility issues in doing simple routing and transformations and connecting between the two versions of broker.
Any pointers on any risk involved in connecting two brokers of different versions will be really helpful.
Many thanks,
Preetha |
how are you proposing to 'connect the two brokers'? And for what purpose are you connecting them up.
I'd use MQ Channels be done with it. However if there is some aversion at your site to using this method then you are pretty much on your own.
Also remember that once you get dependant upon TWO brokers your MTBF has halved and you now have two systems to conside wrt failure etc.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 29, 2012 4:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So from the point of view of each broker, the other broker is not a broker.
It's simply a service provider or consumer.
So what you're asking is the same as asking "what's the risk of connecting a broker version X to a set of service providers and consumers?".
Treat each broker as if it were a global ESB. Treat all of the endpoints it exposes and consumes as if they were hosted on completely unknown hardware and software. The risks you face with connecting to those endpoints are the risks of the interfaces to those endpoints. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Nov 29, 2012 7:46 am Post subject: Re: Connecting WMB v7 borker to WMB v8 Broker CompatibilityI |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| preethalakshmi.s wrote: |
Any pointers on any risk involved in connecting two brokers of different versions will be really helpful.
|
There is no risk actually in connecting two brokers as the protocol between them is what matters. They are totally two independent entities and there should be no risk in connecting between them.
But here what you really mean by connecting two brokers needs more clarity for better responses. |
|
| Back to top |
|
|
| preethalakshmi.s |
| Posted: Thu Nov 29, 2012 9:18 pm Post subject: |
|
|
Newbie
Joined: 28 Nov 2012
Posts: 2
|
Hi All,
Thanks a lot for all the responses.Here is the detailed scenario.
We are working as part of a merger, where the two clients operating from two different geographies are using different versions of WMB , 7.0 and 8.0 and would want to retain both their ESBs to communicate between them and within each's downstream applications.
We have identified one as a Global ESB that will perform Pure routing and Generic transformation so that it is abstracted from formats of downstram systems at high level and this will connect to the Local (regional) ESB which then takes care of bespoke transformations and internal routing.
Communication protocol between the two brokers is still under discussion though SFTP is proposed and preferred by clients as the message size is expected to be huge.We are still on discussion if we can use MQ for such huge volume of data and is it worth using MQ instead of FTP for such a scenario?
Davies,
Could you pls throw some light on this MTBF and how we can ensure we reduce it if we still need to use both the brokers and connect between them?
Also as rightly being point out by Mqjeff and Kash, in the view of one broker, the other is just like any other service that needs to connect to it, if we look at it in that way it seems all well and we can go ahead  but ...beacuse these two are different versions of brokers deplyed in their own environments and each have their responsibility to process data from their end, will there be any risk that needs to be considered?  |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Nov 29, 2012 11:08 pm Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
From development and management point of view you have to be extra careful whit which version artifacts you are dealing and develop decent processes to manage version controlling, development, buildings and deployments.
And at some point you have to upgrade version 7 broker (and of course at the time also 8). Perhaps you can run version 8 broker parallel at the local ESB too and decide to start develop new projects with 8 and start migrating from 7 to 8 when existing artifacts needs to be changed?
--
Marko |
|
| Back to top |
|
|
| kash3338 |
| Posted: Fri Nov 30, 2012 12:12 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| preethalakshmi.s wrote: |
| Communication protocol between the two brokers is still under discussion though SFTP is proposed and preferred by clients as the message size is expected to be huge.We are still on discussion if we can use MQ for such huge volume of data and is it worth using MQ instead of FTP for such a scenario? |
To me MQFTE seems to suite you best, but any other suggestions from experts here can also be taken into account.
| preethalakshmi.s wrote: |
but ...beacuse these two are different versions of brokers deplyed in their own environments and each have their responsibility to process data from their end, will there be any risk that needs to be considered? |
Actually there should be not any risk because of different versions since they act as totally different entities (as mentioned earlier). But as mentioned by marko.pitkanen, you should be considering migrating v7.0 to v8.0 and insight of that you can plan to use a single broker (v8.0) at later point as a overall ESB implementation. To do that, your below quote should be redesigned, and use just one ESB for both routing and all complex transformations.
| preethalakshmi.s wrote: |
We have identified one as a Global ESB that will perform Pure routing and Generic transformation so that it is abstracted from formats of downstram systems at high level and this will connect to the Local (regional) ESB which then takes care of bespoke transformations and internal routing |
|
|
| Back to top |
|
|
|
|
