| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| New Queue managers needed? |
« View previous topic :: View next topic » |
| Author |
Message
|
| kevinf2349 |
 Posted: Tue Mar 21, 2006 8:11 am Post subject: New Queue managers needed? |
 |
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Hello
I have just taken over support for Workflow and I have been asked to setup 2 new workflow 'environments'. Now I understand from the developers that the 'environment' in question are going to be Windows Client based, and they will communicate with z/OS thru Java on the mainframe. So the question I have is this...having read some (be no means all) of the 'Customization and Administration' guide for z/OS I am unclear if I need to have a new queue manager defined on z/OS or not.
If I do, do we also need a queue manager on the Windows end (for clustering)?
The developers want to try and isolate the different workflow 'systems' from each other and have requested seperate WAS and FMC address spaces for these two new applications. Is this feasable/reasonable ?
They have a new Windows box already defined but no MQ on it, just the workflow client.
Thoughts anyone? |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Mar 21, 2006 8:36 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I have not done z/OS workflow, but I am pretty sure you won't need another qmgr just for workflow.
For the workflow client, either you can use an MQClient or MQServer. It is upto you to decide which one to use. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Mar 21, 2006 8:27 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Vennela
Maybe I didn't explain myself. We already share QMrs with non-workflow applications. The issue is that they now want two more workflow applications and want to run them in seperated environments within the same LPAR. Seperate FMC address spaces, seperate WAS address spaces etc. I believe I am going to need seperate Queue managers in order to do this but I am not 100% sure.  |
|
| Back to top |
|
|
| hos |
| Posted: Wed Mar 22, 2006 3:48 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
you are not very specific and you are not using MQWF terminology.
Here is what I assume that you have and want you want to achieve:
1. You have MQWF 3.6 and you are using JACA to configure your web application.
2. In a single LPAR you have
- one WAS1 running in its own address space
- one MQWF1 installation/configuration that is represented by a System
Group (which you call environment)
- one queue manager QMGR1 that connects applications (clients) running
on WAS1 to MQWF1 servers
3. you want to add
- additional WAS2 running in its own address space
- additional MQWF2 system group
- additional applications (clients) running on WAS2 and connecting to
MQWF2
4. Your question is whether you need an additional QMGR2 to connect
WAS2 with MQWF2
The answer is: no, you can use QMGR1 in your configuration FMC2 to connect WAS2 with MQWF2.
Are my assumptions correct and does this help? |
|
| 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
|
|
|
|
