Payload changes in Adapter Engine

[Former Member]

Hi ,

I am facing a strange issue where the payload seen in the Adapter Engine(Receiver end) differs from the payload visible in the Integration Engine (SXMB_MONI).

If I go into the details, we are using a SOAP Adapter on Decentral Adapter engine to fetch data from a .Net service and the synchronous interface fetches the payload correctly as seen in the Integration engine but the strange part is, the hierarchy of the data gets mixed up when it reaches the final receiver.

Please can someone help me where I need to start de-bugging my interface.Seems like somehow my XSL mapping code is inserted in the paylod.

expected response(seen in Int. Engine)

*************************

- <Response>

- <DsgResult>

- <GetDistributionCentersByUserNameResponse>

- <GetDistributionCentersByUserNameResult>

- <DistributionCenter>

<DistributionCenterId>7</DistributionCenterId>

<DistributionCenterNumber></DistributionCenterNumber>

<DistributionCenterName></DistributionCenterName>

<Address1 />

<Address2 />

<Address3 />

<Address4 />

<ContactEmail />

<TimeInterval>-1</TimeInterval>

<OpeningHours>-1</OpeningHours>

<ClosingHours>-1</ClosingHours>

<TimeZone />

Response in Receiver end (as seen in adapter engine)

*********************************************************************

- <GetDistributionCentersByUserNameResponse xmlns="http://tempuri.org/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

- <GetDistributionCentersByUserNameResult xmlns:a="http://schemas.datacontract.org/2004/07/XXXXXXXXXXXXX.Entity" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

<ErrorCode xmlns="XXXXXXXXXXXXX">NoError</ErrorCode>

<ErrorMessage xmlns="XXXXXXXXXXXXX" />

<ErrorReason xmlns="XXXXXXXXXXXXX">NoError</ErrorReason>

<Int64ErrorCode xmlns="XXXXXXXXXXXXX">0</Int64ErrorCode>

<Int64ErrorReason xmlns="XXXXXXXXXXXXX">0</Int64ErrorReason>

<Success xmlns="XXXXXXXXXXXXX">true</Success>

- <a:DistributionCenter>

- <xs:schema id="DistributionCenterDataSet" targetNamespace="http://tempuri.org/DistributionCenterDataSet.xsd" attributeFormDefault="qualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:mstns="http://tempuri.org/DistributionCenterDataSet.xsd" xmlns="http://tempuri.org/DistributionCenterDataSet.xsd" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">

- <xs:element name="DistributionCenterDataSet" msdata:IsDataSet="true" msdata:UseCurrentLocale="true">

[Former Member · Accepted solution]

put the trace level highest (3) , check the payload after technical routing in IE.

take the payload from first step of IE (Moni)-rightclick-view source and put it in mapping test of ESR.

[Former Member]

Hi All,

Thanks for your prompt inputs but I should say I am sorry to comsue your time on this.I just got access to view the PAYLOAD on the Decentral Adapter Engine and it is fine but I am still not clear why the payload is scattered on the Central adapter engine.

Thanks & Regards,

Harish.

[stefan_grube]

> .Seems like somehow my XSL mapping code is inserted in the paylod.

Obviously your XSLT mapping is wrong.

Have you tested this outside PI, with a XSLT test tool? Note that PI supports only XSLT 1.1

[PriyankaAnagani]

Hi,

It seems like there might be some problem with your mapping. Try to copy the payload and test the operation mapping with the same payload.

Regards

Priyanka