Communication Channel
Configuration
It is recommended that you use the channel templates that are provided for the configuration. This section only provides information on how to configure the communication channel in case you do not use the channel template.
Create a communication channel and then choose the Parameters tab.
Configure the following values:
Label |
Value |
Adapter Type |
CIDX |
Sender or Receiver |
Choose Receiver |
Transport Protocol |
HTTP or HTTPs |
Message Protocol |
RNIF 1.1 |
Adapter Engine |
Choose the Adapter Engine on the Integration Server or select a non-central Adapter Engine. |
Choose Single-Action Asynchronous Request.
Field |
Value |
Protocol Field in the Chem eStandard Message |
Process Name |
This value is obtained from the Chem eStandards Business Transaction name. This is however without the space. Example: OrderCreate |
ServiceHeader– ProcessControl/ ProcessIdentity/ GlobalProcessCode |
Transaction Name |
This value is obtained from the Chem eStandards Business Transaction name. This is however without the space. Example: OrderCreate |
ServiceHeader– ProcessControl/ TransactionControl/ TransactionIdentity/ GlobalTransactionCode
|
Message Version |
The version of the Chem eStandard Business Transaction. |
ServiceHeader– ProcessControl/ TransactionControl/ ActionControl/ ActionIdentity/ VersionIdentifier |
Current Business Service Code |
To arrive at this value, append the Service to the role. If the role of XI is Seller, then the value of this field would be Seller Service. |
ServiceHeader- ProcessControl/ ServiceRoute/ fromService.BusinessServiceDescription/ GlobalBusinessServiceCode |
Partner Business Service Code |
To arrive at this value, append the Service to the role. If the role of the partner is Buyer, then the value of this field would be Buyer Service. |
ServiceHeader- ProcessControl/ ServiceRoute/ toService.BusinessServiceDescription/ GlobalBusinessServiceCode |
Current Classification Code |
Not Specified in Chem eStandards. |
ServiceHeader– ProcessControl/ TransactionControl/ ActionControl/ PartnerRoute/ fromPartner.PartnerDescription/ BusinessDescription/ GlobalPartnerClassificationCode |
Partner Classification Code |
Not Specified in Chem eStandards. |
ServiceHeader– ProcessControl/ TransactionControl/ ActionControl/ PartnerRoute/ toPartner.PartnerDescription/ BusinessDescription/ GlobalPartnerClassificationCode |
Field |
Value |
Protocol Field in the Chem eStandard Message |
Code |
This is obtained from the Chem eStandards Appendix D – ChemXML Transaction Code. Example: E41 |
ServiceHeader– ProcessControl/ ProcessIdentity/ GlobalProcessIndicatorCode |
Version |
The version of the Chem eStandard Business Transaction. |
ServiceHeader– ProcessControl/ ProcessIdentity/ VersionIdentifier |
Requesting Message |
This value is obtained from the Chem eStandards Business Transaction name. This is however without any space in-between. Example: OrderCreate |
ServiceHeader– ProcessControl/ TransactionControl/ ActionControl/ ActionIdentity/ GlobalBusinessActionCode |
Current Role |
The role of XI. This value is obtained from the Chem eStandards Business Transaction specification. Example: Buyer
|
ServiceHeader– ProcessControl/ TransactionControl/ PartnerRoleRoute/ fromRole.PartnerRoleDescription/ GlobalPartnerRoleClassificationCode |
Partner Role |
The role of the partner. This value is obtained from the Chem eStandards Business Transaction specification. Example: Seller
|
ServiceHeader– ProcessControl/ TransactionControl/ PartnerRoleRoute/ toRole.PartnerRoleDescription/ GlobalPartnerRoleClassificationCode |
Document Schema Specification |
The name of the document type definition for the Chem eStandard Business Transaction. This is available with the transaction specification. For example: OrderCreateV30.dtd
|
Not Applicable |
Field |
Value |
Number of Retries |
Default value available. |
Time To Acknowledge Receipt |
Time interval between subsequent retries of Business Action messages in case an acknowledgement is not received from the partner. This attribute is present only in the receiver channel. |
Field |
Value |
Sign Action Message |
Select or deselect Sign Action Message. Your selection will determine whether the action message is required to be signed before sending. |
Sign Signal Message |
Select or deselect Sign Signal Message. Your selection will determine whether the signal message is required to be signed before receiving. |
Non-Repudiation |
Check or uncheck to request Non Repudiation logging for the transaction. |
Field |
Value |
URL |
Enter the partner address to which the action message will be sent by the adapter. |
Persist Duration |
Enter the duration during which the message will be persisted on the messaging system store. The default value can be chosen. |
This depends on whether you use HTTP or HTTPs as the transport protocol.
If you choose HTTP:
Value |
Description |
Client Authentication Required |
Check this value |
User name |
Provided by the partner |
Password |
Provided by the partner |
If you choose HTTPs:
Value |
Description |
Authentication Mode |
Username/Password or Certificate Logon If you choose Certificate Logon, specify the values for Keystore Entry and Keystore View. |