Show TOC Start of Content Area

Procedure documentation Configuring a Communication Channel  Locate the document in its SAP Library structure

Use

You use this topic to configure a communication channel for enabling a partner to initiate a message transfer to SAP XI. This information is specific to the Single-Action Responder configuration type (see Single-Action Responder).

Prerequisites

You have created a communication channel. For more information, see Assigning Communication Channels.

Recommendation

We recommend that you use the communication channel template when creating a communication channel. The template is provided as part of the business package for RNIF.

If you want to enable security settings in the channels, you have also performed the steps described in Security Services in the RNIF Adapter.

Procedure

...

The following configuration activities are performed in the Integration Server:

       1.      From the Integration Builder, go to Integration Directory.

The Integration Builder: Configuration Time screen appears.

       2.      From the navigation bar choose the communication channel.

       3.      Choose the Parameters tab, and indicate the values in the following sections:

Communication Channel Types

Field

Action

Adapter Type

Choose RNIF11

Sender or Receiver

Choose Receiver

Transport Protocol

Choose HTTP 1.1 or HTTPs

The value you choose here will determine the values you indicate in the Authentication section below.

Message Protocol

Choose RNIF 1.1

Adapter Engine

Choose the name of an adapter engine on the Integration Server or a non-central Adapter Engine.

Process Specification Tab Page

Configuration Type

Choose Single-Action Asynchronous Request.

Message Protocol Specific Information

The values you enter below are referenced from the PIP Specification document for the PIP you intend to use. The outgoing action message is filled using the values you specify in the channels.

If the business situation require you to, you can further modify these values.

The values in these fields are used to fill in the RNIF Protocol Fields for all outbound action or signal messages. In case of inbound RNIF messages, the RNIF Protocol Fields are validated against the respective fields in the communication channel configuration. Only the following fields are validated:

·         Process Name

·         Transaction Name

·         Message Version (Validated only for action messages).

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.

Field

Action

RNIF Protocol Field

Process Name

Enter the name from title page of the PIP Specification document.

Example: Asynchronous Notification for PIP0C1

ServiceHeader- ProcessControl/ ProcessIdentity/ GlobalProcessCode

Transaction Name

Enter the value from the Activity Name column of the Business Activity Descriptions table in the PIP Specification document.

Example: Notify of remittance advice

ServiceHeader-ProcessControl/ TransactionControl/ TransactionIdentity/ GlobalTransactionCode

Message Version

Enter the value from the PIP Version Identifier available on the title page of the PIP Specification document.

Example: If the PIP Version Identifier in the Specification document is V02.02, the Version is V0202.

ServiceHeader- ProcessControl/ TransactionControl/ ActionControl/ ActionIdentity/ VersionIdentifier

Current Business Service Code

Enter the value from the Network Component in FSV column of the Network Component Specification table in the PIP Specification document. The value corresponds to the role assumed by XI in the PIP.

Examples: Buyer Service, Initiator Service

ServiceHeader- ProcessControl/ ServiceRoute/ fromService/ BusinessServiceDescription/ GlobalBusinessServiceCode

Partner Business Service Code

Enter the value from the Network Component in FSV column of the Network Component Specification table in the PIP Specification document. The value should correspond to the role assumed by Partner in the PIP.

Examples: Seller Service, Responder Service

ServiceHeader- ProcessControl/ ServiceRoute/ toService/ BusinessServiceDescription/ GlobalBusinessServiceCode

Current Classification Code

Enter the value from the entity list specified for the GlobalPartnerClassification Code element in the RosettaNet Service Header Message guideline. The guideline is part of the RNIF 1.1 Specifications document. Choose the most appropriate value corresponding to the currently executing PIP, Activity, and Action in the PIP Specification document. The field describes the function of XI in the supply chain.

Examples: Product Supplier, Supplier

ServiceHeader- ProcessControl/ TransactionControl/ ActionControl/ PartnerRoute/ fromPartner. PartnerDescription/ GlobalPartner ClassificationCode

