| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message going to Compute Failure Node.....Urgent |
« View previous topic :: View next topic » |
| Author |
Message
|
| msgbrkr |
 Posted: Wed Apr 21, 2004 9:34 pm Post subject: Message going to Compute Failure Node.....Urgent |
 |
|
Newbie
Joined: 21 Apr 2004
Posts: 9
|
Hi all,
I am quite new to WBIMB 5.0. I was developing a simple message flow, the input node gets a XMLNS message which is forwarded to the compute node which basically is generating a XML message to start a Workflow instance.
I have set the message domain for the input node to "XMLNS".
But when i put a message thru RFHUTIL into the input queue, the Compute node does not create the req XML msg, and sends the XMLNS msg as is to its Failure terminal.
I think the problem may be that it is considering the input msg to be BLOB.
The input msg is something like :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema".....................
<SOAP-ENV:Header>
<m:WFContext xmlns:m="http//........>
.......................................................
</m:WFContext>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
.........................................
......................................
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
****************************************************
The ESQL looks something like this:
SET OutputRoot.XML.WfMessage.WfMessageHeader.ResponseRequired = 'Yes';
SET OutputRoot.XML.WfMessage.ProcessTemplateCreateAndStartInstance.ProcTemplName='Justlikethat';
SET OutputRoot.XML.WfMessage.ProcessTemplateCreateAndStartInstance.ProcInstName='itsme';
SET OutputRoot.XML.WfMessage.ProcessTemplateCreateAndStartInstance.KeepName='TRUE';
SET OutputRoot.XML.WfMessage.ProcessTemplateCreateAndStartInstance.ExternalProcessContext='Mycontext';
*******************************************
Rgds,
HP |
|
| Back to top |
|
 |
| Neysa |
| Posted: Thu Apr 22, 2004 7:49 am Post subject: |
|
|
Newbie
Joined: 28 Nov 2002
Posts: 7
Location: Netherlands
|
Turn on tracing and read the tracefile to find out the errormessage.
Judging from the bit esql you posted, you ignore the incoming message and create a completely new message with some hardcoded text between the XML tags.
If ALL your esql looks like that the input message is purely used as trigger message.... |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Apr 23, 2004 4:50 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
You can also use Trace nodes to print ExceptionList, which will further explain why the messages failed.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
