ETL LINE in Oracle Data Integrator

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

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

This article covers a JDBC-based ETL -- LINE to Oracle. After reverse engineering a data model of LINE 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 (cdata.jdbc.api.jar) and .lic file (cdata.jdbc.api.lic), located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: ~/.odi/oracledi/userlib and $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\odi\oracledi\userlib and %APPDATA%\odi\agent\lib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of LINE data. After reverse engineering, you can query real-time LINE data and create mappings based on LINE 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 API.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter API.
   • Context: Select Global.
   
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter API.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.api.APIDriver
   • URL: Enter the JDBC URL containing the connection string.

     Start by setting the Profile connection property to the location of the LINE Profile on disk (e.g. C:\profiles\LINE.apip). Next, set the ProfileSettings connection property to the connection string for LINE (see below).

     LINE API Profile Settings

     The LINE Messaging API uses Channel Access Token authentication. To obtain a Channel Access Token:

     1. Log in to the LINE Developers Console at https://developers.line.biz
     2. Select your provider and open your Messaging API channel.
     3. Navigate to the Messaging API tab.
     4. Under Channel access token, click Issue to generate a long-lived token.
     5. Copy the generated token.

     After obtaining your Channel Access Token, set the following connection properties:

     • AuthScheme: Set this to APIKey.

     Set the following in the ProfileSettings connection property:

     • APIKey: Set this to your LINE Channel Access Token.

     Built-in Connection String Designer

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

     
     java -jar cdata.jdbc.api.jar
     

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

     

     Below is a typical connection string:

     
     jdbc:api:Profile=C:\profiles\LINE.apip;ProfileSettings='APIKey=your_channel_access_token;';AuthScheme=APIKey;
     

   
4. On the Physical Schema screen, enter the following information:
   • Name: Select from the Drop Down menu.
   • Database (Catalog): Enter CData.
   • Owner (Schema): If you select a Schema for LINE, enter the Schema selected, otherwise enter API.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for LINE, enter the Schema selected, otherwise enter API.
   
5. In the opened model click Reverse Engineer to retrieve the metadata for LINE tables.

Edit and Save LINE Data

After reverse engineering you can now work with LINE data in ODI. To view LINE 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 LINE. You will load ReplyMessageDelivery 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 ReplyMessageDelivery table in LINE:

   
   CREATE TABLE ODI_DEMO.TRG_REPLYMESSAGEDELIVERY (DELIVEREDCOUNT NUMBER(20,0),DeliveryDate 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_REPLYMESSAGEDELIVERY 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_REPLYMESSAGEDELIVERY table from the Sales Administration model onto the mapping.
7. Drag the ReplyMessageDelivery table from the LINE 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 REPLYMESSAGEDELIVERY_AP in TARGET_GROUP.
10. In the REPLYMESSAGEDELIVERY_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

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