CIDX adapter <!DOCTYPE - addition for Preamble and ServiceHeader

[Former Member]

We are using the CIDX adapter in PI 7.1 for sending the OrderCreate 4.0 message to a partner.

When the partner received a first message they had the following remark:

We are not sending the reference to the DTD for Preamble and ServiceHeader part:

Partner expects:

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE Preamble SYSTEM "PreamblePartMessageGuideline.dtd">

<Preamble><DateTimeStamp>20090724T064154.122Z</DateTimeStamp><GlobalAdministeringAuthorityCode>CIDX</GlobalAdministeringAuthorityCode><GlobalUsageCode>Test</GlobalUsageCode><VersionIdentifier>1.1</VersionIdentifier></Preamble>

We are sending:

<?xml version="1.0" encoding="UTF-8"?>

<Preamble><DateTimeStamp>20090724T064154.122Z</DateTimeStamp><GlobalAdministeringAuthorityCode>CIDX</GlobalAdministeringAuthorityCode><GlobalUsageCode>Test</GlobalUsageCode><VersionIdentifier>1.1</VersionIdentifier></Preamble>

My questions:

Is this really part of the CIDX standard, or can then be left out?

Is there something that I forgot to set up?

Any way I can get it in?

Thanks

Thierry Boeve

[rajasekhar_reddy14 · Accepted solution]

Hi,

When you send CIDX Message to ELEMICA Or what ever system,CIDX msg should contain CIDX message DOC Type Order Create or Order Chnage or Order Response..........

Version is 2.0.2 or 3.0,it depends on which version of DTD using.

i think DOCType and Version misisng,check once in dtd .

Regards,

Raj

[Former Member]

I can't change anything in the Schema, from the part that's added by the CIDX adapter:

I can change the actual OrderCreate message, but not the part that's added by the CIDX adapter.

The CIDX adapter part is in Bold

Content-Type:application/x-rosettanet-agent

• &ÏMessage-ID: <490755631.141248417714315.JavaMail.pxdadmbeevssd2.int.huntsman.com>*

MIME-Version: 1.0

Content-Type: multipart/related;

boundary="----=_Part_688_1226761625.1248417714232";

type="Application/x-ChemXML"

Content-Description: This is the RosettaNet Business Message

------=_Part_688_1226761625.1248417714232

Content-Type: Application/XML; RNSubType="preamble-header"

Content-Transfer-Encoding: binary

Content-ID: preamble-header.1362cb80781d11deb638001125bd0fd4sap.com

<?xml version="1.0" encoding="UTF-8"?><Preamble><DateTimeStamp>20090724T064154.122Z</DateTimeStamp><GlobalAdministeringAuthorityCode>CIDX</GlobalAdministeringAuthorityCode><GlobalUsageCode>Test</GlobalUsageCode><VersionIdentifier>1.1</VersionIdentifier></Preamble>

------=_Part_688_1226761625.1248417714232

Content-Type: Application/XML; RNSubType="service-header"

Content-Transfer-Encoding: binary

Content-ID: service-header.13656390781d11de8dd6001125bd0fd4sap.com

<?xml version="1.0" encoding="UTF-8"?><ServiceHeader><ProcessControl> ... </ProcessControl></ServiceHeader>

------=_Part_688_1226761625.1248417714232

Content-Type: Application/XML; RNSubType="service-content"

Content-Transfer-Encoding: binary

Content-ID: service-content.1367fba0781d11deac08001125bd0fd4sap.com

----=_Part_688_1226761625.1248417714232

[Former Member]

Hi

Please let me know if you got the solution for this.

I am also facing the same issue.

Regards,

Rama.

[Former Member]

Sorry about the poor formatting of my previous reply, i can't get it correctly formatted, i don't understand why.

We are sending CIDX messages to Elemica without the DOCTYPE addition. But another partner is having problems with it.

I still have to add a schema reference to the OrderCreate message, this will be no problem. But how do I add the DOCTYPE for ServiceHeader and Preamble??

[rajasekhar_reddy14]

Hi ,

Please check once your CIDX Message has DocType ,Version or not,if it is not there please add in shema DocType and Version.

regards,

Raj

[Former Member]

Hi Boeve,

I think its something related to your schema you are uisng. Also I think you are not getting the same thing in your payload also apart from header. I think we can add this to your schema and see. Can you please tell from where you downloaded the schema and also give the sample xml file.

Regards,

---Satish

[Former Member]

Hi Satish

I don't have a schema for this, it's all handled by the CIDX adapter.

The OrderCreate message is the only part that I can handle myself, all the enveloping is standard.

The problem is with the Preamble and Service header.

