ETL Jira Service Management in Oracle Data Integrator

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

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

This article covers a JDBC-based ETL -- Jira Service Management to Oracle. After reverse engineering a data model of Jira Service Management 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.jiraservicedesk.jar) and .lic file (cdata.jdbc.jiraservicedesk.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 Jira Service Management data. After reverse engineering, you can query real-time Jira Service Management data and create mappings based on Jira Service Management tables.

1. In ODI, connect to your repository and click New -> Model and Topology Objects. 👁 Create a New Model
   
2. On the Model screen of the resulting dialog, enter the following information:
   • Name: Enter JiraServiceDesk.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter JiraServiceDesk.
   • Context: Select Global.
   👁 Configuring the Model
   
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter JiraServiceDesk.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.jiraservicedesk.JiraServiceDeskDriver
   • URL: Enter the JDBC URL containing the connection string.

     You can establish a connection to any Jira Service Desk Cloud account or Server instance.

     Connecting with a Cloud Account

     To connect to a Cloud account, you'll first need to retrieve an APIToken. To generate one, log in to your Atlassian account and navigate to API tokens > Create API token. The generated token will be displayed.

     Supply the following to connect to data:

     • User: Set this to the username of the authenticating user.
     • APIToken: Set this to the API token found previously.

     Connecting with a Service Account

     To authenticate with a service account, supply the following connection properties:

     • User: Set this to the username of the authenticating user.
     • Password: Set this to the password of the authenticating user.
     • URL: Set this to the URL associated with your JIRA Service Desk endpoint. For example, https://yoursitename.atlassian.net.

     Note: Password has been deprecated for connecting to a Cloud Account and is now used only to connect to a Server Instance.

     Accessing Custom Fields

     By default, the connector only surfaces system fields. To access the custom fields for Issues, set IncludeCustomFields.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.jiraservicedesk.jar
     

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

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     

     Below is a typical connection string:

     jdbc:jiraservicedesk:ApiKey=myApiKey;User=MyUser;InitiateOAuth=GETANDREFRESH;
     

   👁 Configuring the Data Server
   
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 Jira Service Management, enter the Schema selected, otherwise enter JiraServiceDesk.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Jira Service Management, enter the Schema selected, otherwise enter JiraServiceDesk.
   👁 Configuring the Physical Schema
   
5. In the opened model click Reverse Engineer to retrieve the metadata for Jira Service Management tables. 👁 Reverse Engineer the Model
   

Edit and Save Jira Service Management Data

After reverse engineering you can now work with Jira Service Management data in ODI. To edit and save Jira Service Management data, expand the Models accordion in the Designer navigator, right-click a table, and click Data. Click Refresh to pick up any changes to the data. Click Save Changes when you are finished making changes. 👁 Viewing the data.

Create an ETL Project

Follow the steps below to create an ETL from Jira Service Management. You will load Requests 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 Requests table in Jira Service Management:

   CREATE TABLE ODI_DEMO.TRG_REQUESTS (REPORTERNAME NUMBER(20,0),RequestId 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_REQUESTS 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_REQUESTS table from the Sales Administration model onto the mapping.
7. Drag the Requests table from the Jira Service Management 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 REQUESTS_AP in TARGET_GROUP.
10. In the REQUESTS_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. 👁 SQL-based access to Jira Service Management enables you to use standard database-to-database knowledge modules.
    

You can then run the mapping to load Jira Service Management data into Oracle.