Creating a Service 

You must create a new service for the partner using a naming convention.

The service name should comply with the following definition:

Service Name: “CIDX” <Transaction Code>”_” <Version> ”_” <Partner Role>.

This name binding is runtime-relevant. The CIDX Adapter determines the partner’s service name and the local service name for an incoming CIDX action message based on selected header fields of the RNIF 1.1 protocol service header. The adapter then constructs the name 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

Variable	Value
<Transaction Code>	This value is obtained from the corresponding Chem eStandards Appendix D – ChemXML Transaction Code. Example: E41
<Version>	This value is obtained from the version of the Chem eStandards. The dot is removed from the version string. Example: 30
<Partner Role>	This value is obtained from the Chem eStandards Business Transaction specification. Example: Buyer
<Current Role>	This value is obtained from the Chem eStandards Business Transaction specification. Example: Seller

For Example: CIDXE41_30_Seller where E41 is the transaction name, 3.0 is the version and Seller is the partner’s role.