Content type for EDIFACT Messages - AS2
Hello,
We tried to post an EDIFACT message to our local AS2 server (Cyclone- Drummond
Certified AS2 server).However the AS2 message had the content type as
application/EDI-EDIFACT. Due to this Cyclone wasunable to detect this message as
EDIFACT and treated the same as binary message (AS2 headers etc were left
as is in the Cyclone backup folder)
To overcome this, we changed the HTTP content type property to application/EDIFACT
in the send port.However Biztalk continues to post the message with content type as
application/EDI-EDIFACT.
When we manually change the content type of the posted EDIFACT message in
Cyclone, themessage gets processed correctly.
Please let us know as to how we can change the Content Type of the message from
"application/EDI-EDIFACT" to "application/EDIFACT".
Kindly help.
Regards,
Roy.
[3501 byte] By [
Roy_NK] at [2008-2-28]
Dear Yury,
We made the necesary changes as suggested (i.e.) we selected the Content Type of the Receiver Party to "Application/EDIFACT". However, the message continues to be posted with content Type as - "Application/EDI-EDIFACT"
See below the contents of the outbound EDIFACT messages posted via AS2-HTTP
POST /exchange/procter HTTP/1.1
Content-Type: application/EDI-EDIFACT
Message-ID: <BLRWKS0299_911AA8CF-136F-4281-89EF-E3263E26EA50>
Disposition-Notification-To: http://172.16.78.40:80/
AS2-From: CARREFOUR
AS2-To: procter
Content-Transfer-Encoding: binary
Content-ID: {9EEFCE53-F006-4A3F-9A33-4F49A46A948B}
AS2-Version: 1.1
Content-Description: body
Mime-Version: 1.0
User-Agent: Microsoft(R) BizTalk(R) Server 2006 R2 3.0.1.0
Host: 172.16.78.114:4080
Content-Length: 182
Expect: 100-continue
Connection: keep-alive
UNA:+,?*'UNB+UNOB:1+CARREFOUR:14+procter+070702:1709+18++++0++1'UNH+001+ORDERS
:96A:UN:EAN001'BGM+220+472860+9'DTM+137:20040224:102'RFF+SD:32'NAD+BY+881::9'UNS+S'UNT+7+001'UNZ+1+18'
Please update us
Regards,
Roy.
Replying on behalf of Roy,
Yes we tried the steps you have suggested (changed orchestration assigned the HTTP content type to the destination message), restarted service, IIS & host instance.
however the message is still posted with the content type as application/EDI-EDIFACT.
Hello Saravana,
Flat File is received and the same is tranformed into EDIFACT document. The EDIFACT is then sent over AS2/HTTP to another AS2
server.
In order to do the same we iniatlly used a receive port (File protocol) and applied the map. The Send Port was subscribed directly to the
Receive Port using filter.
Send port was configured with HTTP properties (content type as Application/EDIFACT). The send port was assigned to a party.
In the Party EDI properties(party as Interchnage receiver) & AS2 properties (party as AS2 receiver) were configured.
In the AS2 properties, too the HTTP content type was assigned as Application/EDIFACT.
However the message continued to be posted with content type as Application/EDI-EDIFACT (due to which the message was not
getting parsed correctly at the receiving AS2 server)
Later as per your suggestion, we created an orchestration with Receive(FlatMsg) -> Transform (FlatMsg->EDIMessage) -> contruct
message (message asignment) expr: EDIMessage(HTTP.contentType)="Application.EDIFACT"; ->Send
However still the message continue to be posted as application/EDI-EDIFACT
Also as per the AS2 draft
3.4 RFC 1767 EDI Content [2]
This RFC defines the use of content type "application" for ANSI X12
(application/EDI-X12), EDIFACT (application/EDIFACT) and mutually
defined EDI (application/EDI-Consent).
There is no such value as application/EDI-EDIFACT?
Hello Saravana,
Sorry there was a typo mistake, we used - EDIMessage(HTTP.contentType)="Application/EDIFACT".
Further, in the Send Pipeline, we are using AS2EDISend but still we are receving the Content Type of the message as -
application/EDI-EDIFACT.
I'll be posting you another mail by evening which will explain in details as to how we did the setup in BTS R2.
Regards,
Roy.
