Using Conventions for Communication Component Names

If you are using the CIDX adapter, there is a convention for naming the communication component that is assigned to the communication channel. This specification is runtime-relevant.

1. Create a communication component.
2. Adhere to the following convention when naming the communication component:

   Name: CIDX<Transaction code>_<Version>_<Role>

   • <Transaction code> is the corresponding Chem eStandards Appendix D - ChemXML Transaction Code.

     Example: E41

   • <Version> is the version of the Chem eStandard. The dot is removed from the version string.

     Example: 30

   • <Partner role> comes from the Chem eStandards Business Transaction specification.

     Example: Buyer

   • <Current role> comes from the Chem eStandards Business Transaction specification.

     Example: Seller

The CIDX adapter determines the name of the communication component of the partner and the current name of the communication component for an incoming CIDX action message that is based on selected header fields of the RNIF 1.1 protocol service header. The adapter then constructs the name of the communication component according to the above-mentioned rules as follows:

<Transaction Code>:= /ServiceHeader/ProcessControl/ProcessIdentity/GlobalProcessIndicatorCode

<Version>:= /ServiceHeader/ProcessControl/ProcessIdentity/VersionIdentifier

<Partner Role>:= /ServiceHeader/ProcessControl/TransactionControl/PartnerRoleRoute/fromRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

<Current Role>:= /ServiceHeader/ProcessControl/TransactionControl/PartnerRoleRoute/toRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

CIDXE41_30_Seller:

E41 is the transaction name, 3.0 is the version, and Seller is the partner's role.