Skip to Content

SOAP UI Error on receiving MDN in plain text format:

I1.png

MDN Plain text payload:

I2.png

To cater this problem, the MDN appearing in plain text needs to be converted to XML format. This is done through the Standard bean “MEssageTransformBean” using following parameters.

I3.png

I4.png

I5.png

After placing the bean successfully, the MDN response looks like this in SOAP UI.

I6.png

i. Save, activate and deploy the Iflow.

I7.png

Test of the Scenario:

i.  Download the WSDL for the Integration Scenario from the corresponding ICO in ID and import it in the SOAP UI to create a SOAP UI Project. Specify the     authentication details along with the correct URL and hit the Execute button.

I8.png

ii. The successful response is received in the Response window.

I9.png

iii. Go to the Message Monitor and two successful messages can be seen that correspond to the outbound request and incoming response respectively.

I10.png

iv. In the Message Log for outbound request, the AS2 Receiver Channel Details can be found out.

I11.png

v. The Message Log also shows the receipt of MDN and it passing through the MessageTransformBean.

Note: The Outbound Request Message goes out of PI as soon as it goes through the local bean localejbs/ModuleProcessorExitBean and hence doesn’t pass through the MessageTransformBean. It’s only the MDN which passes through the MessageTransformBean and the plain text gets converted to XML.

I12.png

vi. Now go to the B2B Acknowledgements and the MDN status should be Success with the status code as VALIDATED_SYNC_POS which means that the synchronous MDN message has been received successfully.

I13.png

vii. Now select the Response message. It shows the delivery of the Message to the Sender component.

Scenario 2:  IDOC to AS2 Adapter (Receiver) – Asynchronous Scenario

i. Import the dtd (data type definition) in the RosettaNet format as an External definition which will work as the Data Type and Message Type for Receiver Side.

I14.png

ii. Import the Idoc on the sender side which will work as DT, MT and SI.

iii. Create Receiver Async  SI.

     Note: The Interface pattern for both Receiver SI has to be Stateless (XI30 Compatible).

iv. Create the MM & OM.

v. Create an Iflow in a usual way while configuring IDOC Channel on the sender side.

(The multiple recipient list or the branching appearing in the Iflow below can be ignored. This was specifically done to achieve the client requirement).

     Note: The Iflow has to be a Non Specific Operation.

I15.png

vi. Define a specific Channel name for AS2 Receiver Channel . Now configure the AS2 Channel exactly in the same manner as in the scenario 1 apart from the following two differences.

    1. MDN: Go to the MDN tab and choose the processing mode for MDN as NONE. As the Idoc on the sender side works asynchronously hence this mode ensures that PI doesn’t request MDN from the Business partner and considers the message success as soon as it is delivered to the partner.

I16.png

          b. Modules: As no MDN is received from the partner hence there is no need to configure the MessageTransformBean to convert the plain text MDN into               XML.

I17.png

vii.  Save, activate and deploy the Iflow.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply