Configuring the Sender RNIF 2.0 Adapter for Requests

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

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

Define Message Standard

The Agency is RosettaNet.
This selection refers to the Global Administering Authority Code.
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

Under Current, specify the <location ID> of the Integration Server.
For example, enter New York.
Under Partner, specify the <location ID> of the partner.
For example, enter Frankfurt.

Define Message Exchange Controls

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.
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 PIP Details

Under Code, enter the PIP standard code.
For example, enter 3A7.
Under Version, enter the PIP version.
The PIP version ID is on the title page of the PIP specification. It is shorter than the PIP version.

For example, the version ID is V02.02, and the PIP version is V02.02.01.
Under Business Transaction Activity, enter the value from the Activity Name column in the Business Activity Descriptions table in the PIP specification.
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.
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.
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.
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.
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.

Define Security Policy

If you want the action message to be signed before receipt, select Sign Action Message.
If you want the signal message to be signed before it is sent, select Sign Signal Message.
If the origin and contents of the message is non-repudiable, choose Non-Repudiation of Origin and Content.
This enables you to prove that the partner has sent a particular business action message. The partner cannot then deny that the message has been sent. The message is saved in the security archive.
If the receipt of the receipt acknowledgment must be non-repudiable, choose Non-Repudiation of Receipt Acknowledgment.
Make the entries for the certificates in the sender agreement.
More information: Configuring Security in the RNIF 2.0 Adapter

Define Transport Parameters

Select the Source tab page.
Under URL, enter the partner address to which the adapter is to send the RosettaNet signal message.
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

The specifications under Authentication depend 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.
  
  More information: Client Authentication
- Select the authentication mode for 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 Inbound Security Checks

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

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