Content-Type:application/x-rosettanet-agent


  &ÏMessage-ID: <490755631.141248417714315.JavaMail.pxdadmbeevssd2.int.huntsman.com>
MIME-Version: 1.0
Content-Type: multipart/related; 
	boundary="----=_Part_688_1226761625.1248417714232"; 
	type="Application/x-ChemXML"
Content-Description: This is the RosettaNet Business Message



------=_Part_688_1226761625.1248417714232
Content-Type: Application/XML; RNSubType="preamble-header"
Content-Transfer-Encoding: binary
Content-ID: preamble-header.1362cb80781d11deb638001125bd0fd4sap.com

<?xml version="1.0" encoding="UTF-8"?><pre><code><DateTimeStamp>20090724T064154.122Z</DateTimeStamp><GlobalAdministeringAuthorityCode>CIDX</GlobalAdministeringAuthorityCode><GlobalUsageCode>Test</GlobalUsageCode><VersionIdentifier>1.1</VersionIdentifier></code></pre>
------=_Part_688_1226761625.1248417714232
Content-Type: Application/XML; RNSubType="service-header"
Content-Transfer-Encoding: binary
Content-ID: service-header.13656390781d11de8dd6001125bd0fd4sap.com

<?xml version="1.0" encoding="UTF-8"?><ServiceHeader><ProcessControl><ProcessIdentity><GlobalProcessCode>OrderCreate</GlobalProcessCode><GlobalProcessIndicatorCode>E41</GlobalProcessIndicatorCode><initiatingPartner><GlobalBusinessIdentifier>405338377</GlobalBusinessIdentifier></initiatingPartner><InstanceIdentifier>1312afb0781d11de86e9001125bd0fd4</InstanceIdentifier><VersionIdentifier>4.0</VersionIdentifier></ProcessIdentity><ServiceRoute><fromService><BusinessServiceDescription><GlobalBusinessServiceCode>Buyer Service</GlobalBusinessServiceCode></BusinessServiceDescription></fromService><toService><BusinessServiceDescription><GlobalBusinessServiceCode>Seller Service</GlobalBusinessServiceCode></BusinessServiceDescription></toService></ServiceRoute><TransactionControl><AttemptCount>1</AttemptCount><PartnerRoleRoute><fromRole><PartnerRoleDescription><GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode></PartnerRoleDescription></fromRole><toRole><PartnerRoleDescription><GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode></PartnerRoleDescription></toRole></PartnerRoleRoute><TransactionIdentity><GlobalTransactionCode>OrderCreate</GlobalTransactionCode><InstanceIdentifier>1312afb0781d11de86e9001125bd0fd4</InstanceIdentifier></TransactionIdentity><ActionControl><ActionIdentity><GlobalBusinessActionCode>OrderCreate</GlobalBusinessActionCode><InstanceIdentifier>1347f080781d11de8d5b001125bd0fd4</InstanceIdentifier><VersionIdentifier>4.0</VersionIdentifier></ActionIdentity><GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode><PartnerRoute><fromPartner><PartnerDescription><BusinessDescription><GlobalBusinessIdentifier>405338377</GlobalBusinessIdentifier></BusinessDescription><GlobalPartnerClassificationCode>Buyer</GlobalPartnerClassificationCode></PartnerDescription></fromPartner><toPartner><PartnerDescription><BusinessDescription><GlobalBusinessIdentifier>387453178</GlobalBusinessIdentifier></BusinessDescription><GlobalPartnerClassificationCode>Seller</GlobalPartnerClassificationCode></PartnerDescription></toPartner></PartnerRoute><PerformanceControlRequest><timeToAcknowledgeReceipt><TimeDuration>00000003T000000.000Z</TimeDuration></timeToAcknowledgeReceipt></PerformanceControlRequest></ActionControl></TransactionControl></ProcessControl></ServiceHeader>
------=_Part_688_1226761625.1248417714232
Content-Type: Application/XML; RNSubType="service-content"
Content-Transfer-Encoding: binary
Content-ID: service-content.1367fba0781d11deac08001125bd0fd4sap.com

<?xml version="1.0" encoding="utf-8"?>
<OrderCreate Version="4.0">
  <Header>
    <ThisDocumentIdentifier>
      <DocumentIdentifier>4A65D83286B800B8E1008000CDEB6913</DocumentIdentifier>
    </ThisDocumentIdentifier>
    <ThisDocumentDateTime>
      <DateTime DateTimeQualifier="On">2009-07-24T06:41:42Z</DateTime>
    </ThisDocumentDateTime>
   ...
  </OrderCreateBody>
</OrderCreate>

------=_Part_688_1226761625.1248417714232--

Edited by: Thierry Boeve on Aug 3, 2009 9:55 AM