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
You have created a party and a communication component.
More information: Using Conventions for Communication Component Names
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.
For example, enter Notify of Purchase Order Update for PIP3A7.
RNIF protocol field:
ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessCode
For example, enter Notify of remittance advice.
RNIF protocol field:
ServiceHeader-ProcessControl/TransactionControl/TransactionIdentity/GlobalTransactionCode
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
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
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.
For example, enter 3A7.
RNIF protocol field:
ServiceHeader-ProcessControl/ProcessIdentity/GlobalProcessIndicatorCode
For example, enter V020. Omit the period.
RNIF protocol field:
ServiceHeader-ProcessControl/ProcessIdentity/VersionIdentifier
For example, enter Asynchronous Test Notification Action.
RNIF protocol field:
ServiceHeader-ProcessControl/TransactionControl/ActionControl/ActionIdentity/GlobalBusinessActionCode
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
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
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.
The signal message (confirmation/exception) is sent before message processing on the Integration Server is complete.
The signal message (confirmation/exception) is not sent until confirmation has been received from the Integration Server.
Define Security Policy
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
More information: Configuring Security in the RNIF 1.1 Adapter
Define Transport Parameters
Define Authentication
Enter the User Name of the partner and the Password, and confirm.
More information: Client Authentication
Enter the User Name and Password, and confirm.
This information must be provided by the partner.
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
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
Unique alphanumeric ID for an instance of a business process.
Unique alphanumeric ID for the PIP business document.
Date and time that message is sent to partner.