This topic describes how to create a data source. A data source defines the attributes of a product (endpoint) that will be party to a synchronization. Later, you will create a connection that synchronizes between two data sources.
Note: If you are synchronizing with Jira, make sure your project is set up for synchronization. For details, see Prepare Jira for synchronization.
When creating and using data sources, you need to make sure that Micro Focus Connect has access to the data source through an existing user account. For data source user accounts connecting to Jira, ServiceNow, ALM Octane, and ALM/QC, we recommend a service account with full administrative privileges—not a personal user account.
If you set the data source user account with non-administrator privileges, you must explicitly identify the minimal privileges required for the endpoints to successfully synchronize. If your synchronization fails, the cause may be insufficient privileges.
For example, your minimal permissions may exclude Jira query project lists, or ServiceNow query incidents, which would fail the synchronization. You need to add those privileges to enable a successful synchronization.
The access rights requirements described here are only relevant to the user account configured on the data source. They are not related to Micro Focus Connect users, or to users specified in user maps.
The majority of data sources require you to specify a default sample project (/workspace) to be used as a template when you create a data source. Micro Focus Connect uses this project to discover the available types, fields, and list values that will be available for configuring a connection based on this data source. This is required for products whose schema is customizable on a per-project basis, such as ALM Octane, ALM/QC, JIRA, Azure DevOps, Broadcom Rally, CollabNet Version One, and ServiceNow.
Make sure to specify a project that has all the entities you want to apply to the associated connections. It does not have to be the project whose data will actually be synchronized.
The metadata of the projects being mapped in the connection, must be identical to the metadata of the default project. For example, a project being synchronized on a given connection using a Jira data source, must have matching types, properties, and enumerated lists with the default project. However, the connection project does not need to be synchronized with the default project.
Certain product endpoints such as StarTeam, do not surface types, properties, list values, or users per project. Rather, they surface the same schema for the whole system. As a result , a default project is not required.
For any given data source, specify a sample project that includes all the entities required to be used within a connection and all the projects that the connection synchronizes. This will serve as a template project.
Per project, check that all custom properties being mapped are of the same type, same name, and same label. This is true for the sample project and the project(s) being synchronized by the connection.
If one or more projects are expected to use a property whose schema is described by a different sample project, then that property must be the same as the one described by the sample project. Synchronization failures may occur if the properties do no match.
There are two main ways to create a single shared data source:
- across multiple connections
- as a single connection with multiple projects
Note: If you are configuring a shared data source as a single connection with multiple projects, the sample project schema (specifically for types and properties being synchronized) must be identical to all the constituent projects across the related connections.
You can create multiple data sources to the same product endpoint. In such configurations, assign each data source its own sample project.
For connections that synchronization only one endpoint, set a unique and separate data source for the master and for the target. The data source sample project should be set to the same project synchronized by the connection.
To create a data source:
- Click the Data Sources tab.
- Above the Data Sources list, click + Data Source.
In the dialog box that opens, provide the following information:
New Data Source Name Enter a unique name for your Data source. Data Source Product The products that are available in the list are the connectors that were added with the product installation or the ones that you downloaded from our community and installed yourself.
Your data source is added to the list of data sources.
- Select your data source to edit its details.
- Click Properties. The Properties pane lists additional fields that are specific to the product. For information on the fields, click View Readme. The readme file that was installed with your connector displays in the lower pane.
Additional guidelines for working with data sources
This section lists several guidelines that apply to Micro Focus Connect data sources.
- The bottom pane displays a Type with the name ChangeSet. You do not need to make any changes within this pane.
- You can delete a data source provided that it is not included in a connection.
- You can use the same data sources in multiple connections. Data sources describe how to connect to a server. The connection then uses the data source to describe how to map types and projects within that data source.
- You cannot use the same data source for both sides of the connection. If you want to synchronize between projects within the same product, you can create a second data source with the same server details, and use the two data sources at either side of a connection.
- After you create a connection, you can specify any number of combinations of projects between the data sources. The only condition is that the paired projects need to conform to the data source restrictions. For example, Azure DevOps, the paired projects must be of the same type.
Swap the master and target data sources
Once you have selected a master and target for a connection, you can never change them. You can create a different connection, provided that the master is a Micro Focus product, as the term master only applies to Micro Focus products, such as ALM Octane and ALM/QC. The term target applies to all products: Jira, ALM/QC, ALM Octane, Azure DevOps, and so forth.
You can however, change the direction of the data flow in the following way:
- If you want data to flow from Jira to ALM Octane, set the direction to To Master.
- If you want data to flow from ALM Octane to Jira, set the direction to From Master.
- If you want data to flow in both directions, select Bi-directional.
This will not impact cross references, since they remain unchanged inside the Micro Focus Connect database.