ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportAccessing payload for MQ input from failure terminal

Post new topicReply to topic
Accessing payload for MQ input from failure terminal View previous topic :: View next topic
Author Message
jineshpanchal
PostPosted: Mon Feb 12, 2018 2:38 am Post subject: Accessing payload for MQ input from failure terminal Reply with quote

Newbie

Joined: 12 Feb 2018
Posts: 1

Hi Guys,

I am new in IIB v10 and learning failure handling.

I have came across a situation where I need to persist the payload for all failure scenarios.

My flow is as below.

MQ input --> Failure terminal--> Compute (inserts data in table)

Properties set for MQ input node.

Queue Name : MQ_IN
Input Message Parsing : JSON : For Javascript Object Notification Messages
Parser Options : Parse timing : Immediate
Validation : Validate : Content and Value.

Rest all the properties are default.

The usecase is when an invalid input (Non-JSON content) is sent to flow, MQ input node sends the data to failure terminal. But When inputroot tree is expanded I am unable to see the payload which was sent to input node.

I need to access the payload. Need help how to access the same.

Currently JSON Child is empty.

eg. I send <Data>abc </Data> to above flow, it will navigate using failure terminal and the tree formed inside is
Code:
<Input>
    <Properties>
        <MessageSet></MessageSet>
        <MessageType></MessageType>
        <MessageFormat></MessageFormat>
        <Encoding>546</Encoding>
        <CodedCharSetId>1208</CodedCharSetId>
        <Transactional>TRUE</Transactional>
        <Persistence>FALSE</Persistence>
        <CreationTime>2018-02-12 09:45:15.970</CreationTime>
        <ExpirationTime>-1</ExpirationTime>
        <Priority>0</Priority>
        <ReplyIdentifier>000000000000000000000000000000000000000000000000</ReplyIdentifier>
        <ReplyProtocol>MQ</ReplyProtocol>
        <Topic></Topic>
        <ContentType></ContentType>
        <IdentitySourceType></IdentitySourceType>
        <IdentitySourceToken></IdentitySourceToken>
        <IdentitySourcePassword></IdentitySourcePassword>
        <IdentitySourceIssuedBy></IdentitySourceIssuedBy>
        <IdentityMappedType></IdentityMappedType>
        <IdentityMappedToken></IdentityMappedToken>
        <IdentityMappedPassword></IdentityMappedPassword>
        <IdentityMappedIssuedBy></IdentityMappedIssuedBy>
    </Properties>
    <MQMD>
        <SourceQueue>MQ_IN</SourceQueue>
        <Transactional>TRUE</Transactional>
        <Encoding>546</Encoding>
        <CodedCharSetId>1208</CodedCharSetId>
        <Format>MQSTR   </Format>
        <Version>2</Version>
        <Report>0</Report>
        <MsgType>8</MsgType>
        <Expiry>-1</Expiry>
        <Feedback>0</Feedback>
        <Priority>0</Priority>
        <Persistence>0</Persistence>
        <MsgId>414d51204d696e646372616674517565c9f67b5a20018202</MsgId>
        <CorrelId>000000000000000000000000000000000000000000000000</CorrelId>
        <BackoutCount>0</BackoutCount>
        <ReplyToQ></ReplyToQ>
        <ReplyToQMgr>MindcraftQueue                                  </ReplyToQMgr>
        <UserIdentifier>mindcraft   </UserIdentifier>
        <AccountingToken>1601051500000086e7e6709d746376621366b8f303000000000000000000000b</AccountingToken>
        <ApplIdentityData></ApplIdentityData>
        <PutApplType>11</PutApplType>
        <PutApplName>here MQ\bin64\MQExplorer.exe</PutApplName>
        <PutDate>2018-02-12</PutDate>
        <PutTime>09:45:15.970</PutTime>
        <ApplOriginData></ApplOriginData>
        <GroupId>000000000000000000000000000000000000000000000000</GroupId>
        <MsgSeqNumber>1</MsgSeqNumber>
        <Offset>0</Offset>
        <MsgFlags>0</MsgFlags>
        <OriginalLength>-1</OriginalLength>
    </MQMD>
    <JSON />
</Input>


But unable to see the <Data>abc </Data> in the InputRoot.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Feb 12, 2018 5:25 am Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19661
Location: LI,NY

The first thing you need to do on your failure branch is to reset the content descriptor and set it to BLOB. This will then give you the original bit stream.

Up to you what you then want to do with it.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportAccessing payload for MQ input from failure terminal
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.