Dear all,
our scenario is:
(remote)MQ
(ssl connection)
->(local)MQ
-(jms)
>XI--
-(proxy)
>ECC
I met a very strange question during mapping which we use abap mapping inside xi.
the message come out from the abap mapping step.after the abap-mapping, the generated target message still has the source message concatenated with. it occurs only when all servers integrated together, but not occurs when we mannully put the source msg at local MQ (means this way, it works all right).
even during error case, it still can go through all the remaining steps of IE, and the out bound jms adapter then goes into the
target SAP ECC system, but of cause at the final step, it will reach u2018CX_ST_GROUP_MISSING_CASEu2019 error (this is because the message is not a valid xml file, and abap proxy can not consume it...
sample file after abap mapping:
<?xml version="1.0" encoding="utf-8"?> <ns:MT_MQIVMessage xmlns:ns="urn:ianes:mqiv"> <MQIVMessage> <MQIVPayload> ..data..</MQIVPayload> </MQIVMessage> </ns:MT_MQIVMessage> <?xml version="1.0"?> <ns:MT_K2 xmlns:ns="urn:ianes:prp:ipsc"> <header> .header.</header> <data>..data...</data> </ns:MT_K2>