| Author |
Message
|
| wbimb |
 Posted: Mon Aug 28, 2006 4:57 am Post subject: |
 |
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
| jefflowrey wrote: |
| If you don't know where to look for errors, then you shouldn't be trying to configure an Exit. |
Ya i know i should know where to look for it...but since i dont can u please tell me where should i look for it
thanks in advance |
|
| Back to top |
|
 |
| monkey |
| Posted: Tue Aug 29, 2006 7:51 am Post subject: |
|
|
Novice
Joined: 15 Feb 2006
Posts: 24
Location: London
|
| wbimb wrote: |
Ya i know i should know where to look for it...but since i dont can u please tell me where should i look for it
|
Try looking for the errors directories under your MQ install path.
There should be some log files in there, look at the latest one and then look again after you send a test message.
Can you paste your mq.ini file in here so we can see if you've configured it correctly?
It would also be useful if you paste in the config of your namelist
Sorry for the delayed response, new contract = limited net access!
Cheers,
Monkey |
|
| Back to top |
|
|
| wbimb |
| Posted: Tue Aug 29, 2006 7:57 am Post subject: |
|
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
| I am working under windows environment |
|
| Back to top |
|
|
| monkey |
| Posted: Thu Aug 31, 2006 7:00 am Post subject: |
|
|
Novice
Joined: 15 Feb 2006
Posts: 24
Location: London
|
| wbimb wrote: |
| I am working under windows environment |
Look in the registry, tell us how you've configured the mirrorq exit.
Aside from that, did you do the test I suggested? and what messages did you get in the log? |
|
| Back to top |
|
|
| monkey |
| Posted: Thu Aug 31, 2006 7:03 am Post subject: |
|
|
Novice
Joined: 15 Feb 2006
Posts: 24
Location: London
|
the path to your logs will be:
MQInstallPath\WebSphere MQ\Qmgrs\QueueManagerName\errors\AMQERR01.log
or something similar |
|
| Back to top |
|
|
| MQAdminMax |
| Posted: Tue Feb 13, 2007 7:43 am Post subject: mirrorq setup on Windows MQ Version 6 Refresh Pack 1 |
|
|
Newbie
Joined: 12 Feb 2007
Posts: 4
Location: Georgia
|
1. Copy "mirrorq.dll" into C:\Program Files\IBM\WebSphere MQ\exits
2. A total of 4 Local Qs need to be created
a) "mirrorq" Queue Local created with default properties
b) "sourceq" Queue Local created with default properties
c) "stageq" Queue Local created with default properties and Triggering setup - This is the staging Q
DEFINE QLOCAL('stageq') REPLACE +
DESCR('Staging queue for mirrorq') +
SHARE +
TRIGGER +
TRIGTYPE (EVERY) +
INITQ('MIRRORQ.TRIGGER') +
PROCESS('MIRRORQ.PROCESS')
d) "MIRRORQ.TRIGGER" Queue Local created with default properties - This is the Initiation Q
DEFINE QLOCAL('MIRRORQ.TRIGGER') REPLACE +
DESCR('Initiation queue') +
3. Create process defintion to load mirrorq.exe
DEFINE PROCESS('MIRRORQ.PROCESS') REPLACE +
DESCR('Trigger Process for mirrorq') +
USERDATA('sourceq mirrorq') +
APPLICID('mirrorq')
4. Create a NAMELIST called "mirrorq" with names (in the order shown)
sourceq mirrorq QMGR_NM
where QMGR_NM is the actual name of your Queue Manager
5. Setup QMGR exit (right click on QMGR with MQExplorer and choose properties then go to exits)
Setup the exit as follows:
name set to "mirrorq" (Don't enter quotes)
Function set to "EntryPoint" (Don't enter quotes)
Module set to "C:\Program Files\IBM\WebSphere MQ\exits\mirrorq.dll" (Don't enter quotes)
6. Restart Queue Manager for changes to take effect
7. Start Trigger Monitor from command line
"start runmqtrm -m QMGR_NM -q MIRRORQ.TRIGGER" (Don't enter quotes). Where QMGR_NM is the actual name of your Queue Manager.
A new window should be opened with a line at the bottom that states "Waiting for a trigger message".
8. Within the Queues view of MQExplorer right click on the Queue "stageq"
and choose "Put Test Message...."
The Message should be written to "sourceq" and a copy of the same message placed onto "mirrorq"
9. To stop Trigger Monitor - "CTRL-C" on DOS Prompt Command Window
Additional:
Applications should read data from "sourceq"
A staging queue is used to ensure mirroring of all messages. If a staging Q was not used an application could end up pulling the data before the mirrorq application even had a chance to mirror the MSGs.
_________________
"Act Powerfully - Success in life comes not from holding a good hand, but in playing a poor hand well" - Warren G. Lester |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Feb 13, 2007 7:48 am Post subject: Re: mirrorq setup on Windows MQ Version 6 Refresh Pack 1 |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| MQAdminMax wrote: |
| A staging queue is used to ensure mirroring of all messages. If a staging Q was not used an application could end up pulling the data before the mirrorq application even had a chance to mirror the MSGs. |
No.
API exits run simulatenously with the API calls. That means that a message can [i]not[/] be PUT on a queue without the API exit for PUT being invoked, which means that MirrorQ will mirror the message.
Please remember that mirrorq is SAMPLE code, always has been, is completely unsupported, and is not suitable for production use because of both of those.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 16, 2007 3:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| There two versions of MirrorQ, the staging version (a triggered program) and the API exit version. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 16, 2007 6:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Sure.
But MQAdminMax talked about deploying the Exit version as if it were the Trigger Version.
And both of them are unsupported, and sample code.
And I think the Trigger version is older than the API version.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MQAdminMax |
| Posted: Fri Feb 16, 2007 2:18 pm Post subject: Can someone detail out the steps for mirrorq setup (windows) |
|
|
Newbie
Joined: 12 Feb 2007
Posts: 4
Location: Georgia
|
Ok. API exit version versus triggering version? All I know is that the thing works as I have detailed out in my previous post. Without starting the trigger monitor no mirroring of messages takes place.
If you have the exact steps (with similar details as in my previous post) for each or either of the setups for the API exit version and/or the trigger version please feel free to share (as long as you have proven that it works (on Windows Platform). I am not an expert on this, but I posted what I posted because it works all based on my trial and error experience because I have not found anything with detailed steps like I had posted previously. All I can find is "this doesn't work", "do this", "do that", "that won't work". What we need is detailed clear-cut steps as to what works with no holes so that one is left in the dark to pick up the pieces by guesswork. Thanks!
_________________
"Act Powerfully - Success in life comes not from holding a good hand, but in playing a poor hand well" - Warren G. Lester |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 16, 2007 5:35 pm Post subject: Re: Can someone detail out the steps for mirrorq setup (wind |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| MQAdminMax wrote: |
| What we need is detailed clear-cut steps as to what works with no holes so that one is left in the dark to pick up the pieces by guesswork. Thanks! |
And if it were a supported solution, rather than something you were supposed to only implement after carefully examining, making sure you fully understood, and then modifying where necessary to make sure it met your needs...
I'm sure IBM would give you that.
As a sample, though...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 17, 2007 7:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did anybody think to suggest pub/sub to max?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MQAdminMax |
| Posted: Mon Feb 19, 2007 1:39 pm Post subject: Show and Tell |
|
|
Newbie
Joined: 12 Feb 2007
Posts: 4
Location: Georgia
|
Okay, let's pretend this is show and tell. If you know how this mirrorq works then demonstrate. All this talk and no show is a waste of time. If you know how to walk the talk, prove it.
_________________
"Act Powerfully - Success in life comes not from holding a good hand, but in playing a poor hand well" - Warren G. Lester |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 20, 2007 12:45 am Post subject: Re: Show and Tell |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQAdminMax wrote: |
| If you know how this mirrorq works then demonstrate. All this talk and no show is a waste of time. |
The point (as jefflowrey made) is that mirrorq as supplied is a sample and should be used as a starting point for your own development. Certainly you need to be happy (through your own development work and testing) that you're happy with what it's doing, you understand what's going on and it's production ready for your site. It's not a question of walking, running or dancing the talk, it's that we can't develop a solution for your requirements. All we can do is point the way and offer advice.
(Well yes, we can develop solutions, but that normally requires a billable invoice.....  )
Have you given thought to the solution fjb_saper proposed? Pub/sub? Depends a lot on your application architecture but would avoid all this exit business! And there's nothing sample about that, it's fully supported and you can set IBM on it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQAdminMax |
| Posted: Tue Feb 20, 2007 1:24 pm Post subject: Proved that the API Exit works on MQ 6.0 for Windows |
|
|
Newbie
Joined: 12 Feb 2007
Posts: 4
Location: Georgia
|
Thanks for all the inputs. The API Exit works as is for MQ 6.0 on Windows.
I had failed to enter the namelist name as outlined in step 3 when configuring the API exit.
The API exit works and does accomplish the Mirroring. No development needed.
/*****************************************************************************/
/* */
/* (c) Copyright IBM Corp. 2004,2005 All rights reserved. */
/* */
/* This sample program is owned by International Business Machines */
/* Corporation or one of its subsidiaries ("IBM") and is copyrighted */
/* and licensed, not sold. */
/* */
/* You may copy, modify, and distribute this sample program in any */
/* form without payment to IBM, for any purpose including developing, */
/* using, marketing or distributing programs that include or are */
/* derivative works of the sample program. */
/* */
/* The sample program is provided to you on an "AS IS" basis, without */
/* warranty of any kind. IBM HEREBY EXPRESSLY DISCLAIMS ALL WARRANTIES, */
/* EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED */
/* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. */
/* Some jurisdictions do not allow for the exclusion or limitation of */
/* implied warranties, so the above limitations or exclusions may not */
/* apply to you. IBM shall not be liable for any damages you suffer as */
/* a result of using, modifying or distributing the sample program or */
/* its derivatives. */
/* */
/*****************************************************************************/
/* */
/* Program name: mirrorq */
/* */
/* Description: This sample demonstates how an API Exit may be used */
/* to put a copy of a message to a second Queue without */
/* the need to alter the original application. */
/* */
/* Function: This exit opens a Namelist object that contains a list of */
/* source Queues with the respective target Queues and Queue */
/* Managers. If a message is put to the source Queue, this */
/* exit puts a mirror image of the message to the target */
/* Queue. */
/* */
/* Prereqs: This sample program requires WebSphere MQSeries 5.3 */
/* */
/* */
/* Setup: 1. Copy mirrorq.dll to C:\Program Files\IBM\Websphere MQ\exits */
/*
/* */
/* 2. Create a Namelist */
/* From the MQExplorer click on the + sign next to the */
/* Queue Manager name. */
/* Click on the + sign next to the Advanced tab to expand */
/* the list. */
/* Right click on Namelist and select New and Namelist. */
/* Enter a name, for example mirrorq. */
/* NOTE: Although a name up to 48 characters is allowed, */
/* only 32 characters is allowed to configure this name */
/* in the exitdata field so restrict the name to 32 */
/* characters. */
/* In the names field, enter the source Queue to be */
/* copied, followed by the target Queue to copy messages */
/* to followed by the Queue Manager name of the target */
/* Queue. The Queue Manager name is required even if it */
/* is the local Queue Manager. If there is a second Queue */
/* to be mirrored, then enter the next source queue, target */
/* Queue, target Queue Manager. For example: */
/* TEST_IN,TEST_IN_COPY,VENUS.QMGR,TEST_OUT, */
/* TEST_OUT_COPY,PLUTO.QMGR */
/* Click OK to save the new Namelist. */
/* */
/* 3. Configue the API EXIT */
/* From the MQExplorer right click on the Queue manager */
/* name. */
/* Click properties and select Exits tab */
/* Click on the Add button. */
/* Enter a name for the API Exit such as MirrorQ. */
/* Enter EntryPoint in the Function field. */
/* Enter the full path to mirrorq.dll in the Module field */
/* for example: c:\MQSeries\exits\mirrorq.dll or */
/* click the Browse button to locate mirrorq.dll. */
/* Click the window next to Data to enable the data field */
/* and enter the name of the Namelist created in step 2. */
/* If you have other API Exits configured, select a */
/* Sequence Number for this exit that is higher if you */
/* want it called following the other exit(s) or lower if */
/* you want it call prior to the other exit(s). Otherwise, */
/* leave the default Sequence Number. */
/* Click OK to save the exit definition and OK to exit */
/* the Queue Manager properties. */
/* */
/* */
/* 4. Stop / Start the Queue Manager */
/* To activitate the API Exit, stop and restart the */
/* Queue Manager. */
/* */
/* */
/* 5. Test the API Exit */
/* From MQSeries Explorer, click the + next to the Queue */
/* Manager and click Queues. */
/* Right click on one of the Queues to be mirrored and */
/* click on Put Test Message. */
/* Enter a string of text. */
/* Click OK to put the message. */
/* Double click on the Target Queue name to open it. */
/* You should see the text string you entered. If not, */
/* double check the configuration steps above and the */
/* MQ log error log files.
_________________
"Act Powerfully - Success in life comes not from holding a good hand, but in playing a poor hand well" - Warren G. Lester |
|
| Back to top |
|
|
|
|
