Show TOC

Configuring the Receiver RNIF 2.0 Adapter for RequestsLocate this document in the navigation structure

Use

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 the RNIF 2.0 Adapter with Communication Channel Templates

Prerequisites

You have created a party and a communication component.

More information: Using Conventions for Communication Component Names

Procedure
  1. Select theTransport Protocol:
    • HTTP 1.0
    • HTTPS
  2. The Message Protocolis RNIF 2.0.
  3. Select the Adapter Engineon the Integration Server, or select a non-centrally installed Adapter Engine.
  4. Select the Process Specification tab page.
  5. Depending on the scenario, select the Configuration Type:
    • Single-Action Asynchronous Request
    • Two-Action Asynchronous Request

Define Message Standard

  1. The Agency is RosettaNet.

    This selection refers to the Global Administering Authority Code.

  2. The Version is 
    2.0
    .

    The version identifier is different from the PIP version that is listed in the PIP dictionary on the RosettaNet website.

Define Locations

  1. Under Current, specify the <location ID> of the Integration Server.

    For example, enter New York.

  2. Under Partner, specify the <location ID> of the partner.

    For example, enter Frankfurt.

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.

Define PIP Details

  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 Business Transaction Activity, enter the value from the Activity Name column in the Business Activity Descriptions table in the PIP specification.

    RNIF protocol field:

    ServiceHeader-ProcessControl/TransactionControl/TransactionIdentity/GlobalTransactionCode

  4. 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.

    RNIF protocol field:

    ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/GlobalBusinessActionCode

  5. Under Current Role, enter the value from the FromRole element in the PIP specification.

    Take into account the PIP, activity, and action currently being executed.

    RNIF protocol field:

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

  6. Under Partner Role, enter the value from the ToRole element in the PIP specification.

    Take into account the PIP, activity, and action currently being executed.

    RNIF protocol field:

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

  7. Under Current Business Service Code, enter the value from the FromService element in the PIP specification.

    Take into account the PIP currently being executed, and the activity, and action.

    RNIF protocol field:

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

  8. Under Partner Business Service Code, enter the value from the corresponding ToService element in the PIP specification.

    Take into account the PIP currently being executed, and the activity, and action.

    RNIF protocol field:

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

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

    RNIF protocol field:

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

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 the origin and contents of the message is non-repudiable, choose Non-Repudiation of Origin and Content.
  4. If the receipt of the receipt acknowledgment must be non-repudiable, choose Non-Repudiation of Receipt Acknowledgment.

    A partner that has received a particular business action message cannot then deny receipt of the message.

    You must have selected Sign Action Message and Sign Signal Message.

    The action message and signal message are saved in the message archive.

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

    More information: Configuring Security in the RNIF 2.0 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 under Authenticationdepend on the transport protocol you have selected:
    • If a client authentication is required for the HTTP 1.1 transport protocol, select Client Authentication Required.

      Enter the user nameof the partner and the password, and confirm.

    • Select the authentication modefor the HTTPS transport protocol:
      • User name/password

        Enter the user nameof the partner and the password, and confirm.

      • Certificate Logon

        Select the keystore viewand the keystore entry.

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 the PI message header, 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.