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 Sender |
Transport Protocol |
HTTP 1.1 or HTTPs 2.0 |
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 |
The name of the Chem eStandard business transaction. For example: OrderCreate |
ServiceHeader– ProcessControl/ ProcessIdentity/ GlobalProcessCode |
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/ toService.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/ fromService.BusinessServiceDescription/ GlobalBusinessServiceCode |
Supply Chain Code |
This is specified in the RNIF 1.1 standard The values are available in the DTDs of the signal messages. |
Not Applicable |
Field |
Value |
Protocol Field in the Chem eStandard Message |
Code |
This value 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 value is however without spaces 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 /toRole.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/ fromRole.PartnerRoleDescription/ GlobalPartnerRoleClassificationCode
|
Field |
Value |
Number of Retries |
Default value available. |
Receipt Acknowledgement |
· Weak Strong means that the signals (acknowledgement /exception) will be sent only after receiving the acknowledgement from the Integration Server. Weak means that we do not wait for the Integration Server’s message processing to be completed to send out the signals (acknowledgement/exception). This attribute is configured only for the sender 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 receiving. |
Sign Signal Message |
Select or deselect Sign Signal Message. Your selection will determine whether the signal message is required to be signed before sending. |
Non-Repudiation |
Check or uncheck to request for non-repudiation logging for the transaction. |
Field |
Action |
URL |
Enter the partner address to which the signal 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. |
Field |
Action |
Set Adapter-Specific Message Attributes |
Select or deselect Set Adapter-Specific Message Attributes. Your selection determines whether attributes are available for selection. |
If you choose Set Adapter-Specific Message Attributes, the following fields are available:
Field |
Technical Name |
Action |
Process Instance Identifier |
Proc Inst Identifier |
Select or deselect Process Instance Identifier. Denotes a unique alphanumeric identifier that represents a specific instance of a business process. |
Message Identifier |
Message Identifier |
Select or deselect Message Identifier. Denotes a unique alphanumeric identifier that represents the message for tracking. This identifier is unique within the context of the message sender. |
Document Identifier |
Document Identifier |
Select or deselect Document Identifier. Denotes a unique alphanumeric identifier that represents the PIP business document. |
Document Date Time Stamp |
Document Date Time |
Select or deselect Document Date-Time Stamp. Denotes the date and time when the message is sent to the partner. |