The SAP integration nodes allow you to integrate your data flows with an SAP system in order to execute functions on the SAP system. This is done using the SAP Java Connector library (JCo), and allows you to configure nodes to create, read, update and extract data from an SAP system via remote function calls (RFCs).
Use of these nodes assumes a working knowledge of SAP BAPI functionality.
The following software components are required:
- A sapjco3.jar Java library, available to users of SAP.
- A sapjco3.dll Windows library, available to users of SAP.
- A libsapjco3.so Unix library, available to users of SAP.
- A working connection to an SAP instance, either via direct connection or via the SAPRouter application.
The sapjco3.jar and sapjco3.dll files can be obtained from the SAP Service Marketplace for users of SAP, which can be found at http://service.sap.com/connectors. You will need to login to the SAP Service Marketplace to access the download. The ERP nodes require SAP JCo 3.0.X.
Install the sapjco3.jar file in the following location:
<Data360Analyze site configuration directory>/site-<port>/lib/java
Install the sapjco3.dll file or the libsapjco3.so file in the following location:
<Data360Analyze site configuration directory>site-<port>/lib/<platform>
<platform>directory if it does not already exist. For example:
SAP nodes overview
The following four SAP integration nodes are provided with Data360 Analyze:
The preferred mechanism for integrating with a SAP system is to use the Extract ERP Metadata and ERP Connector nodes to execute remote functions. See the above node help pages for details on the interface, usage and limitations of these nodes.
Common connectivity properties
The ERP integration nodes require a connection to the SAP system and they share a set of common connectivity properties. Rather than setting these properties on each node, it is simpler to create a set of corresponding data flow/run properties that can be used to provide these property values to each of the SAP nodes which requires them.
To configure the connection properties:
- Select a connection type in the ConnectionType property. Choose from:
- Group/Server Selection
- Custom Application Server
- Depending on your chosen connection type, configure the remaining connection properties as per the following table, where:
- indicates that this property is required for this connection type
x - indicates that this property should not be set for this connection type
|ApplicationServer||Name of the SAP application server.||x|
|Group/Server||Group of SAP servers.||
|MessageServerHost||SAP message server host.||
|MessageServerPort||SAP message server port.||optional||
|SystemNumber||Instance Number||Two-digit system number of the SAP system (as seen in the SAP login window).||optional|
|R3Name||System ID of the SAP system.||optional|
Three-digit client number for the SAP system (as seen in the SAP login window).
In the SAP landscape, a client is an entity with independent information and data. The SAP client concept is based on the fact that an application service provider (ASP) must provide and administer all resources at a minimal cost, which is quite challenging in a multiple customer-client environment.
If connecting via an SAP Router, specify the SAP router string through which the connection is made, including:
Requires the following format:
/H/<IP address of SAP Router/S/<port of the SAP Router>/H/<SAP server host ip address/H/
|User||SAP username to connect with.|
|Password||Password for the specified SAP user on the SAP system.|
Method used to connect to the SAP system. Choose from:
The default value is Pooled Connection.
For examples of how to work with the four ERP nodes, see Working with the ERP nodes.