Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 18880 invoked from network); 24 Sep 2008 11:42:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Sep 2008 11:42:32 -0000 Received: (qmail 86707 invoked by uid 500); 24 Sep 2008 11:42:29 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 86688 invoked by uid 500); 24 Sep 2008 11:42:29 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 86677 invoked by uid 99); 24 Sep 2008 11:42:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 04:42:29 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [195.69.129.177] (HELO exsmtp01.exserver.dk) (195.69.129.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 11:41:27 +0000 Received: from EXVS04.exserver.dk ([10.10.10.84]) by exsmtp01.exserver.dk with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Sep 2008 13:39:36 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Bridging the ActiveMQ with IBM Websphere using Camel Date: Wed, 24 Sep 2008 13:41:50 +0200 Message-ID: <4C1FB9C00D24A140906239533638C4D205716433@EXVS04.exserver.dk> In-Reply-To: <19646763.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bridging the ActiveMQ with IBM Websphere using Camel Thread-Index: AckeOBj3De+ss+WGSwWdvE32Z7AqkgAAQccA From: "Claus Ibsen" To: X-OriginalArrivalTime: 24 Sep 2008 11:39:36.0049 (UTC) FILETIME=[386EC610:01C91E3A] X-Virus-Checked: Checked by ClamAV on apache.org Hi Can you use Hermes to browse the MQ queues? Maybe the MQ queue browser = is showing it as a raw kinda format. I am not familiar with the MQ = console. At my current client we have with success setup Hermes to browse our MQ = broker. I think you need some Java code in between your routing to be able to = set the IBM specific headers and other stuff that you need in your case = to send it to your MQ. So the route: from(activemq:queue.in).to(ibmmq:queue///queue.out) Must be expanded with a processor to do the java coding needed. You can do this route to let you be in control what is sent to MQ from(activemq:queue.in).process(new Processor()) { public void process(Exchange exchange) { // TODO: Insert java code here exchange.getIn().setBody("Hello World"); exchange.getIn().setHeaders(Collections.EMPTY_MAP); };).to(ibmmq:queue///queue.out) You can also remove the .to(ibmmq:queue///queue.out) in the route and = send it manually from the processor in java code. Here you can send it = using spring-jms, so you can avoid whatever Camel interferes with. Bottom line: I will try to get some plain java code working that can = send a message to MQ. And then later use that code in Camel. If you ping my en email at: davsclaus@apache.org then I will be able to = send you some sample java code that we use for sending message to MQ = using spring-jms. Albeit we don't use this in production, we are using = it for proof-of-concept. The same code can be used in Camel, just in the processor or as a spring = bean etc. =20 Med venlig hilsen =20 Claus Ibsen ...................................... Silverbullet Skovsg=E5rdsv=E6nget 21 8362 H=F8rning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: JavaRat [mailto:fredrik.sassenberg@mindwell.se]=20 Sent: 24. september 2008 13:26 To: camel-user@activemq.apache.org Subject: RE: Bridging the ActiveMQ with IBM Websphere using Camel Hi Claus, many thanks for your ideas and suggestions so far! We have tested the above tips you had. Both on their own and together without any effect we can see on the message which ends up on our final queue destination. Browsing the message we get on the IBM MQ queue we = get the following: XQH .... CAMELoutputchannel queue.out CT ....................=FF=FF=FF=FF.... ....R...MQHRF2 .............AMQ Qmgr < jms_text ...Xqueue:///queue.out 1222311223456 2 ...... 1 MQSTR my chocolatechip cookie recipie Without getting into MQ details it looks very much as we have a = JMSMessage around the TextMessage which we are intending to put onto the queue. = (Clues too why we think so is we see a MQHRF2 and a RFH part.) Also we see the MQSTR and jms_text beeing recognized. =20 Our current guess (and let us assume this is the case) is that we are = not "peeling" off the camelWrapper Message before putting it onto the IBM MQ queue.=20 How can we avoid sending our textMessage inside this = camelWrapperMessage? Have we made a misstake thinking we can use the following configuration inside the camel-context.xml? We refer to this bean when we use the from(activemq:queue.in).to(ibmmq:queue///queue.out) =20 =20 =20 --=20 View this message in context: = http://www.nabble.com/Bridging-the-ActiveMQ-with-IBM-Websphere-using-Came= l-tp19623329s22882p19646763.html Sent from the Camel - Users mailing list archive at Nabble.com.