Hello,I am new to Wire Tap and a novice on MQ technology.I have a stack of applications on different platforms (such as Siebel-CRM interfacing with a Clarify application, etc).. The interfaces between those applications are through MQ.I am looking into Wire Tap as tool to achieve following objectives, between say for e.g. application A and application B:1. To take a copy of the message in the MQ interface between A and B, and push it to a repository for future use AND allow the original message to go from A to B.2. Whenever required, to PUSH a message into this MQ so that it reaches the destination application B, without need for invoking the message from application A (basically stubbing application A)My question is - to achieve the above objectives, a) can Wire Tap do this without 'breaking' the MQ - meaning without changing the existing MQ interface/configuration ?b) OR, will it require re-designing the existing MQ to configure it for application A to interface to WireTap and in turn WireTap to interface with application B ?Thanks in advance.Paddy
-- View this message in context: http://camel.465427.n5.nabble.com/Wire-Tap-MQ-should-I-break-the-MQ-tp5741555.html Sent from the Camel - Users mailing list archive at Nabble.com.
