Author |
Message
|
EricCox |
Posted: Wed May 25, 2016 11:05 am Post subject: IIB10 Define Local Queue Manager not hard code in MQ Nodes |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
To all,
Is there a way to define a local queue manager to IIB 10 and not have to hard code Queue Manager names in the MQInputNode? We have multiple Queue Managers in production and don't hard code QM names into Flows.
Can we do the same thing in IIB 10?
I want to define a local QM to the IIB installation and then leave the Queue Manager property empty on the nodes so it picks up the local QM the way it worked in WMB 8.0.0.x.
How do I define the local Queue Manager so I get the same behavior as WMB 8? Is there a doc to help?
Thanks,
EMC |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 25, 2016 11:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 11:19 am Post subject: TYVM |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 11:32 am Post subject: mqsichangeproperties |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
It's not clear in the documents if I can use mqsichangeproperties to set the QM after creating the node.
Is it possible to assign the QM after the node is created?
Unfortunately I don't have a local QM to exercise the commands. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 25, 2016 11:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 11:48 am Post subject: OK, now |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
Can we define a remote queue manager to an IIB Node? mqsichangebroker doc doesn't quite talk about that.
LOL. I'm on my laptop but without a QM.
Our delivery team does all this set up. I'm not familiar with all the command line stuff.
I appreciate your patience. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 25, 2016 11:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I don't think v10 supports a remote queue manager.
If it did, it would be in the docs on the createbroker/changebroker commands. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 11:55 am Post subject: It does |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
I think it does but you end up having to hard code stuff on the nodes....yuk. |
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 11:57 am Post subject: |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 25, 2016 12:06 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Quote: |
If you select the local queue manager option, you must specify a queue manager name. |
So no matter what, you end up having to specify a qmgr name.
With a CCDT, however, you should be able to specify a *.
Regardless, you should be able to use mqsiapplybaroverride to change the values in the bar files before deploying to newer environments.
http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an19545_.htm _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
EricCox |
Posted: Wed May 25, 2016 12:11 pm Post subject: Hope Not |
|
|
Master
Joined: 08 Apr 2011 Posts: 292
|
If that is true we will have to deploy hundreds and hundreds of bar overrides to configure QM's in all of our environments for hundreds of services. What a nightmare. I hope that isn't true. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 25, 2016 12:20 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Or "why everyone scripts things". _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
stoney |
Posted: Wed May 25, 2016 1:30 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2013 Posts: 140
|
EricCox wrote: |
http://www.ibm.com/developerworks/websphere/library/techarticles/1602_movva-trs/1602_Movva.html |
Have you looked at MQ policy which is not mentioned at all by this article?
You can specify an MQ policy URL on the MQ nodes at development time or via BAR file overrides.
In the toolkit, the property is on the Policy tab of the properties of all of the MQ nodes.
For example, I might set an MQ policy URL of "/apiv1/policy/MQEndpoint/WarehouseQM" on all my MQ nodes.
You (as a developer) can then define an MQ policy in the toolkit, web UI, or via command line to point at a local or remote queue manager depending on your environment.
The MQ policy you create just needs to have the right name - WarehouseQM in this case.
The MQ policy gives you the ability to define all of the connection settings for local, client, or CCDT based connections to MQ queue managers.
Your administrators can then define an MQ policy with the same name, except they point their policy at the queue manager for the correct environment.
They can even change the MQ policy whilst the system is running, and all MQ nodes that have that MQ policy attached will be automatically reconfigured with the changes.
Here's a link to the starting docs for operational policy:
https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bi62000_.htm |
|
Back to top |
|
 |
|