Show TOC

Adapter Engine (Java SE)Locate this document in the navigation structure

Purpose

The Adapter Engine (Java SE) connects the Integration Service with third-party systems. Using the various adapters in the Adapter Engine, XML and HTTP-based messages can be converted to the specific protocol and format required by such systems, and the other way around.

In principle, you connect external systems to the Integration Server using the adapters that are installed centrally or non-centrally in the Adapter Engine. You configure this centrally by using the Integration Directory. Additional functions include an enhanced monitoring and increased downtime security due to the Java-based cluster operation of the Adapter Engine.

The plain J2SE Adapter Engine provides some of these adapters as a standalone version with restricted functions for operating systems that do not support the SAP J2EE server, but that do have JDK 1.3.1 or higher. Therefore, you should only use the plain J2SE Adapter Engine if the platform prerequisites do not allow you to use the J2EE-based Adapter Engine.

You installthe individual adapters either separately or together, and then configurethem using their own configuration interface.

For more information on security settings for the adapter, see the security guide for SAP NetWeaver Process Integration in the chapter Adapters Running in the Adapter Engine (Java SE).

Implementation Considerations

The Adapter Engine (Java SE) (referred to below as the Adapter Engine) is a separate software component that you must install later.

Its features are the same as those of the Adapter Engine shipped with SAP XI 2.0. You can copy the adapter configurations of the XI 2.0 Adapter Engine to the XI 3.0 Adapter Engine without changes. However, in order to be able to use all the XI 3.0 message format options, you must change the address parameters in the sender adapter configurations as described below. You then copy the XI 2.0 adapter configurations (see the section Upgrading the Installation of an XI 2.0 Adapter Engine in Installation).

Features

Depending on the configuration, the adapters can be used to do the following:

  • Exchange data with external systems using a file interface or an FTP server (file/FTP adapter)
  • Communicate with messaging systems using the JMS API (JMS adapter)
  • Access databases using JDBC (JDBC adapter)
  • Communicate with clients and providers of Web Services using SOAP (SOAP adapter)

An important distinction to be made here is whether an adapter is a sender adapter (converts data from external systems) or an receiver adapter (converts data from the Integration Engine).

To begin functioning, each sender or receiver adapter must be appropriately installed and configured, and then started.

You can use different adapters simultaneously or different configurations of the same adapter. For this purpose, it may be necessary for you to change the installation parameters to enhance the installation.