SAP Integration

Systems, Applications, and Products (SAP) for data processing is an industry leading enterprise software solution that is widely used in product and process oriented enterprises for finance, operations, HR and many other aspects of a business. SAP ERP solutions provide reliable and efficient platforms to build and integrate enterprise or business-wide data and information systems with ease. 

The ESB profile of WSO2 Enterprise Integrator (WSO2 EI) leverages the best of both worlds by providing the integration layer so that an existing SAP R/3 based solutions of an enterprise can be integrated with other data/business oriented systems so that you can mix-and-match requirements with minimal effort. As a result, enterprises can keep parts of their systems independent of SAP and extensible for many other systems, solutions and middleware.

The WSO2 SAP adapter is shipped with the ESB profile and is implemented as a transport for the ESB profile. This is provided in the <EI_HOME>/wso2/components/plugins directory as org.wso2.carbon.transports.sap-VERSION.jar (e.g. org.wso2.carbon.transports.sap_1.0.0.jar).

The WSO2 SAP adapter has full IDoc and experimental BAPI support. It uses the SAP JCO library as the underlying framework to communicate with SAP.  This section describes how to set up the ESB profile in a SAP environment, how to install the SAP JCo middleware library, SAP Intermediate Document (IDoc) and Business Application Programming Interface (BAPI) adapters.

Installing the SAP Adapter

Follow the instructions below to install and set up the SAP adapter.

1. Download WSO2 EI and install the ESB Profile by following the instruction in the Installation Guide.

2. Download the sapidoc3.jar and sapjco3.jar middleware libraries from the SAP support portal and copy those libraries to the <EI_HOME>/lib directory.

3. Download the native SAP JCo library and copy it to the system path. You need to select the system path applicable to your operating system as described below.

4. Create a directory named conf in the <EI_HOME>/conf/ directory.

5. Create a directory named sap within the conf directory that you created and provide access rights to read the properties files you will save in it later.

6. Copy the following SAP endpoint properties files to the <EI_HOME>/conf/sap/ directory. You need to have two properties files, one at the server-end and the other at the client-end to communicate with an external SAP endpoint using IDoc or BAPI.

   • *.dest : This is where we store SAP endpoint parameters when the ESB Profile of WSO2 EI is configured as a client to an external SAP endpoint.  

   • *.server : This is where we store SAP endpoint parameters when the ESB Profile of WSO2 EI is configured as a server to an external SAP endpoint.

   For details on creating the properties files and defining the relevant properties, see Setting up the Client Configuration File and Setting up the Server Configuration File.

7. Start the ESB profile of WSO2 EI using the -Djava.library.path switch to specify the location of your SAP jco library. 
   For example, you can execute the following command to start the ESB Profile:

   ./integrator.sh -Djava.library.path=/usr/lib/jvm/jre1.7.0/lib/i386/server/

Setting up the Client Configuration File

To setup the ESB profile as a client to a SAP system you need to create the *.dest properties file and define the relevant properties. The following table lists the properties and the description of each property that should be specified in the *.dest properties file.