| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FTE Co-ordination QMs |
« View previous topic :: View next topic » |
| Author |
Message
|
| burman.abhishek |
 Posted: Fri Dec 11, 2009 4:42 am Post subject: FTE Co-ordination QMs |
 |
|
Apprentice
Joined: 23 Aug 2006
Posts: 37
|
Can we have multiple instances of co-ordination manager in the same machine, even if we make them unaware of each other. In the sense, suppose we have two queue manager clusters, each cluster having its instance of coordination, agent and command queue manager, can they work independently if located in the same server. We have been able to install this configuration, and have also verified that both the agents are up and running, but are not able to see the separate setups within the mq explorer.
_________________
With warm Regards,
Burman |
|
| Back to top |
|
 |
| PeteVerdon |
| Posted: Tue Dec 15, 2009 7:01 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
It's possible to have multiple coordination queue managers, but not to directly interoperate between them. (Interoperation isn't explicitly prevented, but is not supported.) Each coordination queue manager and its agents is considered an FTE "network", also known in some places as a "configuration set". If a command line tools install is configured to enable access to multiple networks, the -p option is used to select the one required; there is a default if -p is not used.
For the GUI, if the configuration files are correctly laid out on the local disk you should see the different coordination queue managers in the tree in the left-hand pane. You can only be connected to one coordination queue manager at a time; the others will be grey. To connect to a coordination queue manager (which will implicitly disconnect from the current one if applicable) you right-click on it and select "Connect".
The appropriate directory structure for this is as follows (example names, Unix filesystem conventions):
| Code: |
/var/IBM/WMQFTE/
`-- config/ Single config directory
|-- NET_1/ First coordination QM
| |-- NET_1.mqsc
| |-- agents/
| | |-- AGENT_1A/ First agent on NET_1 network
| | | |-- AGENT_1A_create.mqsc
| | | |-- AGENT_1A_delete.mqsc
| | | |-- UserSandboxes.xml
| | | |-- agent.properties
| | | `-- exits/
| | `-- AGENT_1B/
| | |-- AGENT_1B_create.mqsc
| | |-- AGENT_1B_delete.mqsc
| | |-- UserSandboxes.xml
| | |-- agent.properties
| | `-- exits/
| |-- command.properties Properties files for first coord QM
| `-- coordination.properties
|-- NET_2/ Second coordination QM
| |-- NET_2.mqsc
| |-- agents/
| | |-- AGENT_2A/
| | | |-- AGENT_2A_create.mqsc
| | | |-- AGENT_2A_delete.mqsc
| | | |-- UserSandboxes.xml
| | | |-- agent.properties
| | | `-- exits/
| | `-- AGENT_2B/
| | |-- AGENT_2B_create.mqsc
| | |-- AGENT_2B_delete.mqsc
| | |-- UserSandboxes.xml
| | |-- agent.properties
| | `-- exits/
| |-- command.properties Properties for second coord QM/network
| `-- coordination.properties
`-- wmqfte.properties Properties file common to both nets.
|
This can be generated by running the fteSetupCoordination, fteSetupCommands and fteCreateAgent commands with appropriate options. The wmqfte.properties indicates which of the two nets is the default when the -p option is not used.
If your configuration on the machine on which the Explorer is run looks something like this, you should see both coordination QMs and be able to switch between them.
I hope this helps; if not please come back with a bit more information about how your FTE networks are configured.
Pete |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Dec 15, 2009 9:06 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Pete,
I hope I'm not diverting the topic...
If my agent1 belongs to CM1 and Agent2 to CM2...and I do a file transfer from Agent1 to Agent2...which CM will provide me information about the transfer ? and will it be the entire info or only about send/receive ?
Regards. |
|
| Back to top |
|
|
| PeteVerdon |
| Posted: Wed Dec 23, 2009 4:52 am Post subject: |
|
|
Apprentice
Joined: 11 Feb 2009
Posts: 33
Location: Hursley, UK
|
Transferring between agents that report to different coordination queue managers is not a supported configuration.
In practice, it's the source agent that sends information about the transfer, to its own coordination queue manager. |
|
| Back to top |
|
|
| angka |
| Posted: Fri Aug 13, 2010 1:15 am Post subject: |
|
|
Chevalier
Joined: 20 Sep 2005
Posts: 406
|
Hi PeteVerdon,
from the gettingstartedwmqfte redbook chapter 2 fig 2.7, it shows that transferring btw agents tt report to different CQM is possible. Am i missing something?
Thanks. |
|
| Back to top |
|
|
| mphillip |
| Posted: Mon Aug 16, 2010 3:47 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2009
Posts: 49
|
This sort of topology will currently work, but only the source agent is going to log information to it's coordination queue manager. The destination agent will currently report nothing. If you care about the log messages and knowing what is going on with transfers in your FTE network, then it is probably not a good idea to allow this.
For example if you have "accounts" and "warehouse" FTE networks (with their own coordination queue managers), would you want "warehouse" to send a file to "accounts" that accounts gets no notification or log messages about?
As for whether you are missing something, I think the thing I would point out is that the Redbooks are not necessarily a statement of support for IBM products. They can contain inaccuracies and just because it's in a Redbook doesn't make it correct or sensible. A comment to this effect is mentioned at the start of every Redbook. |
|
| 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
|
|
|
|
