Syndeia requires Java libraries (jar files) to connect and communicate with PLM systems (Teamcenter and Windchill), requirements management systems (DOORS-NG), databases (MySQL), ALM systems (GitHub), project management systems (JIRA), and domains models (NX, Creo, and Simulink). Some of the Java libraries are proprietary technology of the vendors— Siemens PLM (Teamcenter, NX), PTC (Windchill, Creo), and Oracle (MySQL)—and are not distributed with the Syndeia plugins.

The following sections describe the specific jar files (and their locations) that you need to gather from your own PLM/ALM/database/tool installations to use with Syndeia. You will need to contact your PLM/ALM/database administrators to gather these jar files. It is best if the administrator can host these files at a shared location so that all Syndeia users in your organization/group can readily access them. Alternatively, a lead MBSE engineer can copy these jar files in the Syndeia plugin (zip) and re-distribute the Syndeia plugin within the organization. You need to gather libraries for only those repositories that you will connect and communicate with.

Adding actual Repositories

After Integrations with repositories have been configured, administrators will want to add one or more instances of the repositories which are in use by engineering teams across the organization. To add such instances into a configured Syndeia deployment, visit the guide at Adding a Repository.

The following pages concern the integrations that require some additional configuration including gathering of jar files as explained above:

The following integrations do not require additional configuration, as Syndeia already comes with the necessary libraries that are installed with the Syndeia plugin for SysML tools. No additional user action is required for these, and the user can proceed straight to Adding a Repository.

Aras
Artifactory
Bitbucket
Collaborator
Confluence
DOORS-NG
Excel
GitHub
GitLab
Jama
Jira
RESTful
Teamwork Cloud (TWC)
TestRail
VOLTA