Partner Classification Code

Enter the value from the entity list specified for the GlobalPartnerClassification Code element in the RosettaNet Service Header Message guideline. The guideline is part of the RNIF 1.1 Specifications document. Choose the most appropriate value corresponding to the currently executing PIP, Activity, and Action in the PIP Specification document. The field describes the function of Partner in the supply chain.

Examples: Product Supplier, Distributor

ServiceHeader- ProcessControl/ TransactionControl/ ActionControl/ PartnerRoute/ toPartner. PartnerDescription/ GlobalPartner ClassificationCode
PIP Information

The fields in this section describe adapter metadata. For more information about adapter development, see Adapter and Module Development.

Configure these fields only if you are adapting to partner implementations that deviate from specified RosettaNet standards.

The values in these fields are used to fill in the RNIF Protocol Fields for all outbound action or signal messages. In case of inbound RNIF messages, the RNIF Protocol Fields are validated against the respective fields in the communication channel configuration. Only the following fields are validated:

·         Code

·         Requesting Action.

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.

Field

Action

RNIF Protocol Field

Code

Enter PIP standard code.

Example: 3A7

ServiceHeader- ProcessControl/ ProcessIdentity/ GlobalProcessIndicatorCode

Version

Enter the PIP Version Identifier available on the title page of the PIP Specification document.

Example: If the PIP Version Identifier in the Specification document is V02.02, the Version is V0202.

ServiceHeader- ProcessControl/ ProcessIdentity/ VersionIdentifier

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.

Example: Asynchronous Test Notification Action

ServiceHeader- ProcessControl/ TransactionControl/ ActionControl/ ActionIdentity/ GlobalBusinessActionCode

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 XI in the PIP.

Examples: Buyer, Initiator

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

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 Partner in the PIP.

Examples: Seller, Responder

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

Document Schema Specification

Enter the value of the DTD for the corresponding action from the XI Integration Builder.

Configure this field only for the receiver channel.

Example:

1_MS_R01_02_Asynchronous TestNotification.dtd

URI reference to external DTD as system identifier, formed in DOCTYPE - XML processing instruction.
Message Exchange Controls

Field

Action

Number of Retries

You can use the default value displayed or enter a new value from the Retry Count column of the Business Activity Performance Controls table in the PIP Specification document. The value is the number of times the action message is re-transmitted before the adapter receives a signal from the partner.

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.

Configure this attribute only for the receiver channel.
Security Policy

Field

Action

Sign Action Message

Select or deselect Sign Action Message.

Your selection will determine whether the action message is required to be signed before sending.

Sign Signal Message

Select or deselect Sign Signal Message.

Your selection will determine whether the signal message is required to be signed before receiving.

Non-Repudiation

Select or deselect Non-Repudiation.

To enable Non-Repudiation, you must also select the Sign Message option.

Target Tab Page

Transport Parameters

Field

Action

URL

Enter the partner address to which the adapter sends the RosettaNet Signal Message.

Persist Duration

You can use the default value displayed or enter a new time in format provided.
Authentication

The values you enter here are determined by the Transport Protocol entered earlier.

If you choose HTTP 1.1, the following fields are available:

Field

Action

Client Authentication Required

Select or deselect Client Authentication Required.

User Name

Enter the value provided by the partner.

Password

Enter the value provided by the partner.

If you chose HTTPs, the following fields are available:

Field

Action

Authentication Mode

Choose User Name/Password or Certificate Logon

The value you choose here will determine additional details you need to enter.

If you chose User Name/Password, the following fields are available:

Field

Action

User Name

Enter the value provided by the partner.

Password

Enter the value provided by the partner.

If you chose Certificate Logon, the following fields are available:

Field

Action

Keystore View

Enter the path to keystore entries in the J2EE engine containing private key of the XI party.

Example: SslService

Keystore Entry

Enter the name of private key of the XI party.

Example: SslCredentials

 

See also:

Single-Action Initiator

 

 

 

End of Content Area