Configuring the Sender RNIF 1.1 Adapter for Responses

You use this adapter in the Two-Action Responder scenario. The partner uses the adapter to respond to a request from the Integration Server.

More information: Two-Action Responder

We recommend using the communication channel templates provided in the business package. 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.1
   • HTTPS
2. The Message Protocol is RNIF 1.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

The values you enter are referenced from the PIP specification document for the PIP you want to use.

The values are used to validate the RNIF protocol fields for inbound RNIF messages against the corresponding fields in the configuration of the communication channel. If the validation is unsuccessful, a general exception signal is sent to the partner.

1. Under Supply Chain Code, enter a value from the entity list for the GlobalSupplyChainCode element in the guideline for RosettaNet receipt acknowledgment messages. The guideline is part of the RNIF 1.1 specification document.

   For example, enter Electronic Components.

   RNIF protocol field:

   ReceiptAcknowledgmentPayload-fromRole.PartnerRoleDescription/PartnerDescription/BusinessDescription/GlobalSupplyChainCode

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

Define Message Exchange Controls

1. Under Number of Retries, specify how often the partner can attempt to resend messages.
2. Select the Receipt Acknowledgment:
   • Weak

     The signal message (confirmation/exception) is sent before message processing on the Integration Server is complete.

   • Strong

     The signal message (confirmation/exception) is not sent until confirmation has been received from the Integration Server.

Define Security Policy

1. If you want the action message to be signed, select Sign Action Message.
2. If you want the signal message to be signed, 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.

   A partner that has sent a business action message cannot deny having done so.

   The message is saved in the security archive.

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

   More information: Configuring Security in the RNIF 1.1 Adapter