Syntax of Parameter for Secure Communication

The parameter specifies where internal communication in PI should use secure communication (HTTPS) instead of plain HTTP. The parameter has the following syntax:

<secure_connections> ::= <entry> ("," <entry>)*

<entry>                  ::= <usecase> ( "(" <component_list> ")" )?

<usecase>             ::= "messaging" | "all"

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

Basically, it is a comma-separated list of use cases with an optional list of components. Currently there are two use cases:

?      Messaging

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

?      All

Includes all communications.

If only the use case is given, the setting applies to all components in the PI landscape. It is also possible to restrict the selection to specific PI components by adding a list of SLD instance names in parentheses after the use case. In this case, the setting only applies for communications which involve one of the listed instances.

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

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

If you are in doubt about the correct names, look them up in the SLD.

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

Possible Applications:



Integration Repository


Integration Directory


Adapter Engine


Runtime Workbench


Mapping Runtime


Use the system number instead of the SID.

Example 1: =

No secure communication is used (only standard HTTP); this is the default setting.

Example 2: = messaging

All components use secure communication for messaging.

Example 3: = 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.

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.