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 Initiator configuration type (see Single-Action Initiator).

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

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

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 name of an adapter engine on the Integration Server or a noncentral 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.

If the business requirements expect you to change these values, 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.

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: Notify of Purchase Order Update for PIP3A7

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

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/ toService. 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/ fromService. BusinessServiceDescription/ GlobalBusinessServiceCode

Supply Chain Code

Enter the value from the PartnerDescription element in the RosettaNet Receipt Acknowledgement Specifications document.

Enter the value from the entity list specified for the GlobalSupplyChainCode element in the RosettaNet Receipt Acknowledgement Message guideline. The guideline is part of the RNIF 1.1 Specifications document.

Example: Electronic Components

ReceiptAcknowledgment Payload -fromRole. PartnerRoleDescription/ PartnerDescription/ BusinessDescription/ GlobalSupplyChainCode

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 corresponds to the role assumed by XI in the PIP.

Examples: Seller, Responder

ServiceHeader- ProcessControl/ TransactionControl/ PartnerRoleRoute/ toRole. 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 corresponds to the role assumed by Partner in the PIP.

Examples: Buyer, Initiator

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

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 used to restrict the number of retries from the partner.

Receipt Acknowledgement

Strong or Weak. Configure this attribute only for the sender 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 receiving.

Sign Signal Message

Select or deselect Sign Signal Message.

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

Non-Repudiation

Select or deselect Non-Repudiation.

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

Source 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 choose 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 choose 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 choose Certificate Logon, the following fields are available:

Field

Action

Keystore View

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

Example: SslService

Keystore Entry

Enter the name of private key of the XI party.

Example: SslCredentials

Advanced Tab Page

Adapter-Specific Message Properties

Field

Action

Set Adapter-Specific Message Properties

Select or deselect Set Adapter-Specific Message Properties.

Your selection determines whether attributes are available for selection.

If you choose Set Adapter-Specific Message Properties, the following fields are available:

Field

Technical Name

Action

Process Instance Identifier

Proc Inst Identifier

Select or deselect Process Instance Identifier.

Denotes a unique alphanumeric identifier that represents a specific instance of a business process.

Message Identifier

Message Identifier

Select or deselect Message Identifier.

Denotes a unique alphanumeric identifier that represents the message for tracking. This identifier is unique within the context of the message sender.

Document Identifier

Document Identifier

Select or deselect Document Identifier.

Denotes a unique alphanumeric identifier that represents the PIP business document.

Document Date Time Stamp

Document Date Time

Select or deselect Document Date-Time Stamp.

Denotes the date and time when the message is sent to the partner.

 

See also:

Single-Action Responder

 

 

 

End of Content Area