on 06-08-2009 2:40 PM
Hello Experts,
I have a specific business requirement for one of my interfaces.
It looks like: 3rd party -
> WMQ -
>PI
Example: 3rd party sends 3 (Header, detail and Trailer) messages WMQ and MQ processes these 3 messages one by one through specific Queue.
TO be approach: We have to ignore Header and Trailer messages before processing through Integration Engine as it does not contain any business data, we should only process the Detail message to the receiver.
Message 1 Header:
<FIData>
<detail>
<HeaderReference/>
<PostingItem>
<ProfitCentre/>
<CostCentre/>
<RunDate>TOTAL NUMBER OF RECORDS SENT 4</RunDate>
<Description/>
<Assignment/>
<CalculateTaxBase/>
</PostingItem>
</detail>
<FIData>
Message 1 Detail:
<FIData>
<detail>
<HeaderReference>483061</HeaderReference>
<PostingItem>
<ProfitCentre>AU21</ProfitCentre>
<CostCentre/>
<RunDate>20090512</RunDate>
<Description>9587531|57372.000|41348.00|.00</Description>
<Assignment/>
<CalculateTaxBase/>
</PostingItem>
</detail>
<FIData>
Message 1 Trailer:
<FIData>
<detail>
<HeaderReference/>
<PostingItem>
<ProfitCentre/>
<CostCentre/>
<RunDate>COCS</RunDate>
<Description/>
<Assignment/>
<CalculateTaxBase/>
</PostingItem>
</detail>
<FIData>
Note: Structures of 3 messages is same, and remember these 3 are individual messages and the runDate values in header and trailer messages will not have any impact on business.
Valuable inputs are much appreciated!!
Receiver is same(only one).
Regards,
Raj
You can use message selector feature of JMS adapter: The adpater only pick up certain messages that has particular value of a attribute.
You have to work with your MQ consultant, when publish the publish the message into the queue, they can set the value of attribute.
Please refer my wiki:
Usage of Message Selector for JMS Sender Adapter
Regards.
Liang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
module helped
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey
The best option would be to ignore this in receiver determination.
Just give a condition there to drop any message which is either Header or Trailer.
Thanks
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The easy way is create a module in the adapter level restrict the header and trailer messages.
One more solution is create a xslt mapping and use the mapping in adapter level.
[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3823] [original link is broken] [original link is broken] [original link is broken];
Regards,
Prakasu.M
Dude... i didnt follow ur question...
Looks like all you have to do is ignore the header and the triler in ur mapping...unless...I am missing somethinbg else... U pls be more specific as to the issue u are facing??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.