16. Configuring Connectors

While Polarion ALM provides solutions that encompass all aspects of the application life cycle, it may not always be possible or realistic for organizations to adopt Polarion ALM solutions for the full spectrum. For example, your team or department might want to use Polarion ALM for requirements management, but other teams or departments are currently unable or unwilling to adopt the Polarion ALM solution applicable to their function. For example, development teams might want to keep their present tool for task and issue tracking, or testing teams might want to keep on with their current test management and testing tools.

If we identify sufficiently widespread demand for interoperation with Siemens or third party systems or tools in order to help prospective customers remove barriers to adoption of a Polarion solution within their organizations, we may develop Connectors for these third-party tools and systems. Connectors are integrated directly into the Polarion ALM platform rather than implemented as extensions. Connectivity and interoperation is configurable directly in platform's Administration interface, in the Connectors topic, and technical support is provided according to the customer's subscription plan.

The list includes connectors for such popular solutions as:

Some connectors may require you to download them from the Polarion ALM Extensions portal and install them per bundled instructions before they can be set up in Polarion ALM administration.

Overview of Functionality

Connectors provided either unidirectional or bidirectional synchronization of data between Polarion and a third-party system. The synchronization process generally works in the following way:

  1. Load all items that match a query and other parameters from Polarion ALM.

  2. Load all items that match query and other parameters from other system.

  3. Determine what needs to be done with the items:

    • Create "pairs" of items that have been synchronized before by looking up the connection information stored in folder [POLARION]/data/synchronizer.

    • If the "partner item" is found in the queried items, create a pair to be synchronized.

    • If an item is connected, but the "partner item" was not found, try to load the partner item by ID to create a pair to be synchronized.

    • If loading the item by ID fails, consider the item as deleted.

    • Consider all items that are not connected according to information in [POLARION]/data/synchronizer as new items.

  4. Create new items, synchronize paired items and propagate deletions according to the connector configuration.

In summary, if an item matches the query on either side (Polarion or third-party system) it will be synchronized.

The following sections in this chapter explain how to configure a connection to third-party systems, define synchronization pairs, map data interchange between Polarion and another system, and use features of the connectors.