X hits on this document





96 / 131

Installing and Configuring JCo

The SAP adapter uses JCo to connect to the SAP system. JCo must be configured before proceeding with the project.

To install and configure JCo:

  • 1.

    Download a supported JCo version for your configuration from http://service.sap.com. Check the Oracle Data Integrator Certification Matrix available on the Oracle Technology Network to choose the appropriate SAP JCo version. Note that a minimum version of JCo 3.0.2 is required.

  • 2.

    Unzip the appropriate distribution package into an arbitrary directory {sapjco-install-path}.

  • 3.

    Follow the installation instructions in {sapjco-install-path}/javadoc/installation.html for the respective platform.

  • 4.

    Copy sapjco3.jar and sapjco3.dll (or respective binary) into the oracledi/drivers directory.

  • 5.

    Check the JCo installation.

Note: Changing the JCo library installed in the {windows-dir}\system32 directory of a machine running other SAP tools or components may cause issues with these components. Please check with your machine administrator before performing this change.

Setting up the Topology

If you are using this adapter in an existing Oracle Data Integrator version, the topology components required for this adapter are not installed yet.

You must perform the following operations after upgrading your Oracle Data Integrator version:

  • 1.

    If the SAP ABAP technology does not exist in your Master Repository, import the SAP ABAP technology in Synonym INSERT_UPDATE mode from the /impexp folder.

  • 2.

    Open the Java BeanShell technology and check on Language tab, that the JYTHON language is listed. If not, add it.

  • 3.

    Create a File Physical Schema pointing to an existing FTP server into which the extraction file will be pushed from SAP and picked up for SQL*Loader. Set the parameters for this data server as follows: Host (Data Server): FTP Server IP host name or IP address. User: Username to log into FTP server. Password: This user’s password. Data Schema: Path on FTP server

  • 4.

    Create a File Logical Schema called File Server for SAP ABAP, if it does not exist yet. This Logical Schema name is fixed and must be mapped to the Physical Schema created in the previous step.

  • 5.

    Configure the OdiSAPAbapExecute Open Tool in your repository. The Open Tool is available in your classpath after an upgrade, and needs to be added to the list of tools in the Master Repository. This process is described in the Using Open Tools section of the Oracle Data Integrator Tools Reference Manual.

The class name for this open tool is: oracle.odi.sap.km. OdiSapAbapExecute


Working with the SAP ABAP ERP KMs

The Oracle Data Integrator SAP ABAP ERP KMs enable to reverse and extract data from SAP ERP. To use SAP ERP data in your Oracle Data Integrator integration projects, you must:

Knowledge Modules Reference Guide


Document info
Document views257
Page views260
Page last viewedWed Oct 26 00:42:36 UTC 2016