Removing messsage header from the incoming AS2 message

[saurabhkumbhare]

Hello Experts,

I have a query.

Below is the payload content sent by the external party while sending the ORDERS message.

Can you please help me to know how the Message header part from "Mime-Version......................................application/xml" can be removed.

I just want the actual data.

Thanks in advance!!!

Regards

Saurabh

[saurabhkumbhare · Accepted solution]

Hi ,

Below is the audit log if the message contains the unnecessary header information and with the corrections you suggested above.

If i send the message using just the edifact message ( excluding the header ), below is the audit log.

This is to show that the TPM Content Access Module is configured correctly.

But still guessing how the header can be removed.

Thanks

Saurabh

[Dimitri · Accepted solution]

Can you share your adapter module configuration just one last time please?

[saurabhkumbhare · Accepted solution]

Hi ,

Sorry. I was unwell due to this issue

There is no space before the last module name OR before the first module name.

Regards

Saurabh

[Dimitri · Accepted solution]

Hi Saurabh,

Please refer to my previous post and have a look at the module names.

I'm still missing the localejbs in front of the TPM module.

Please be aware that module names must be correct and are case-sensitive.

Thank you.

Dimitri

[saurabhkumbhare · Accepted solution]

Hi Former Member,

Sorry, maybe i did not understand you correctly.

Config :

Output in Mendelson

Error in RWB of SAP PO

Payload of Version 2 : ( Latest payload )

Sender EDISeparator adaptor Config :

Can you tell me please what changes are required ?

Thanks

Saurabh

[Dimitri · Accepted solution]

Seems like all is OK, but I still doubt about the header. Does not seems to be standard EDI.

[saurabhkumbhare · Accepted solution]

Thanks Former Member.

Hi ,

Can you confirm once if possible if it is allowed for to pass such paylaods to the AS2 adapter.

Thanks

Saurabh

[saurabhkumbhare · Accepted solution]

Hi All,

The customer was sending an incorrect message. Header is not allowed as a part of the payload.

URL given to customer (CGI) was http://host:port/AS2/ but they send to http://hostport/AS2

Notice a slash is missing at the end. They corrected the URL and the header was removed

(Explanation given by CGI expert which sounds strange)

Thanks

Saurabh

[Dimitri]

Hi Saurabh,

Strange message content...

Can you share your sender AS2 adapter configuration please?

Please do not forget to use module localejbs/EdifactConverterModule to convert to XML.

Kind regards,

Dimitri

[saurabhkumbhare]

Hi ,

Thanks for your quick response.

Here are the config details of the sender AS2 CC.

I have used localejbs/EdifactConverterModule in the Sender EDI Seperator adaptor in the subsequent chain. Do you think this is required in the Sender AS2 adapter ?

Regards

Saurabh

[Dimitri]

Please do use the module I suggested and test.

[saurabhkumbhare]

Hi ,

When I add the module on the sender AS2 adapter as you suggested, I get the below error :

(The sequence of modules are 1. localejbs/EdifactConverterModule 2. TPMContentAccessModule 3.CallSAPAdapter)

[Oct 13, 2014 9:20:34 PM] mendelson_opensource_AS2-1413228033620-3@AS2ILEXT_7310865000002: MDN state is [processed/error: unexpected-processing-error].

[Oct 13, 2014 9:20:34 PM] mendelson_opensource_AS2-1413228033620-3@AS2ILEXT_7310865000002: Details of MDN received from remote AS2 server: Cannot deliver message to Moduleprocessor

If i removed the 1st module and trigger my payload looks as below : (the sender does not remove the header therefore it is expected that I remove it once i receive this message)

Regards

Saurabh

[Dimitri]

Hi Saurabh,

I see you work with Mendelson AS2. Please do have a look at these blog series:   Perhaps you can find some leads.

Very important is to use TPMContentAccessModule as the first module in the adapter. Please do change your module sequence.

Kind regards,

Dimitri

[saurabhkumbhare]

Hi ,

I tried as per your latest suggestion, however, i still get the same error.

[9:19:09 AM] mendelson_opensource_AS2-1413271149371-1@AS2ILEXT_7310865000002: MDN state is [processed/error: unexpected-processing-error].

[9:19:09 AM] mendelson_opensource_AS2-1413271149371-1@AS2ILEXT_7310865000002: Details of MDN received from remote AS2 server: Cannot deliver message to Moduleprocessor

As per my understanding this is probably because the CallSAPAdapter does not recognize the message as an EDIFACT/EANCOM message.

Thanks

Saurabh

[Dimitri]

Can you share your adapter module configuration?

Also, communicating with Mendelson requires some specific settings. Please do have a look at them too.

[saurabhkumbhare]

Hi ,

Please find below the adapter module configuration.

The problem is with the below configuration; if i send a file which contains payload ( that does not start with the EANCOM message), then i get the error mentioned.

Basically I want something that will offset the header.

Thanks

Saurabh

[Dimitri]

Hi Saurabh,

Please make sure you use the correct names for the modules

First, please correct this:

Second, is there a space before the last module name?

Kind regards,

Dimtiri