JMS sender with MessageTransformBean and xml.additionalLastFields

[JaySchwendemann]

Hi all,

I have a JMS sender adapter (generic JMS) which I use for this scenario

MQ (JMS) --> PI (7.4 AEX) --> ERP (IDoc)

I am following this page for setting up content conversion for the adapter:

Adapter Engine (Java SE) - SAP Library

If i specify the following parameters...

xml.missingLastFields = Error
xml.additionalLastFields = Error

... the channel goes to error state when it tries to process a shorter / longer message then the configured one.

This of course is expected / wanted behavior. What is not wanted is that the channel does not pick up the message from the JMS queue and then putting it on error state within PI. Instead the message stays in the queue and the channel tries to pick up the message every second or so.

So my question is:

Is there any way to have the channel pick up the message from the queue, then fail on PI and put the message in (system) error state?

(I already tried Transform.PermanentErrors = true but no luck, maybe this only applies to file adapter?)

Thanks and kind regards

Jens

[Harish · Accepted solution]

Hi Jens,

AFAIK - there is no standard way in adapter engine to perform this. But you can pick the message a throw the error in transformation step (using mapping).

regards,

Harish

[JaySchwendemann · Accepted solution]

As there seems no other opinion on whehter it is possible to have PI pick up the message and then fail within PI I'm marking this thread answered.

Cheers

Jens