Installation and Connectivity Options

Runtime Engines

SAP NetWeaver PI provides the following runtime engines:

• Integration Engine

  Based in AS ABAP and contains the following adapters for connectivity: IDoc (ABAP-based), XI (connectivity to proxy runtime), HTTP (ABAP-based), as well as the connectivity to systems or applications based on Web Services Reliable Messaging (WS channel).

  More information: Connectivity Options Using SAP NetWeaver PI Standard Installation under Integration Engine-Based Message Processing .

• Advanced Adapter Engine

  Based on AS Java and provides the following adapters: RFC Adapter, SAP Business Connector Adapter, File/FTP Adapter, JDBC Adapter, JMS Adapter, SOAP Adapter, Marketplace Adapter, Mail Adapter, RNIF Adapter, CDIX Adapter, IDoc Adapter (AAE) (adapter type DOC_AAE), HTTP Adapter (AAE) (adapter type HTTP_AAE).

• Business Process Engine

  Based in AS ABAP and comes into play when you execute scenarios that contain integration processes (cross-component Business Process Management).

  More information: Cross-Component Business Process Management

The runtime engines can be installed and used in different ways, which will be shown in the next section.

Installation Options

Basically, you can install SAP NetWeaver PI in the following ways:

• SAP NetWeaver PI (dual-stack installation)

  This installation option is technically based on both AS ABAP and AS Java and comprises the complete functional range of SAP NetWeaver PI.

  It provides tools for designing and configuring integration content (Enterprise Services Repository, Integration Directory and System Landscape Directory), as well as runtime engines.

  In particular, when you choose this option, as host for the runtime engines you install the Integration Server .

  The Integration Server hosts the following runtime engines:

  • Integration Engine

  • Advanced Adapter Engine

  • Business Process Engine

  If in a specific scenario, the Integration Engine or Advanced Adapter Engine is involved as the runtime component, depends on the actual used adapters.

  In addition to using the Advanced Adapter Engine as part of the Integration Server (the central Adapter Engine), there is also the option to use the Advanced Adapter Engine stand-alone, next to the Integration Server (non-central Advanced Adapter Engine).

  Note

  As an additional option, you can use the Adapter Engine (Java SE). This option is only supported for compatibility reasons. It hosts only a subset of the adapter functionality and has fewer security and monitoring features.

  More information: Connectivity Options Using SAP NetWeaver PI Standard Installation

  Technically, this installation option is based on both AS ABAP and AS Java.

• Advanced Adapter Engine Extended

  This installation option is based on AS Java only.

  It provides tools for designing and configuring integration content (Enterprise Services Repository, Integration Directory and System Landscape Directory), as well as the Advanced Adapter Engine as runtime engine.

  Note

  However, when using this installation option, the functional range of these tools is slightly restricted as compared to an SAP NetWeaver PI installation.

  More information: Connectivity Options Using Advanced Adapter Engine Extended

• SAP Partner Connectivity Kit (SAP PCK)

  Enables smaller business partners or subsidiaries to integrate their system landscape with an SAP NetWeaver Process Integration installation of their business partner or head office.

  More information: SAP Partner Connectivity Kit

The following figure summarizes the connectivity and installation options of SAP NetWeaver PI.