Communication Channel
Configuration
You create two communication channels, one as Sender and another as Receiver.
Create a communication channel and then choose the Parameters tab.
Configure the following values:
Field |
Action |
Adapter Type |
RNIF |
Sender or Receiver |
Choose Receiver |
Transport Protocol |
HTTP or HTTPs |
Message Protocol |
RNIF 2.0 |
Adapter Engine |
Choose the Adapter Engine on the Integration Server or select a non-central Adapter Engine. |
Choose Two-Action Asynchronous Request.
Field |
Action |
Agency |
RosettaNet (default – refers to the global administering authority code) |
Version |
2.0 (default – standard version identifier). The version identifier is different from the PIP version that is listed in the PIP dictionary on the RosettaNet website. |
Field |
Action |
Current |
<locationID> of the XI party. Example: New York |
Partner |
<locationID> of the configured partner. Example: Frankfurt |
Field |
Action |
Number of Retries |
You can use the default value displayed or enter a new value from the Retry Count column of the Business Activity Performance Controls table in the PIP Specification document. The value is the number of times the Action message will be re-transmitted before the adapter receives a signal from the partner. |
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. This value must be taken from the Time to Acknowledge column from the PIP specification’s Business Activity Performance Controls table. |
Time to Perform |
Value must be taken from the Time to Perform column of the PIP specification’s Business Activity Performance Controls table. |
Field |
Action |
Code |
PIP standard code ex. 3A4 |
Version |
PIP version. The PIP version identifier is found on the front page of the PIP specification and is shorter than the PIP Version. Example: V02.02 is the version identifier while V02.02.01 is the PIP version. |
Business Transaction Activity |
Value must be taken from the Activity Name column from the PIP specification’s Business Activity Descriptions table. |
Requesting Action |
Value must be taken from the Business Action in FSV column of the PIP specification's Business Action - Business Document Mapping table. |
Current Role |
Value must be taken from the corresponding FromRole element (or ToRole element, as the case may be) in the PIP specification corresponding to the currently executing PIP, Activity and Action. |
Partner Role |
Value must be taken from the corresponding ToRole element (or FromRole element, as the case may be) in the PIP specification corresponding to the currently executing PIP, Activity and Action. |
Current Business Service Code |
Value must be taken from the corresponding FromService element (or ToService element, as the case may be) in the PIP specification corresponding to the currently executing PIP, Activity and Action |
Partner Business Service Code |
Value must be taken from the corresponding ToService element (or FromService element, as the case may be) in the PIP specification corresponding to the currently executing PIP, Activity and Action. |
Document Schema Specification |
DTD of the corresponding action. This is available only in the receiver channel. |
Field |
Action |
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 of Origin and Content |
Check or uncheck depending on the standard. |
Non-Repudiation of Receipt Acknowledgement |
Check or uncheck depending on the standard. |
Value |
Description |
URL |
Enter the partner address to which the RosettaNet 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:
Field |
Action |
Client Authentication Required |
Check this value |
User name |
Provided by the partner |
Password |
Provided by the partner |
If you choose HTTPs:
Field |
Action |
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. |
Create a communication channel and then choose the Parameters tab.
Configure the following values:
Field |
Action |
Adapter Type |
RNIF |
Sender or Receiver |
Choose Sender |
Transport Protocol |
HTTP or HTTPs |
Message Protocol |
RNIF 2.0 |
Adapter Engine |
Choose the Adapter Engine on the Integration Server or select a de-centrally installed Adapter Engine. |
Choose Two-Action Asynchronous Request.
Field |
Action |
Receipt Acknowledgement |
· Strong · Weak Strong means that the RNIF 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 RNIF signals (acknowledgement/exception). This attribute is configured only for the sender channel. |
Field |
Action |
Responding Action |
Value must be taken from the Business Action in FSV column of the PIP specification's Business Action - Business Document Mapping table. |
Field |
Action |
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 of Origin and Content |
Check or uncheck depending on the standard. |
Non-Repudiation of Receipt Acknowledgement |
Check or uncheck depending on the standard. |