Configuring the Receiver RNIF 1.1 Adapter for Responses

You use this adapter in the Two-Action Initiator scenario. The adapter is used to send a response to the initiator of message exchange.

More information: Two-Action Initiator

We recommend using the communication channel templates provided in the shipment. If you do not use the templates, make the required specifications for the adapter.

More information: Configuring RNIF 1.1 Adapter with Comm. Channel Templates

• You have created a party and a communication component.

  More information: Using Conventions for Communication Component Names

1. Select the Transport Protocol:
   • HTTP 1.0
   • HTTPS
2. The Message Protocol is RNIF1.1.
3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.
4. Select the Process Specification tab page.
5. The Configuration Type is Two-Action Asynchronous Response.

Define Message Protocol Specific Information

1. Under Message Version, enter the value from the PIP Version Identifier on the title page of the PIP specification document.

   If the PIP version identifier in the specification document is V02.02, enter V0202.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ProcessIdentity/VersionIdentifier

2. Under Current Classification Code, enter a value from the entity list specified for the GlobalPartnerClassification Code element in the guideline for RosettaNet service header messages. The guideline is part of the RNIF 1.1 specification document.

   Choose the most appropriate value for activity and action in the PIP specification document, corresponding to the currently executing PIP.

   The field describes the function of the Integration Server in the supply chain.

   For example, enter Product Supplier, Supplier.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/PartnerRoute/fromPartner.PartnerDescription/ GlobalPartner ClassificationCode

3. Under Partner Classification Code, enter the value from the entity list specified for the GlobalPartnerClassification Code element in the guideline for RosettaNet service header messages. The guideline is part of the RNIF 1.1 specification document.

   Choose the most appropriate value for activity and action in the PIP specification document, corresponding to the currently executing PIP.

   The field describes the function of the partner in the supply chain.

   For example, enter Product Supplier, Distributor.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/PartnerRoute/toPartner.PartnerDescription/GlobalPartnerClassificationCode

Define PIP Information

1. Under Responding Action, enter the value from the Business Action in FSV column of the Business Action - Business Document Mapping table in the PIP specification document.

   For example, enter Purchase Order Confirmation Action.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/GlobalBusinessActionCode

2. Under Document Schema Specification, enter the DTD for the corresponding action from the Integration Builder.

   For example, enter 1_MS_R01_02_Asynchronous TestNotification.dtd.

   RNIF protocol field:

   URI reference to external DTD as system identifier, created in the DOCTYPE - XML processing statement.

Define Message Exchange Controls

1. Under Number of Retries, specify how often an action message can be transferred before the adapter receives a signal message from the partner.

   You can change the value displayed and enter a value from the Retry Count column of the Business Activity Performance Controls table in the PIP specification document.

2. Under Time to Acknowledge Receipt, enter the value from the Time to Acknowledge column of the Business Activity Performance Controls table in the PIP specification document.

Define Security Policy

1. If you want the action message to be signed before sending, select Sign Action Message.
2. If you want the signal message to be signed before receipt, select Sign Signal Message.
3. If you want to request a non-repudiation log for the transaction, select Non-Repudiation.

   Non-repudiation can only be checked if you select Sign Action Message and Sign Signal Message.

   More information: Non-Repudiation

4. Make the entries for the certificates in the receiver agreement.

   More information: Configuring Security in the RNIF 1.1 Adapter