| Author |
Message
|
| jmac |
 Posted: Sat Jan 24, 2004 10:57 am Post subject: Using an existing Queue Manager |
 |
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I have a situation where it is desireable to use an existing queue manager (not created by MQWF). I am interested in any experiences anyone has had with similar situations. Looking over some of the old posts, I get kind of a mixed message. It appears that some have done this successfully, but I see in one case someone indicated that IBM will not support such a system. I will admit to not having gone over the V3.4 Install guide closely yet, but I plan on doing so. I am just looking for any experiences that you can share.
Thanks
_________________
John McDonald
RETIRED |
|
| Back to top |
|
 |
| leongor |
| Posted: Sun Jan 25, 2004 1:54 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
I have tried once to use my own queue manager for WF, but with no success.
AFAIK, WF uses internal pointers to its queues, so if you even delete some WF queue by yourself
you cannot recreate it manually, but only with fmczutil.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| karthik |
| Posted: Mon Jan 26, 2004 9:59 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi
we have done Wf install using an already existing QMGR.
The way we have done it was to save the existing QMGR objects , delete the existing QMGR .
Later allow workflow to create the QMGR with its previous name and then incorporate the saved QMGR objects back into this QMGR. Thus there is no loss of anything and WF can create its own queues and definitions without any conflicts.
Karthik |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 26, 2004 11:09 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Karthik, Does it not mean that you havent used an existing QM?
_________________
-Ratan |
|
| Back to top |
|
|
| karthik |
| Posted: Mon Jan 26, 2004 11:16 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi ratan,
I was explaining how i was able use an existing QMGR for WF.
Because i know that WF does not create the queues and the authorisations when we point the configuration utility to use an already existing QMGR.
Therefore the workaround thought for this was to bring down the QMGR , let workflow create all the required objects in the QMGR and then incorporate the previous Saved Objects into the QMGR.
That was what we have done, and since john's question seemed pretty close what we did , i thought i would share my experience.
Thanks
karthik |
|
| Back to top |
|
|
| clindsey |
| Posted: Mon Jan 26, 2004 11:23 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
John, I saw your note.
I have not tried this so no personal experience to share, but I see no reason why it would not work. The key is to get all the required objects created and to get the queue manager joined in the cluster.
Workflow dynamically creates the mq scripts used to define the mq objects and then users normal mq facilities to create the objects. You would have to clone these script files from an existing configuration. Then modify to change all the object names that are derived from the group and system name.
Look at an existing system in /var/fmc/qmgrs/<qmgrname>/mqs or the equivalent dir on a windows system. You will see the mq script files that were used to generate this queue manager. Move these to your new system and modify. I think you can look for all instances of the group name and see what needs to be changed. For example, if the group name is FMCGRP, grep or find all occurences of FMCGRP in these files and this will show in each file where the group name exists. This will be all the entries for queue definitions, aliases, cluster details, processes, etc.
After making the changes, run each of the files through 'runmqsc'. Assume the new qm name is JMAC, enter 'runmqsc JMAC < fn.mqs' where fn.mqs would be all the mqs files in the directory.
Hope this helps,
Charlie |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 30, 2004 1:02 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Looks like you can use an existing queue manager for a workflow configuration. But there are a few things that you need to look out for.
Though you specify the option to use the existing queue manager, workflow will add it's own objects.
The implications are:
1. If the QMGR is already in a cluster and is a repository for one or more clusters, the config utility will overwrite this. You can manually alter this change. After the config utility is done, you can create a namelist and add the already existing clusters and the new workflow cluster in the namelist. Use this namelist in the REPOSNL.
2. If for some reason you are deleting the configuration and you do not want to delete the queue manager but remove it from cluster, then workflow config utility will not be able to remove the QMGR from the cluster in a clean way while deleting the configuration.
3. In the directory var/fmc/qmgrs/<qmgrname>/mqs that charlie mentioned, there are .mqs files built, but you will have to identify when to use what files. For example, some files are used when creating the workflow configuration and some files are used while deleting the workflow configuration and removing the QMGR from the cluster without deleting it.
4.(1) and (2) are aslo true for the CLUSSDR and CLUSRCVR channels.
5. If you specify a port that is not the port the current QMGR listener is running on then a new listener will be created.
If this is what has to be done then you will have to save off all the objects and authorities (support pacs are available to do this) and then do this. |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jan 30, 2004 1:08 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Thanks to all, especially Charlie and Vennala
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
