Author |
Message
|
BrianS |
Posted: Fri Jan 13, 2006 4:12 am Post subject: MQSeries Integrator |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
A product I used years ago was called MSeries Integrator -- set up a few queues on the MVE/CICS side and an NT side then use this Integrator product to define process flow for distribution, translation etc..
So now I have to pitch a proposal this Monday for a somewhat very large project involving some 23 sights for publish/subscribe -- first thing I thought of was MQSeries Integrator.
I spent all night on IBM's website and could not make heads or tails of what is available today. Searching on MQSeries Integrator there was nothing but broken links, mentions of other products etc.
What has become of MQseries Integrator the graphical process flow tool that was so good? |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jan 13, 2006 4:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Rebranded : Websphere Business Integrator ? Search under MQSI will give you the message broker if this is what you are gunning for...
Enjoy
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
BrianS |
Posted: Fri Jan 13, 2006 4:19 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
fjb_saper wrote: |
Rebranded : Websphere Business Integrator ? Search under MQSI will give you the message broker if this is what you are gunning for...
Enjoy
 |
I saw Message Broker but could not figure out if that was the MQSI product I knew and used a few years ago. Do you know where I can look at some screen shots of Message Broker? Also if I opt for a Message Broker then what other products are required?
Thanx. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jan 13, 2006 4:24 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
MQ is a prerequisite to the broker as it is build on top of it.
You will want as well a DB. Check out the product sheet there is a number of certified DBs (DB2 of course, Oracle, ...)
For screen shots look at the manuals and pdfs / redbooks.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jan 13, 2006 4:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Message Broker is the most recent version of what used to be Integrator.
Version 2.0 was MQSeries Integrator.
Version 2.1 was WebSphere MQ Integrator
Version 5 was WebSphere Business Integration Message Broker
Version 6 is WebSphere Message Broker.
It's still mostly the same product... except it's several revisions later. The same general concepts are there, and you can still use ESQL. But there's a lot of new stuff, and the Tooling is different (and to a large extent, better). _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
BrianS |
Posted: Fri Jan 13, 2006 6:26 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
jefflowrey wrote: |
Message Broker is the most recent version of what used to be Integrator.
Version 2.0 was MQSeries Integrator.
Version 2.1 was WebSphere MQ Integrator
Version 5 was WebSphere Business Integration Message Broker
Version 6 is WebSphere Message Broker.
It's still mostly the same product... except it's several revisions later. The same general concepts are there, and you can still use ESQL. But there's a lot of new stuff, and the Tooling is different (and to a large extent, better). |
Thank You
So moving forward -- for a customer with nothing MQ in place today where I need one server site and 23 client sites in a Pub/Sub arrangement and I want to propose use of MQSeries Integrator I should get pricing on the following:
IBM WebSphere MQ Processor
IBM WebSphere Message Broker Processor
Would that be all I need? |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jan 13, 2006 6:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You don't really even need the license for MQ, assuming they have MQ every where they need it that is not where Broker lives.
Broker licensing includes licenses for MQ and DB2 - for use with the product itself.
A broker production license also covers (as I understand it) as many developer workstations as you want to have, with full product installs for local testing only (no interconnection between workstations, but a fully operational broker/cfg mgr on every developer station).
But as always, all licensing questions should go through your IBM sales representative. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
BrianS |
Posted: Fri Jan 13, 2006 7:01 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
jefflowrey wrote: |
You don't really even need the license for MQ, assuming they have MQ every where they need it that is not where Broker lives.
Broker licensing includes licenses for MQ and DB2 - for use with the product itself.
A broker production license also covers (as I understand it) as many developer workstations as you want to have, with full product installs for local testing only (no interconnection between workstations, but a fully operational broker/cfg mgr on every developer station).
But as always, all licensing questions should go through your IBM sales representative. |
Well that would be cool -- what I think will be the proposal is to put broker into production on their Sun Server. 23 client stations (at varous sites around the country) will send and recieve via their own respective queues from broker. So from your statement it doesn't look like I need client licensing to add a queue? From the prelim designs it looks like I need two queues setup for each client. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jan 13, 2006 9:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
MQ Clients are free.
If you are going to put Queue Manager on the clients to serve production data, then you need to license those QMS for production.
As I understand it.
Again, all license questions can only really be answered by your IBM sales rep. That person may completely disagree with what I have said, and they will be correct and I won't. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
BrianS |
Posted: Fri Jan 13, 2006 9:30 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
jefflowrey wrote: |
MQ Clients are free.
If you are going to put Queue Manager on the clients to serve production data, then you need to license those QMS for production.
As I understand it.
Again, all license questions can only really be answered by your IBM sales rep. That person may completely disagree with what I have said, and they will be correct and I won't. |
Thanx for the note on licensing -- we will be in touch with an IBM rep on all this. For now I am just trying to figure out who has what.
I think I worded things wrong -- the clients won't have a Queue themselves but instead will put and get from queues on the server running Broker.
If I put a queue on a client box then I would need to license Queue Manager correct? If the client uses queues on the Broker server machine then I only need to install MQ Client on the client box. Correcct?
Again thanx |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Jan 13, 2006 9:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Yes. If there isn't a queue manager on the client box, but you want the client box to connect the the Broker's queue manager, then you need to install the free MQ Client on each client box. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
BrianS |
Posted: Tue Jan 17, 2006 7:25 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
jefflowrey wrote: |
Yes. If there isn't a queue manager on the client box, but you want the client box to connect the the Broker's queue manager, then you need to install the free MQ Client on each client box. |
Thanx -- looks like the direction the client wants to go is to have MQSeries Queuemanager and the MA0C SupportPac Pub/Sub Broker installed at three sites. Once the three sites are up the brokers will be linked together so that from the outside work it looks like one central Pub/Sub Broker.
The clients who will subscribe are on a number of platforms such as Sun, Linux, Mac and Windows -- understanding the client is free my question is what is the minimum I need to put on the client in order for them to subscribe to the topics made available by the Broker?
Thanx. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Jan 17, 2006 7:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Actually, you shouldn't use MA0C any more. It's built into the product as of CSD8 of v5.3 - so you merely need to upgrade all Qmgrs in question to CSD11 (CSD 8 and 9 have some issues) or to v6.
The safest course is to install the full client on all machines that need to access a qmgr. Anything else is unsupported by IBM. You can get away with just some jar files if your apps are Java, but it's not supported that way. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
wschutz |
Posted: Tue Jan 17, 2006 7:43 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Brian..ma0c is no longer needed with MQ, its included in V6 and became part of the base product with MQ V5.3 at some CSD level (I forget which one). EDIT: its CSD8.
You've been talking about using the WebSphere Message Broker (aka MQSI etc...) to do Pub/Sub. Has that plan changed and now you are using the Pub/Sub engine that ships with WMQ? _________________ -wayne |
|
Back to top |
|
 |
BrianS |
Posted: Thu Jan 19, 2006 6:02 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2006 Posts: 9
|
wschutz wrote: |
Brian..ma0c is no longer needed with MQ, its included in V6 and became part of the base product with MQ V5.3 at some CSD level (I forget which one). EDIT: its CSD8.
You've been talking about using the WebSphere Message Broker (aka MQSI etc...) to do Pub/Sub. Has that plan changed and now you are using the Pub/Sub engine that ships with WMQ? |
Yup -- gonna have to propose this solution to the customer on a budget. The proposal long term will scale out to include MQSI where transactions reach set volume thresholds and the needs for additional process flows and possible translations become a factor. But for now we can get away with spending 1/3 to 1/2 less and instead put v6 of Queue Manager broker on four sites and linking the brokers to form a virtual central broker for a very basic Pub/Sub.
Thanx and thanx for noticing the plan change, impressed. |
|
Back to top |
|
 |
|