Ready to get started?

Learn more about the CData JDBC Driver for Sage 200 or download a free trial:

Download Now

ETL Sage 200 in Oracle Data Integrator

This article shows how to transfer Sage 200 data into a data warehouse using Oracle Data Integrator.

Leverage existing skills by using the JDBC standard to connect to Sage 200: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Sage 200 connects real-time Sage 200 data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with Sage 200 just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Sage 200 APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- Sage 200 to Oracle. After reverse engineering a data model of Sage 200 entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR and .lic file, located in the installation folder, into the ODI userlib directory:

On Unix: ~/.odi/oracledi/userlib On Windows: %APPDATA%\Roaming\odi\oracledi\userlib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of Sage 200 data. After reverse engineering, you can query real-time Sage 200 data and create mappings based on Sage 200 tables.

  1. In ODI, connect to your repository and click New -> Model and Topology Objects.
  2. On the Model screen of the resulting dialog, enter the following information:
    • Name: Enter Sage200.
    • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
    • Logical Schema: Enter Sage200.
    • Context: Select Global.
  3. On the Data Server screen of the resulting dialog, enter the following information:
    • Name: Enter Sage200.
    • Driver List: Select Oracle JDBC Driver.
    • Driver: Enter cdata.jdbc.sage200.Sage200Driver
    • URL: Enter the JDBC URL containing the connection string.
      • Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
      • Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.

      Built-in Connection String Designer

      For assistance in constructing the JDBC URL, use the connection string designer built into the Sage 200 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.sage200.jar

      Fill in the connection properties and copy the connection string to the clipboard.

      Below is a typical connection string:

      jdbc:sage200:SubscriptionKey=12345;Schema=StandardUK;InitiateOAuth=GETANDREFRESH
  4. On the Physical Schema screen, enter the following information:
    • Schema (Schema): Enter Sage200.
    • Schema (Work Schema): Enter Sage200.
  5. In the opened model click Reverse Engineer to retrieve the metadata for Sage 200 tables.

Edit and Save Sage 200 Data

After reverse engineering you can now work with Sage 200 data in ODI. To view Sage 200 data, expand the Models accordion in the Designer navigator, right-click a table, and click View data.

Create an ETL Project

Follow the steps below to create an ETL from Sage 200. You will load Banks entities into the sample data warehouse included in the ODI Getting Started VM.

  1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

    Alternatively you can use SQLPlus. From a command prompt enter the following:

    sqlplus / as sysdba
  2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the Banks table in Sage 200: CREATE TABLE ODI_DEMO.TRG_BANKS (CODE NUMBER(20,0),Id VARCHAR2(255));
  3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
  4. Click Reverse Engineer. The TRG_BANKS table is added to the model.
  5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
  6. Drag the TRG_BANKS table from the Sales Administration model onto the mapping.
  7. Drag the Banks table from the Sage 200 model onto the mapping.
  8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
  9. Open the Physical tab of the Mapping Editor and click BANKS_AP in TARGET_GROUP.
  10. In the BANKS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load Sage 200 data into Oracle.