Polarion® Connector for Polarion®

 Connect more Polarion servers in order to seamlessly connect your cross-functional teams, and your customers to a single source of truth.


Do you use multiple Polarion servers? Do you work with customers or partners that use Polarion, like you? Are you spending time with manual operations to exchange data with other teams, or your customers and partners? Are you struggling to get full traceability? Would you like to have the data exchanged seamlessly, and the traceability maintained automatically, without any additional effort?

Polarion Connector for Polarion seamlessly connects your cross-functional teams by enabling bi-directional synchronization of work items between different Polarion servers. Thanks to a direct integration, disparate teams can collaborate without having to leave their familiar environments.

Polarion Connector for Polarion is part of Polarion INTEGRATION PLATFORM™, designed to enable you to seamlessly integrate disparate applications with Polarion’s unified ALM Solution. It is architected to manage all integrations centrally to speed up development and maintenance. It provides you with out-of-box access to all integrated applications, eliminating the burden of having to interface with them individually.

Here are some scenarios in which Polarion Connector for Polarion can help:

  • You have one server for the engineering team where software is developed and validated, and another server for the product and project management team where requirements are written and managed. You want to give your engineers direct access to all requirements, and at the same time provide project managers with direct visibility of the development status.

  • You have a project that is outsourced so it can be developed abroad. You don’t want to give the development team access to your main Polarion server, but you want them to see the requirements they need to implement.

  • You are managing customer requests on one Polarion server. The customers have access to this server, so they can post questions and they can see the status of their requests. You are using a separate server for the actual development and project management activities. You want your internal team to see what the customers are requesting, but you don’t want your customer to see your internal details.

  • You have a public server and a private server. You want to be able to synchronize data between the two systems, but you want to keep your private data private.

  • You are working with a partner that uses Polarion. You want to synchronize your requirements to the partner and receive the status updates back.

Let’s have a closer look at this use case example:

You have two Polarion Servers:

  1. The first Polarion server for Requirements Management and QA Management. Let’s call it “Polarion REQ-QA”
  2. The second server is for development. Let’s call it “Polarion DEV”.

You want to synchronize the User Stories and Defects to the development server so that the development team knows what to implement, and the status of the User Stories and Defects to the requirements server so that the Product and QA teams can monitor the status of the implementation.

With Polarion Connector for Polarion these User Stories and Defects are synchronized seamlessly, meaning that all changes to your items are propagated to the other server automatically. Hence one single source of truth is maintained on both servers.




Perform bi-directional and uni-directional synchronization of any artifact type including critical ones like requirements, user stories, tasks, defects and tests. This ensures that all collaborators can see the same data, no matter what application they use.

  • Bi-directional synchronization allows the data to flow in two directions. You want your teams to be able to modify the data in their own environment, and then propagate the changes across all Polarion servers.

  • Uni-directional synchronization allows the data to flow in only one direction. For example, you have a production and a backup server, and you want to allow changes only on the production server, with the backup server receiving the data as “read-only”. Or your Business Analysts create requirements on one Polarion server, and make them  visible, but not modifiable, for the Development team working on another Polarion server.

All details of the artifacts can be synchronized, including comments and attachments. This ensures a comprehensive and undiluted understanding of the artifacts, while the respective teams can keep working in their familiar environment.

The synchronization happens real-time, meaning that the data changes in one system are immediately reflected in the other. This ensures that the data remains consistent across all applications. At the same time, the possibility of conflicts is minimized because there is a smaller probability for the same data to be modified at the same time by two different collaborators.

However, in case you need it, there are also options for scheduling the synchronization of each of the integrated applications, and project artifacts at different times.



One of the major advantages of the Polarion Connector for Polarion is end to end traceability. Work item types are synchronized together with their links. Any type of relationship is maintained.

You can see what has been built, track the impact of an actual change, or analyze a potential change.



Every modification made to a work item is communicated centrally to the Polarion INTEGRATION PLATFORM. In case a work item is modified at the same time from different systems, conflict resolution mechanisms can be configured to resolve conflicts automatically.



In the real environment, the network might fail, or servers might become unreachable. Polarion Connector for Polarion as part of the Polarion INTEGRATION PLATFORM has built-in mechanisms for failure management and automatic recovery.

  • If the endpoint is down,data is kept in the queue until the endpoint is up again, and then re-transmitted.

  • In case Polarion INTEGRATION PLATFORM is stopped for updates or other reasons, an auto recovery mechanism is in place that allows it to continue to function correctly. No transaction is ever lost or duplicated.

  • If for some reason transactions fail, Polarion INTEGRATION PLATFORM notifies the administrator so that the error can be corrected.



You can manage and configure the integrations via Polarion INTEGRATION PLATFORM web-based console. As is characteristic of Polarion’s solutions, the administration console is designed with ease of use in mind, enabling less technical users to perform complex enterprise configurations.

To configure the integration you need 3 simple steps:

1. Configure the Polarion servers that you want to connect: add the details about the applications that you want to configure, the servers, and the project.

2. Choose what work item types you want to synchronize. Polarion INTEGRATION PLATFORM can synchronize any Work Item type, standard or custom-defined in the applications.

3. Configure the mapping: indicate what fields you want to be synchronized, the direction of synchronization, the transformations and who takes precedence in case of conflict.



The main page of the web-based Administration Console shows a graphical visualization of all configured synchronizations: connected applications and projects, mapped work item types, active and inactive synchronizations.

The Monitoring page offers instant visibility into the activity of the Polarion INTEGRATION PLATFORM:

  • What synchronizations are performed, the work item types, the number of outgoing and incoming messages.
  • The possibility to clean the message queues that contain errors.
  • The log data and the outstanding errors.





Vendor Siemens PLM
Published Version 1.0.3 - April 2016
Price Free
Community Supported Extension This extension is not supported by Siemens PLM.
Requirements Polarion 2014 and newer
Windows Server 2008, 2012, SUSE Linux Enterprise Server 11, Red Hat Enterprise Linux6.x/CentOS 6.x, Debian GNU/Linux 6.0, 7.0, Ubuntu Server 12.04 LTS
Last tested with Polarion 2019 SR3 (3.19.3)