Connectivity Adapter Preference

This is a list of PI/PO adapters, sorted by the preferred way of communication from SAP PI point of view regarding reliability, architecture fit, monitoring and maintenance:

SAP Systems

  1. ABAP (XI) Proxy
    • synchronous & asynchronous communication
    • dynamic queue assignment
    • usage of acknowledgements
    • processing of (binary) attachments (PDF, JPG, ..)
    • usage of Forward Error Handling (FEH, ECH Error and Conflict Handler)
  2. IDoc (ALE)
    • asynchronous communication
    • usage of acknowledgements
    • SAP Business Workflow integration
  3. BAPI/RFC
    • synchronous & asynchronous communication
    • async communication not recommended (monitoring)
  4. File
    • for standard import programs
    • Integration via (S)FTP(s)/NFS

Non-SAP Systems

  1. SOAP/http
    • exchange XML messages via http(s)
    • synchronous & asynchronous communication
    • reliable async communication via WS-RM protocol
  2. JMS
    • exchange XML messages via queues
    • reliable asynchronous communication (exactly once/EOIO)
    • usage of drivers necessary (matching the JMS provider)
  3. JDBC
    • integrate database tables/views by reading/writing entries, call stored-procedures
    • usage of drivers necessary (matching the database vendor)
  4. File/FTP
    • exchange data (XML/CSV/Flat) via file systems/FTP Server
    • asynchronous communication
  5. Mail
    • integrate e-mail systems via smtp/imap/pop3 protocol
    • asynchronous communication (at most once)

J2SE Adapter Engine – Setup/Installation

How to use the J2SE Adapter Engine:
The J2SE AE aka “Adapter Engine (Java SE)” is still supported and being maintained by SAP. You can use it if you need a light-weight middleware component on any system close to database, JMS queue, WebService or NFS filesystem.
Mainly it is used to solve the UNIX-Windows NFS dilemma (you want to access a network drive but your PI/PO installation is in UNIX).
Another network/security use case is to install it into the DMZ and use the J2SE AE as a reverse proxy (application gateway) for inbound communication from the internet.

Here you go:

  1. Get J2SE software from SAP (Service Marketplace Alias /swdc -> Support Packages and Patches-> Browse -> SAP NetWeaver and complementary products -> SAP NetWeaver -> SAP NETWEAVER 7.4 -> Entry by Component -> PI Adapter Engine (Java SE) => Downoad XI CONNECTIVITY SE 7.40
  2. Download JRE (e.g. from http://www.oracle.com/technetwork/java/index.html according to the required version) – Java 7 works fine
  3. Install JRE and extract AE archive into file system (only archive com.sap.xi.techadapters.sda is needed)
  4. Copy file servlet.jar (can be downloaded e.g. from http://www.java2s.com/Code/Jar/s/Downloadservletjar.htm) into extracted folder tech_adapter
  5. Install Service under Windows/Unix (use admin rights “run as administrator” when executing the script)
  6. Start the Admin UI from Browser with default port 8200 and user sap password init
  7. Configure the channels you need and communicate via HTTP(S) to your PI/PO integration server

Btw: This approach basically exists since XI 2.0 and is still valid for PI/PO 7.5! See the official documentation: SAP Help.