Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →
Automated Jira Service Management Data Replication to Teradata
Use CData Sync to Customize and automate Jira Service Management data replication to Teradata.
Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Jira Service Management data into your Teradata instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.
Configure Teradata as a Replication Destination
Using CData Sync, you can replicate Jira Service Management data to Teradata. To add a replication destination, navigate to the Connections tab.
- Click Add Connection.
- Select the Destinations tab and locate the Teradata connector.
- Click the Configure Connection icon at the end of that row to open the New Connection page. If the Configure Connection icon is not available, click the Download Connector icon to install the Teradata connector. For more information about installing new connectors, see Connections in the Help documentation.
- To connect to Teradata, set the following connection properties:
- Connection Name: Enter a connection name of your choice.
- Data Source: Enter either the Teradata server name, the database computer (DBC) username, or the Teradata Director Program Id (TDPID).
- User: Enter the username that you use to authenticate to your Teradata account.
- Password: Enter the password that you use to authenticate to your Teradata account.
- Auth Scheme: Select the authentication scheme. The Auth schemes available in Sync are TD2 and LDAP. TD2 is the default scheme.
- Database: Enter the name of your Teradata database.
Note: If you do not specify a database, CData Sync connects to your default database.
- Port: Enter the port number for your Teradata server. The default port value is 1025.
- Once connected, click Create & Test to create, test and save the connection.
You are now connected to Teradata and can use it as both a source and a destination.
NOTE: You can use the Label feature to add a label for a source or a destination.
In this article, we will demonstrate how to load Jira Service Management data into Teradata and utilize it as a destination.
Configure the Jira Service Management Connection
You can configure a connection to Jira Service Management from the Connections tab. To add a connection to your Jira Service Management account, navigate to the Connections tab.
- Click Add Connection.
- Select a source (Jira Service Management).
- Configure the connection properties.
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.
- Click Connect to Jira Service Management to ensure that the connection is configured properly.
- Click Save & Test to save the changes.
Configure Replication Queries
CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.
Replicate Entire Tables
To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Jira Service Management tables you wish to replicate into Teradata, and click Add Tasks again.
Customize Your Replication
You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication with the help of SQL queries.
Schedule Your Replication
Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.
Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Jira Service Management data to Teradata.
Run the Replication Job
Once all the required configurations are made for the job, select the Jira Service Management table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.
Free Trial & More Information
Now that you have seen how to replicate Jira Service Management data into Teradata, visit our CData Sync page to explore more about CData Sync and download a free 30-day trial. Start consolidating your enterprise data today!
As always, our world-class Support Team is ready to answer any questions you may have.
