Author |
Message
|
Partha.Baidya |
Posted: Thu May 26, 2016 10:04 am Post subject: IIBv10 Internal runtime components |
|
|
 Voyager
Joined: 05 Nov 2009 Posts: 97
|
Could you please give me light about IIBv10 internal run time components?
Prior to v10 WMQ used to have internal Queues created when we install WMB. These internal MQs used to contain run time data required for WMB to function.
Now WMA is not required for IIB. Where and how IIB is keeping runtime data? |
|
Back to top |
|
 |
maurito |
Posted: Thu May 26, 2016 10:40 am Post subject: Re: IIBv10 Internal runtime components |
|
|
Partisan
Joined: 17 Apr 2014 Posts: 358
|
Partha.Baidya wrote: |
Could you please give me light about IIBv10 internal run time components?
Prior to v10 WMQ used to have internal Queues created when we install WMB. These internal MQs used to contain run time data required for WMB to function.
Now WMA is not required for IIB. Where and how IIB is keeping runtime data? |
I don't think that information will be made public as it concerns design decisions that are confidential. |
|
Back to top |
|
 |
Vitor |
Posted: Thu May 26, 2016 12:17 pm Post subject: Re: IIBv10 Internal runtime components |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Partha.Baidya wrote: |
Where and how IIB is keeping runtime data? |
Why do you need to know? What value does this knowledge have for you? What use could you put it to? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Partha.Baidya |
Posted: Thu May 26, 2016 5:15 pm Post subject: |
|
|
 Voyager
Joined: 05 Nov 2009 Posts: 97
|
I am looking at IIB high availability. As previous versions using WMQ, then for HA we need to create multi instance Queue Manager to configure HA. As IIB is not using WMQ then why do we need to create multi instance Queue manager. That's why I want to know how the IIB internal works. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 27, 2016 3:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Without an MQ MI queue manager, can't you simply deploy your flows to two independant IIB configurations - in an active/active setup?
If one goes down, well, one goes down. Work continues to flow. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 27, 2016 4:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Partha.Baidya wrote: |
That's why I want to know how the IIB internal works. |
You shouldn't want that. You should want to read the IIBv10 InfoCenter more carefully. Because then you wouldn't be saying:
Partha.Baidya wrote: |
As IIB is not using WMQ |
which is not true. As described here, IIBv10 does indeed use MQ. What has changed between v10 and earlier version is that MQ is no longer a pre-requisite for IIB and it's no longer mandatory to have a queue manager.
So if you're looking to create a highly available IIBv10 solution, you need to consider any MQ that IIBv10 is using as part of the solution. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 27, 2016 4:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Vitor wrote: |
As described here, IIBv10 does indeed use MQ. |
For those functions listed, and only those functions listed.
Quote: |
What has changed between v10 and earlier version is that MQ is no longer a pre-requisite for IIB and it's no longer mandatory to have a queue manager.
So if you're looking to create a highly available IIBv10 solution, you need to consider any MQ that IIBv10 is using as part of the solution. |
Right. But if you're not using any of those functions, there's no reason to create a multi-instance Broker. Just use two brokers. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 27, 2016 4:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Vitor wrote: |
As described here, IIBv10 does indeed use MQ. |
For those functions listed, and only those functions listed. |
mqjeff wrote: |
Vitor wrote: |
What has changed between v10 and earlier version is that MQ is no longer a pre-requisite for IIB and it's no longer mandatory to have a queue manager.
So if you're looking to create a highly available IIBv10 solution, you need to consider any MQ that IIBv10 is using as part of the solution. |
Right. But if you're not using any of those functions, there's no reason to create a multi-instance Broker. Just use two brokers. |
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Partha.Baidya |
Posted: Fri May 27, 2016 7:26 am Post subject: |
|
|
 Voyager
Joined: 05 Nov 2009 Posts: 97
|
You mean to say if none of my message flow is using MQ I do not need a multi instance Queue manager for high avaibility. Only two instance of broker can create a high available solution.
@Vitor, could you please confirm if this understanding is right? |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 27, 2016 7:38 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Partha.Baidya wrote: |
@Vitor, could you please confirm if this understanding is right? |
It's not. Which I think proves you've not looked at that link I included.
If none of the flows are using application level MQ (MQInput, MQOutput or MQGet nodes) but are using a feature that requires MQ (such as an aggregation) then you need a queue manager and that queue manager needs to be as highly available as the broker running the flow. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Partha.Baidya |
Posted: Fri May 27, 2016 7:47 am Post subject: |
|
|
 Voyager
Joined: 05 Nov 2009 Posts: 97
|
I got your point.
But if I am not using aggregration and other functionality where I need MQ to create the message flow. Then in that environment it would not require to have multi instance Queue Manager, only multi instance of Broker will provide high availability.
Please correct me. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 27, 2016 7:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
as long as you're clear about the difference between "two brokers" and "a multi-instance broker".
The first one is active/active. The second is active/passive, and requires MQ. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 27, 2016 7:51 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
If you're not using any of the IIB features that require a queue manager, then you don't need a queue manager. If you don't need a queue manager, then you don't need the queue manager than you don't have to be multi-instance. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Partha.Baidya |
Posted: Fri May 27, 2016 9:36 am Post subject: |
|
|
 Voyager
Joined: 05 Nov 2009 Posts: 97
|
mqjeff wrote: |
as long as you're clear about the difference between "two brokers" and "a multi-instance broker".
The first one is active/active. The second is active/passive, and requires MQ. |
@mqjeff, I am not getting a clear idea about "two brokers" and "a multi-instance broker".
Is it
two broker= two different installation of broker without MQ
multi-instance broker= two different broker with multi instance queue manager.
Could you please help me to clear my understanding?
Thanks al lot for your effors. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 27, 2016 10:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
"Two brokers " is Broker A on Machine A and Broker B on Machine B.
"Multi Instance Broker" is Broker A on Machine A, that can fail over to Machine B.
The second requires MQ, and a multi-instance queue manager.
The first doesn't. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
|