|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Middleware Architecture |
« View previous topic :: View next topic » |
Author |
Message
|
sajid08 |
Posted: Sat Sep 16, 2006 12:01 am Post subject: Middleware Architecture |
|
|
Novice
Joined: 08 Sep 2006 Posts: 22 Location: Karachi
|
Hi All!!
We are working to implement middleware solution for a large bank. We require the solution be to enable us toward SOA. Point to Point integration is mainly done at the moment. We want to change and put the middleware in b/w. The most important question of all is which architecture and products to choose.
IBM offers quiet a few fantastic products for integration solutions, but the problem is we are not familiar with them and what they do, so it is difficult to map them on a Architecture:
1. One architecture that we are considering is applications sending messages to WebSphere MQ, and from their Broker picks the messages up and route them according to their content or to a pre-configured way to services. But that is still pretty much point-to-point? Also one more thing we want to ask about this architecture is can we define a complete two-way message flow with this? what I mean by this is:
Application --> WebSphere MQ --> Message Broker --> Service
thats the flow, but can we define a flow in broker, where it performs the backword flow as well, meaning it picks up the reply from service and returns it to a queue where the application can pick the message? Can we correlate messages?
And the other very important thing is where to host services?
WebSphere ESB is also there, how do you see that can be used with broker or without broker?
I'd like all the expert people out there to comment or give us suggests, all of that would be highly appreciated. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Sep 16, 2006 3:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
You want websphere ESB if your architecture includes XML capable components ONLY. Otherwise you want the full Message Broker. No problems with correlation ID and returns from the service, Message Broker V6 handles that very gracefully. Cobol copy books imports are no problem either.
Depending on your needs you might want to add the Process server into your picture. (Long running stateful transactions)
If you are already using a number of IBM products (CICS, IMS, etc) get them involved early and have them talk to you about integrating all of them.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Sep 16, 2006 4:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I have already told you that Broker can handle a request/reply scenario.
And I really hope, for your sake, that nobody at the bank reads this message. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sajid08 |
Posted: Sat Sep 16, 2006 5:20 am Post subject: |
|
|
Novice
Joined: 08 Sep 2006 Posts: 22 Location: Karachi
|
Ok so, if we go for Process Server, ESB is included in it, We can get the Business Modeler, and WID, for development of it. So Process Server can pretty much fix the bill.
But do you see any role of Message Broker in presence of all these?. I understand it has alot of adapters for reaching out to legacy applications and it presents an Ultra High Transaction speed. But what would we really lack if we not use Broker with Process Server?
If we decide to use Broker then on which role it would fit in if we use Process Server and ESB with it?
Thanks for the responses, its really nice!! |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Sep 16, 2006 7:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
FJB_Saper has already told you that ESB can only handle XML data. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
msukup |
Posted: Tue Sep 19, 2006 5:48 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002 Posts: 56
|
sajid,
Here is a very helpful link in helping you map out your architecture. Each pattern also contains a possible product mapping (runtime patterns). It is quite a lot of reading, but highly useful:
http://www-128.ibm.com/developerworks/patterns/
There are also a couple of great redbooks about the architecture patterns. There are several variations, one that focuses on Websphere ESB, and one with MB.
Patterns: SOA Foundation Service Creation Scenario
http://www.redbooks.ibm.com/abstracts/sg247240.html?Open
Patterns: SOA Foundation Service Connectivity Scenario
http://www.redbooks.ibm.com/abstracts/sg247228.html?Open
Patterns: Integrating Enterprise Service Buses in a Service-Oriented Architecture.
http://www.redbooks.ibm.com/abstracts/sg246773.html?Open
Generally, MB is great for integrating legacy without requiring adapters that "speak" SOAP (meaning you can map payload to COBOL copybook). Its weakness is that, out-of-the-box, it doesn't accomodate for WS-Security, WS-Policy, WSDM, etc -- you can handle some of these reqs with the "Gateway" pattern mentioned in the redbook (Gateway handles security; a gateway product might be DataPower . . .), or write your own plugins. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|