Systems, Applications, and Products (SAP) for data processing is an industry leading enterprise software solution that is widely used among 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.
...
- Download and install WSO2 ESB by following the instruction in Getting Started.
Download the
sapidoc3.jarandsapjco3.jarmiddleware libraries from the SAP support portal and copy those libraries to the<ESB_HOME>/repository/components/libdirectory.Info title Note You need to have SAP login credentials to access the SAP support portal.
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.
Linux 32-bit
Copy the Linux native SAP jco library libsapjco3.soto<JDK_HOME>/jre/lib/i386/server.Linux 64-bit
Copy the Linux native SAP jco library libsapjco3.soto<JDK_HOME>/jre/lib/amd64.Windows
Copy the Windows native SAP jco library sapjco3.dllto<WINDOWS_HOME>/system32.Create a directory named
sapin the<ESB_HOME>/repository/conf/directory and provide access rights to read the properties files you will save in it later.Copy the following SAP endpoint property files to the
<ESB_HOME>/repository/conf/sapdirectory. You need to have two property files, one at the server-end and the other at the client-end to communicate with an external SAP endpoint using IDoc or BAPI.Info .
*.dest: This is where we keep SAP endpoint parameters when WSO2 ESB should act as a client to an external SAP endpoint.*.server: This is where we keep SAP endpoint parameters when WSO2 ESB should act as a server to an external SAP endpoint.
- Start the ESB using the
-Djava.library.pathswitch to specify the location of your SAP jco library.
For example./wso2server.sh -Djava.library.path=/usr/lib/jvm/jre1.7.0/lib/i386/server/
...
Following are descriptions of the proxy level listener parameters that can be defined in a proxy configuration:
| Parameter | Description |
|---|---|
transport.sap.serverName | The name of the server containing the JCO server configuration. |
transport.sap. enableErrorListener | Set this to enable the default error listener. If this is used together with the transport.sap. customErrorListener parameter, the custom error listener will be used. |
transport.sap. enableTIDHandler | Set this to enable the transaction handler to handle transactions that are received from a SAP system. Transactional applications must provide a custom implementation using the transport.sap. customTIDHandler parameter. |
transport.sap. customTIDHandler | The fully qualified class name for the custom TID handler implementing JCoServerTIDHandler. |
transport.sap.connections | The number of registered connections managed by the server instance. The default value is 1 and the maximum value is 100. |
transport.sap. customErrorListener | The fully qualified class name for the custom error listener implementing JCoServerErrorListener. |
transport.sap. customExceptionListener | The fully qualified class name for the custom exception listener implementing JCoServerExceptionListener. |
Following are descriptions of the SAP client properties that can be defined in the message context with axis2-client scope:
| Property | Description |
|---|---|
transport.sap.xmlMapper | The key of custom IDOC XML mapper to use. This key should be defined in the transport.sap. customXMLMappers parameter. If no key is specified the default IDoc XML mapper will be used. |
transport.sap. xmlParserOptions | The options for the default IDoc XML parser to be used in the default IDoc XML mapper. Multiple options can be combined using the bitwise OR "|" operator. The possible parser options are as follows: PARSE_ACCEPT_ONLY_XMLVERSION_10 3328 |
...