Configuring the Receiver RNIF 1.1 Adapter for Requests

You use this adapter in the Single-Action Responder and Two-Action Responder scenarios. The partner uses this adapter to respond to the Integration Server.

More information: Single-Action Responder , Two-Action Responder

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 RNIF 1.1.
3. Select the Adapter Engine on the Integration Server, or select a non centrally installed Adapter Engine.
4. Select the Process Specificationtab page.
5. Depending on the scenario, select the Configuration Type.
   • Single-Action Asynchronous Request
   • Two-Action Asynchronous Request

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 in these fields are used to fill the RNIF protocol fields for all outbound action or signal messages.

1. Under Process Name, enter the name from the title page of the PIP specification document.

   For example, enter Asynchronous Notification for PIP0C1.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessCode

2. Under Transaction Name, enter the value from the Activity Name column of the Business Activity Descriptions table in the PIP specification document.

   For example, enter Notify of remittance advice.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/TransactionIdentity/GlobalTransactionCode

3. Under Message Version, enter the value from the PIP version identifier on the title page of the PIP specification document.

   For example, the PIP version identifier in the specification document is V02.02. Omit the period.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/VersionIdentifier

4. Under Current Business Service Code, enter the value from the Network Component in FSV column of the specification table for network components in the PIP specification document.

   The value corresponds to the role assumed by the Integration Server in the PIP.

   For example, enter Buyer Service, Initiator Service.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ServiceRoute/fromService/BusinessServiceDescription/GlobalBusinessServiceCode

5. Under Partner Business Service Code, enter the value from the Network Component in FSV column of the specification table for network components in the PIP specification document.

   The value should correspond to the role assumed by the partner in the PIP.

   For example, enter Seller Service, Responder Service.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ServiceRoute/toService/BusinessServiceDescription/GlobalBusinessServiceCode

6. 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 or Supplier.

   RNIF protocol field:

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

7. Under Partner 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 partner in the supply chain.

   For example, enter Product Supplier or Distributor.

   RNIF protocol field:

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

Define PIP Information

1. Under Code, enter the PIP standard code.

   For example, enter 3A7.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessIndicatorCode

2. Under Version, enter the value from the PIP version identifier on the title page of the PIP specification document.

   For example, the PIP version identifier in the specification document is V02.02. Omit the period.

   RNIF protocol field:

   ServiceHeader-ProcessControl/ProcessIdentity/VersionIdentifier

3. Under Requesting 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 Asynchronous Test Notification Action.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/ActionControl ActionIdentity/GlobalBusinessActionCode

4. Under Current Role, enter the value from the Role Name column of the Partner Role Descriptions table in the PIP specification document.

   The value should correspond to the role assumed by the partner in the PIP.

   For example, enter Buyer or Initiator.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/PartnerRoleRoute/fromRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode

5. Under Partner Role, enter the value from the Role Name column of the Partner Role Descriptions table in the PIP specification document.

   The value should correspond to the role assumed by the partner in the PIP.

   For example, enter Seller or Responder.

   RNIF protocol field:

   ServiceHeader-ProcessControl/TransactionControl/PartnerRoleRoute/ toRole.PartnerRoleDescription/GlobalPartnerRole ClassificationCode

6. Under Document Schema Specification, enter the DTD for the corresponding action from the Integration Server.

   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 from the partner.

   Use the default value displayed or 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.
3. Specify the Time to Perform in days, hours, minutes, and seconds.

   Enter the value from the Time to Perform 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 (BC-XI)

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

   More information: Configuring Security in the RNIF 1.1 Adapter

Define Transport Parameters

1. Select the Target tab page.
2. Under URL, enter the partner address to which the adapter is to send the RosettaNet signal message.
3. Under Persist Duration, specify the length of time in days, hours, minutes, and seconds that messages are to be stored in the Adapter Framework message store, depending on the communication channel.

Define Authentication

1. The specifications for Authenticationdepend on the transport protocol you have selected:
   • If a client authentication is required for transport protocol HTTP 1.1, select Client Authentication Required.
   • Enter the User Name and Password, and confirm.

     This information is provided by the partner.

   • Select the Authentication Mode for transport protocol HTTPS:
     • User Name/Password

       Enter the User Name and Password of the partner.

       This information is provided by the partner.

     • Certificate Logon

       Select the Keystore View and the Keystore Entry.

       Under Keystore View, enter the path to the keystore entries in AS Java that contain the private key of the partner, for example SslService.

       Under Keystore Entry, enter the name of the private key of the partner, for example SslCredentials.

Define Adapter-Specific Message Properties for Configuration Type Two-Action Asynchronous Request

1. Select the Advanced tab page.
2. To evaluate adapter-specific attributes in the message header of the PI message, select Set Adapter-Specific Message Properties.
3. To evaluate the following attributes in PI message headers, set the corresponding indicators:
   • Process Instance Identifier (technical name: Proc Inst Identifier)

     Unique alphanumeric ID for an instance of a business process.

   • Message Identifier (technical name: Message Identifier)
   • Document Identifier (technical name: Document Identifier)

     Unique alphanumeric ID for the PIP business document.

   • Document Date Timestamp (technical name: Document Date Time)

     Date and time that message is sent to partner.