Show TOC

Syntax of Parameter for Secure CommunicationLocate this document in the navigation structure

Use

The parameter com.sap.aii.connect.secure_connections specifies when internal communication in PI uses secure communication (HTTPS) instead of plain HTTP. The syntax is essentially a comma-separated list of use cases with an optional list of components, as described in the following.

Note

In addition to setting the parameter secure_connections , you also have to configure the HTTPS ports of the involved components in the Connections section of the exchange profile.

Example

com.sap.aii.connect.secure_connections =

If no values are specified for the parameter, no secure communication is used (only standard HTTP). This is the default setting.

Example

  • com.sap.aii.connect.secure_connections = messaging

    All components use secure communication for messaging.

  • com.sap.aii.connect.secure_connections = messaging, all

    Secure communication is used for messaging (on all systems) and for all connections.

Advanced Syntax

For more detailed control of the secure connections, the parameter also supports a more complex syntax:

com.sap.aii.connect.secure_connections = <usecase_entry> ("," <usecase_entry>)

The parameter can contain one or more use case entries, each separated by a comma. <usecase_entry> is a placeholder which is described in the following.

Syntax Elements

Description

<usecase_entry>

<usecase_entry> = <usecase> ("(" <component_list> ")" )?

A use case entry consists of the use case name and an optional list of components. The component list is added in parentheses after the use case name. If no component list is specified, the entry applies to all components.

(see below for a list of valid use case names)

<usecase>

There are the following use cases:

  • messaging

    Internal transport of payload messages between PI components (for example, between the Integration Server and adapters).

  • all

    Includes all communications.

  • browser

    Used for communication between Browser and PI components and tools.

  • CacheRefresh

    Used for cache refresh of the Adapter Engine. And for communication from the Adapter Engine to the Integration Directory.

  • hmi

    Used for cache refresh of the Adapter Engine. And for communication from the Integration Directory to the Adapter Engine. Also used for internal communication between Integration Directory and Enterprise Services Repository.

<component_list>

<component_list> = <sld_instance_name> (","<sld_instance_name>)*

The component list can contain one or more comma-separated SLD instance names.

<sld_instance_name>

The SLD instance names usually consist of the application name, the system ID, and the database host:

<sld_instance_name> = <application_id> "." <SID> "." <DBHOST>

To check the correct names, look them up in the SLD.

Note

The SLD instance name of the Integration Server uses the system number instead of the system ID <SID> .

<application_id>

You can specify the following applications:

Application

<application_id>

Enterprise Services Repository

repository

Integration Directory

directory

Adapter Engine

af

Runtime Workbench

rwb

Mapping Runtime or Integration Server

is

Note

Use the system number instead of the SID.
Example

Here is a more complex example of the detailed syntax:

com.sap.aii.connect.secure_connections = messaging, all(af.BXI.pwdf0591, af.Y6D.ld0050)

Secure communication is used for messaging (on all systems) and for all connections from or to the adapters on system BXI/pwdf0591 and Y6D/ld0050.