Show TOC

Configuring the Sender RNIF 1.1 Adapter for RequestsLocate this document in the navigation structure

Use

You use this adapter in the Single-Action Initiator and Two-Action Initiatorscenarios. The partner uses this adapter to initiate message exchange with the Integration Server.

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

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

Prerequisites

You have created a party and a communication component.

More information: Using Conventions for Communication Component Names

Procedure
  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. Depending on the scenario, select the Configuration Type.
    • Single-Action Asynchronous Request
    • Two-Action Asynchronous Request

Define Message Protocol Specific Information

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

In the case of inbound RNIF messages, the RNIF protocol fields are validated against the respective fields in the communication channel configuration. The process name and transaction name are checked:

If the adapter is unable to successfully validate a field against the configuration in the channel, a general exception signal is sent to the partner.

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

    For example, enter Notify of Purchase Order Update for PIP3A7.

    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 Current Business Service Code, enter the value from the Network Component in FSVcolumn 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 or Initiator Service.

    RNIF protocol field:

    ServiceHeader-ProcessControl/ServiceRoute/toService.BusinessServiceDescription/GlobalBusinessServiceCode

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

    The value corresponds to the role assumed by the partner in the PIP.

    For example, enter Seller Service or Responder Service.

    RNIF protocol field:

    ServiceHeader-ProcessControl/ServiceRoute/fromService.BusinessServiceDescription/GlobalBusinessServiceCode

  5. Under Supply Chain Code, enter the value of the Partner Description element from the RosettaNet receipt acknowledgment specification document.

    Enter a value from the entity list for the GlobalSupplyChainCode element in the RosettaNet Receipt Acknowledgement Message guideline. 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

    More information: Supply Chain Code

Define PIP Information

In the case of inbound RNIF messages, the RNIF protocol fields are validated against the respective fields in the communication channel configuration. The Code and Requesting Action fields are checked:

If the adapter is unable to successfully validate a field against the configuration in the channel, a general exception signal is sent to the partner.

  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, enter V020. 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 corresponds to the role assumed by the Integration Server in the PIP.

    For example, enter Seller or Responder.

    RNIF protocol field:

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

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

    The value corresponds 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

Define Message Exchange Controls

  1. Under Number of Retries, specify how often the partner can attempt to resend messages.

    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. 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 before receipt, select Sign Action Message.
  2. If you want the signal message to be signed before it is sent, 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.

    More information: Non-Repudiation

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

    More information: Configuring Security in the RNIF 1.1 Adapter

Define Transport Parameters

  1. Select the Source 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 Authentication depend 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 of the partner and the Password, and confirm.

      More information: Client Authentication

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

        Enter the User Name and Password, and confirm.

        This information must be provided by the partner.

      • Certificate Logon

        Under Keystore View, select the path to the keystore entries of the private key of the partner. Example: SslService

        Under Keystore Entry, enter the name of the private key of the partner. Example: SslCredentials

Define Inbound Security Checks

  1. Select the HTTP Security Levelfor inbound messages:
    • HTTP
    • HTTPS without client authentication
    • HTTPS with client authentication

More information: SAP NetWeaver Process Integration Security Guide under Communication   → Network and Transport Layer Security, read section HTTP and SSL under Enforcing HTTP Security for Incoming Messages.

Define Adapter-Specific Message Properties

  1. Select the Advanced tab page.
  2. To save adapter-specific attributes in the message header of the PI message, select SetAdapter-Specific Message Properties.
  3. To apply 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.