This documentation is for WSO2 Enterprise Service Bus version 4.8.0 . View documentation for the latest release.

All docs This doc
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

SAP software solutions are widely used among product and process oriented enterprises for finance, operations, HR and many other aspects of the business. SAP ERP solutions provide reliable and efficient platforms to build and integrate enterprise or business-wide data and information systems with ease.

One of the drawbacks however is vendor lock-in and the relative inflexibility of SAP solutions to align itself with the business model or customization required. Having understood these challenges, SAP software vendors are moving towards exposing their solutions to SOA.

WSO2 ESB on the other hand leverages the best of both worlds by supporting technologies along with native SOA integration technologies. It has the capability to connect existing SAP based solutions of an enterprise with other data/business oriented systems and to mix-and-match user 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.

This section describes how to set up WSO2 ESB in a SAP environment, how to install the SAP JCo middleware library, SAP Intermediate Document (Idoc) and Business Application Programming Interface (BAPI) adapters.

Installing WSO2 SAP Adapter

The WSO2 SAP adapter is written as a transport for WSO2 ESB. The relevant jar is org.wso2.carbon.transports.sap-VERSION.jar (e.g. org.wso2.carbon.transports.sap-1.0.jar). Follow the steps below to install and set up.

1. Download and install WSO2 ESB using instruction given in section Getting Started.

2. Download the sapidoc3.jar and sapjco3.jar middleware libraries from SAP support at http://service.sap.com/connectors, and copy them to <ESB_HOME>/repository/components/lib directory.

3. Copy the native SAP jco library to the system path. Pick the system path relevant to your operating system from the list below.

Linux 32-bit

Copy the Linux native SAP jco library (libsapjco3.so) to <JDK_HOME>/jre/lib/i386/server.

Linux 64-bit

Copy the Linux native SAP jco library (libsapjco3.so) to <JDK_HOME>/jre/lib/amd64.

Windows

Copy the Windows native SAP jco library (sapjco3.dll) to <WINDOWS_HOME>/system32.

4. Copy the SAP endpoint property files to <ESB_HOME>/repository/conf/sap. When communicating with an external SAP endpoint using IDoc or BAPI, there are two property files for server-side and client-side as follows:

  • *.dest - SAP endpoint properties when the ESB acts as the client to an external SAP endpoint.
  • *.server - SAP endpoint properties when the ESB acts as the server to an external SAP endpoint.

The SAP client and server properties file should be available with its name according to the property transport.sap.serverName for server, and the endpoint name for the destination. The next section explains this in detail.

5. Start the ESB using the -Djava.library.path switch 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/

Configuring WSO2 SAP Adapter

As noted earlier, the SAP adapter was written as a new transport for the WSO2 ESB. This transport consists of two parts as follows.

  • BAPI/RFC transport
  • IDoc transport

Just as a normal transport, define each of these transports' receiver/sender configurations in <ESB_HOME>/repository/conf/Axis2/axis2.xml file. Examples are given below for your reference.

BAPI/RFC Adapter

transportSender:

<transportSender name="bapi" class="org.wso2.carbon.transports.sap.SAPTransportSender"/>

transportReceiver:

<transportReceiver name="bapi" class="org.wso2.carbon.transports.sap.SAPTransportListener"/>
IDoc Adapter

transportSender:

<transportSender name=”idoc” class="org.wso2.carbon.transports.sap.SAPTransportSender"/>

transportReceiver:

<transportReceiver name=”idoc” class="org.wso2.carbon.transports.sap.SAPTransportListener"/>

The table below summarizes how to define a SAP endpoint and a proxy service.

 Endpoint ConfigurationProxyService Configuration

BAPI/RFC adapter

<endpoint name="sapbapiendpoint">
  <address
 uri="bapi:/JCOCLIENT01"/>
</endpoint>

The SAP endpoint client property file should be in <ESB_HOME>//repository/conf/sap/JCOCLIENT01.dest.

<proxy name=”sapbapiproxy” transports=”bapi”/>
//in,out,fault Sequence
  <parameter name="transport.sap.serverName">  
    JCOSERVER01
  </parameter>
// other parameters
</proxy>

SAP endpoint server property file should be in <ESB_HOME>/repository/conf/sap/JCOS ERVER01.server

IDoc adapter
<endpoint name="sapidocendpoint">
   <address
 uri="idoc:/JCOCLIENT01"/>
</endpoint>

The SAP endpoint client property file should be in <ESB_HOME>/repository/conf/sap/JCOCLIENT01.dest

<proxy name=”sapidocproxy”
 transports=”idoc”/>

//in,out,fault Sequence
  <parameter
 name="transport.sap.serverName">

    JCOSERVER01

  </parameter>

// other parameters
</proxy>

SAP endpoint server property file should be in <ESB_HOME>/repository/conf/sap/JCOSERVER01.server

JCo parameters

You have to specify some properties when communicating with a SAP system using the JCo middleware library. They are specified using the *.dest and *.server properties files in <ESB_HOME>/repository/conf/sap directory. The two tables below define the properties and their possible values.

Server properties (*.server property file)

PropertyDescription

gwhost

Gateway host

gwserv

Gateway service

progid

Program ID of the server

trace

