Hi, Just a thought, could you check the message type and then use a destination list to assign the output queue you want to route to?
We were using an external Oracle Database to store replyto information in one of our WMQI flows. We recently migrated away from the database for a couple of reasons. One was when the database was backed up every night. WMQI could not reconnect gracefully and was failing on the first message each day. I actually implemented an error routine to check for this connect error and to retry the message which worked fine. However, due to high availability issues we decided to move to using the MQGET support Pac. This way we didn't have to worry about database backups and availability and the storage place for our information was under our control not the DBA's. So far this has worked out ok for us. Time had nothing to do with our changes though. Storing to a queue instead of a database had very little impact on our end to end times and our project is sensitive down to the milliseconds. Karen -----Original Message----- From: Kieran Brennan [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 4:13 PM To: [EMAIL PROTECTED] Subject: Routing Table in WMQI Hi, I am looking into the development of a routing message flow in WMQI 2.1, allowing WMQI to work as a hub. Each queue manager will have a channel defined to/from the WMQI qm, and a unique identifier will identifier carried in the MsgType will define the routing required for each particular type of message. Essentially it will work as follows in WMQI: MQinput Node receives a message Using the MsgType from the MQMD it looks up a database table to find out the name of the destination queue and qm. Then in an output node puts the message on this queue. I am concerned that this will be too slow, and the look-up against the database each time will be too slow. There will be up to one million messages a day passing through, and peak times will exist. I am considering using the PostIT node to store the routing table in shared memory initially in a separate flow, and then using postiit nodes to look up the relevant information in the message flow detailed above instead of using the database. Has anyone implemented a similar design before? What issues should I look out for? Thanks Kieran **************************************************************** The information transmitted in this email is intended for the addressee only and may contain confidential and/or privileged material. Any review, retransmission,dissemination,reliance upon or other use of, this information by persons or entities other than the addressee is prohibited.If you received this in error, please contact the sender and delete the material. This message has been swept by Anti-Virus software **************************************************************** Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
