Create Informatica Mappings From/To an ODBC Data Source for Jira Service Management



Create an ODBC connection to Jira Service Management in Informatica and browse and transfer Jira Service Management data.

Informatica provides a powerful, elegant means of transporting and transforming your data. By utilizing the CData ODBC Driver for Jira Service Management, you are gaining access to a driver based on industry-proven standards that integrates seamlessly with Informatica's powerful data transportation and manipulation features. This tutorial shows how to transfer and browse Jira Service Management data in Informatica PowerCenter.

Connect to Jira Service Management as an ODBC Data Source

Information for connecting to Jira Service Management follows, along with different instructions for configuring a DSN in Windows and Linux environments.

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, you will need to 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.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Linux

If you are installing the CData ODBC Driver for Jira Service Management in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData JiraServiceDesk Source] Driver = CData ODBC Driver for Jira Service Management Description = My Description ApiKey = myApiKey User = MyUser

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Create a Linked Table to Requests Data

Follow the steps below to create a linked table, which enables you to access live Requests data.

Create the ODBC Connection

Follow the steps below to connect to Jira Service Management in Informatica PowerCenter:

  1. In the Informatica Developer tool connect to your repository and create a project.
  2. In the Connection Explorer pane, right-click and click Create a Connection.
  3. In the New Database Connection wizard that is displayed, enter a name and Id for the connection and in the Type menu select ODBC.
  4. In the Connection String property, enter the DSN.

NOTE: If you are working in a Linux operating system, set the Driver Manager for Linux property to unixODBC 2.3.x.

Create the Jira Service Management Data Object

After you have created an ODBC connection to Jira Service Management, you can now access Jira Service Management entities in Informatica. Follow the steps below to add Requests entities to your project.

  1. In the Object Explorer, right-click your project and then click New -> Data Object.
  2. In the wizard that is displayed, select the Relational Data Object option.
  3. Click the Browse button next to the Connection box and select the ODBC connection you created in the previous step.
  4. Select the option to create a data object from an existing resource and click the Browse button next to the Resource box.
  5. In the dialog that is displayed, clear the Show Default Schema Only option and expand the node for the ODBC connection. Select the entity that you want.

You can now browse the table in the Data Viewer: Right-click the node for the table and then click Open. On the Data Viewer view, click Run.

Create the Mapping

Follow the steps below to add the Jira Service Management source to a mapping:

  1. In the Object Explorer, right-click your project and then click New -> Mapping.
  2. Expand the node for the Jira Service Management connection and then drag the data object for the table onto the editor.
  3. In the dialog that appears, select the Read option.

Follow the steps below to map Jira Service Management columns to a flat file:

  1. In the Object Explorer, right-click your project and then click New -> Data Object.
  2. Select Flat File Data Object -> Create as Empty -> Fixed Width.
  3. In the properties for the Jira Service Management object, select the rows you want, right-click, and then click copy. Paste the rows into the flat file properties.
  4. Drag the flat file data object onto the mapping. In the dialog that appears, select the Write option.
  5. Click and drag to connect columns.

To transfer Jira Service Management data, right-click in the workspace and then click Run Mapping.

Ready to get started?

Download a free trial of the Jira Service Management ODBC Driver to get started:

 Download Now

Learn more:

Jira Service Management Icon Jira Service Management ODBC Driver

The Jira Service Management ODBC Driver is a powerful tool that allows you to connect with live data from Jira Service Management, directly from any applications that support ODBC connectivity.

Access Jira Service Management data like you would a database - read, write, and update Jira Service Management Customers, Organizations, Requests, etc. through a standard ODBC Driver interface.