Author |
Message
|
catshout |
Posted: Sun Nov 06, 2016 7:30 am Post subject: Enable MQEndpoint policy globally for all MQ nodes? |
|
|
Acolyte
Joined: 15 May 2012 Posts: 57
|
Hi everybody,
I've setup an IIBv10 (with MQ Client) and IMQv8 on different machines. For MQ connectivity I've created a MQEndpoint policy and tested it successfully for a sample flow (assigned it to the MQ nodes).
As we have a lot of flows in our current environment that work with local queues; do I need to add the policy to every MQ related node? Or is there a way to assign a kind of "standard" MQEndpoint policy to the integration node and all flows/nodes will inherit this policy by default?
Best regards
- Gerald |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Nov 07, 2016 5:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
If you have a lot of flows that work with "local" queues, why don't you run IIB on top of a local queue manager?
I'm guessing (I haven't done it) that you would need an MQ policy for each external queue manager you are connecting to, and would have to apply that policy to each MQ node that neede to work with MQ.
Again, if that's a lot of nodes, seems a better idea to run IIB on top of a queue manager. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Craig B |
Posted: Thu Nov 10, 2016 2:58 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
Unfortunately there is no method of applying a default MQEndpoint to the whole broker or integration server. For an MQEndpoint policy to take affect on an MQ node, it has to be set individually on that node.
It is also not possible to promote the policyURI to the flow level.
Ie there is no way to set the an MQEndpoint policy as a BAR Override such that it applies to every MQ node that has promoted it.
So I'm afraid you will have to set the MQEndpoint policy individually on each MQ node in the Toolkit. _________________ Regards
Craig |
|
Back to top |
|
 |
Vitor |
Posted: Thu Nov 10, 2016 5:38 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Craig B wrote: |
Unfortunately there is no method of applying a default MQEndpoint to the whole broker or integration server. |
Sounds like an RFE candidate to me. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
zpat |
Posted: Thu Nov 10, 2016 7:48 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Also needs a way to ensure the administrator can enforce use of certain queue managers only.
Otherwise, sure as eggs are eggs, someone will promote a flow to production that accesses a development QM (or vice versa).
It would be my preference to have a configurable service per QM name, which defined the connection information and credentials to connect. If this CS was not present then the MQ connection would not be permitted. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
|