Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Use Updategrams with Jira Service Desk Data
You can use updategrams to insert, update, and delete Jira Service Desk data. This guide shows how to use the CData BizTalk Adapter for Jira Service Desk to generate updategram schemas and instances.
In this article, you will create updategrams that can be executed by the CData BizTalk Adapter for Jira Service Desk. You will design a schema and use it as a template for generating insert, update, and delete updategrams.
Add the Adapter for Jira Service Desk to Your Project
Use the Add Adapter wizard to add the adapter to a BizTalk Server project in Visual Studio. You will use the adapter to query Jira Service Desk for metadata about the table you want to modify.
- Right-click on the project in the Solution Explorer and click Add -> Add Generated Items.
- Select Add Adapter Metadata in the resulting dialog box.
- In the resulting Add Adapter Wizard, select the CData BizTalk Adapter for Jira Service Desk from the list view.
- In the Port menu, leave the selection blank. Or, select a receive location or send port that has been configured to use the adapter.
- When you click Next, the Schema Wizard is displayed.
Generate a Schema for an Updategram
Follow the steps below to create a schema in a BizTalk Server project in Visual Studio.
- If you have not already done so, add the Jira Service Desk adapter to your project.
- On the Connection String page of the Add Adapter wizard, enter authentication credentials and other connection properties, if they were not already configured in the send port or receive location. Below is a typical connection string:
ApiKey=myApiKey;User=MyUser;InitiateOAuth=GETANDREFRESH
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.
See the "BizTalk Configuration" chapter in the help documentation for more information on the required connection properties.
- On the Schema Information page, click Send Port in the General Options section. Select Updategram from the CommandType menu. If you are using the adapter in a solicit-response send port, disable the One-Way option.
On the next page, Statement Information, select the type of the updategram: Insert, Update, or Delete. Select the Table name and the columns you want to include in the schema. If you want to update or delete, the Id column is required.
Note: When you create the updategram, you are limited to modifying the columns you include in the schema.
- Click Next to view a summary of the schema and finish the wizard to create the schema. The resulting .xsd file is added to your project.
Generate Insert, Update, and Delete Instance Messages
After you create the updategram schema, you can use the .xsd file to generate the updategram: Right-click the .xsd file and select Generate Instance. You can also use this file as a template to manually create updategrams. Below are example generated updategram instances for inserts, updates, and deletes:
Insert
An example of INSERT is below. In this instance, there is only an after block, which specifies how the data will change.
<ns0:parameters xmlns:ns0="http://www.cdata.com/JiraServiceDeskProvider">
<ns0:sync>
<ns0:before></ns0:before>
<ns0:after>
<ns0:Requests RequestId="RequestId_0" ReporterName="ReporterName_1" />
</ns0:after>
</ns0:sync>
</ns0:parameters>
Update
An example of UPDATE is below. In this instance, there is both a before block (how the data currently exists in the table) and an after block (how the data will change).
<ns0:parameters xmlns:ns0="http://www.cdata.com/JiraServiceDeskProvider">
<ns0:sync>
<ns0:before>
<ns0:Requests Id=001d000000YBRseAAH></ns0:Requests>
</ns0:before>
<ns0:after>
<ns0:Requests RequestId="RequestId_0" ReporterName="ReporterName_1" ></ns0:Requests>
</ns0:after>
</ns0:sync>
</ns0:parameters>
Delete
An example for DELETE is below. The after block will be empty to show that it is removing the item.
<ns0:parameters xmlns:ns0="http://www.cdata.com/JiraServiceDeskProvider">
<ns0:sync>
<ns0:before>
<ns0:Requests Id=001d000000YBRseAAH></ns0:Requests>
</ns0:before>
<ns0:after></ns0:after>
</ns0:sync>
</ns0:parameters>
Processing Schemas
To use updategrams to insert, update, or delete Jira Service Desk records, see the tutorial.