You can enable or disable the RFC trace
paramsArbitrary parameters for RFC library

snc_myname

SNC name

snc_qop

SNC level of security (1-9)

snc_lib

Path to the SNC library

profile_name

Name of the profile file used during start-up

unicode

Determines whether or not you connect in unicode

mode (1=true, 0=false)

max_startup_delay

Maximum server start-up delay time in seconds

Client properties (*.dest property file)

PropertyDescription

client

Client logon

user

User logon

alias_user

Alias user name

passwd

Logon password

lang

Logon language

sysnr

R/3 system number

ashost

R/3 application server

mshost

R/3 message server

gwhost

Gateway host

gwserv

Gateway service

r3name

R/3 name
groupGroup of application servers

tpname

Program ID of external server program
tphostHost of external server program

type

Type of remote host (3=R/3, E=External)
codepageInitial code page for logon

use_sapgui

Use remote SAP graphical user interface

mysapsso2

Use the specified SAP cookie version 2 as the logon ticket
grt_dataAdditional data for GUI

use_guihost

Host to which the remote GUI is redirected

use_guiserv

Service to which the remote GUI is redirected
use_guiprogidProgid of the server that starts the remote GUI
snc_partnername

SNC partner name (for example, CN=B20, O=SAP-AG, C=DE\) snc_mode

snc_mode

SNC mode (0 or 1)

snc_qop

SNC level of security (1-9)

snc_myname

SNC name; overrides default SNC partner
snc_libPath to the library

Dest

R/2 destination

saplogon_id

SAPLOGON string on 32-bit Windows

extiddata

Data for external application (PAS)

extidtype

Type of external authentication (PAS)

x509cert

Use the specified X509-certificate as the logon ticket

msserv

R/3 port number of message server

profile_name

Profile name used for shared memory communication

idle_timeout

Idle timeout for the connection

ice Ignore

RFC library character conversion errors (1 or 0)

logon

Enable or disable logon check at open time (1 or 0)

trace

Enable or disable RFC trace (1 or 0)

abap_debug

Enable ABAP debugging (1 or 0)

getsso2

Get or do not get a SSO ticket after logon (1 or 0)

toupper

Enable or disable uppercase character conversions for logon

Troubleshooting

Given below are general troubleshooting guides.

How to handle the Server unknown error

An example of this error message is as follows:

[2010-10-25 19:53:00,405] ERROR - DefaultErrorListener Exception occured on :
JCOSERVER01 and connection : null
com.sap.conn.jco.JCoException: (129) JCO_ERROR_SERVER_STARTUP: Server startup
failed at Mon Oct 25 19:53:00 IST 2010.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown,
c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=JCOSERVER01 GWHOST=cynthia GWSERV=sapgw00
ERROR service 'sapgw00' unknown
TIME Mon Oct 25 19:53:00 2010
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -3
MODULE nixxsl.cpp
LINE 184
DETAIL NiSrvLGetServNo: service name cached as unknown
COUNTER 2
at com.sap.conn.jco.rt.DefaultServer.openConnection(DefaultServer.java:1168)
at com.sap.conn.jco.rt.DefaultServer.openConnections(DefaultServer.java:1057)
at com.sap.conn.jco.rt.DefaultServer.adjustConnectionCount(DefaultServer.java:1004)
at
com.sap.conn.jco.rt.DefaultServerManager$DispatcherWorker.run(DefaultServerManager.java:
299)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sap.conn.jco.JCoException: (129) JCO_ERROR_SERVER_STARTUP: Could
not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=JCOSERVER01 GWHOST=cynthia GWSERV=sapgw00
ERROR service 'sapgw00' unknown
TIME Mon Oct 25 19:53:00 2010
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -3
MODULE nixxsl.cpp
LINE 184
DETAIL NiSrvLGetServNo: service name cached as unknown
COUNTER 2
at
com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.accept(MiddlewareJavaRfc.java:2135)
at com.sap.conn.jco.rt.ServerConnection.accept(ServerConnection.java:380)
at com.sap.conn.jco.rt.DefaultServer.openConnection(DefaultServer.java:1149)
© 2012 WSO2
.. 4 more
Caused by: RfcException: [null]
message: Connect to SAP gateway failed
Connect parameters: TPNAME=JCOSERVER01 GWHOST=cynthia GWSERV=sapgw00
ERROR service 'sapgw00' unknown
TIME Mon Oct 25 19:53:00 2010
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -3
MODULE nixxsl.cpp
LINE 184
DETAIL NiSrvLGetServNo: service name cached as unknown
COUNTER 2
Return code: RFC_FAILURE(1)
error group: 102
key: RFC_ERROR_COMMUNICATION
at com.sap.conn.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:255)
at com.sap.conn.rfc.engine.RfcIoControl.ab_rfcaccept(RfcIoControl.java:43)
at com.sap.conn.rfc.api.RfcApi.RfcAccept(RfcApi.java:41)
at
com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.accept(MiddlewareJavaRfc.java:2121)
... 6 more

The solution is to add your SAP server names to /etc/services file with their relevant ports. For example, the following lines can be added as relevant to the example error given above.

sapgw00 3300/tcp
sapgw01 3301/tcp
  • No labels