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.
- Creo - If you will use Syndeia to connect/communicate with Creo models managed in a local file system or Windchill repository, follow instructions in section 2.3.1.
- DOORS-NG - If you will use Syndeia to connect/communicate with DOORS-NG, follow instructions in section 2.3.2.
- Excel - If you will use Syndeia to connect/communicate with Excel models managed in a local file system, follow instructions in section 2.3.3.
- GitHub - If you will use Syndeia to connect/communicate with DOORS-NG, follow instructions in section 2.3.4.
- JIRA - If you will use Syndeia to connect/communicate with DOORS-NG, follow instructions in section 2.3.5.
- MySQL - If you will use Syndeia to connect/communicate with MySQL, follow instructions in section 2.3.6.
- NX - - If you will use Syndeia to connect/communicate with NX models managed in a local file system or Teamcenter repository, follow instructions in section 2.3.7.
- Simulink – If you will use Syndeia to connect/communicate with Simulink models managed in a local file system, follow instructions in section 2.3.8.
- Teamcenter - If you will use Syndeia to connect/communicate with Teamcenter, follow instructions in section 2.3.9.
- Windchill - If you will use Syndeia to connect/communicate with Windchill, follow instructions in section 2.3.10.
For using Syndeia to access Creo models in local file system or Windchill, follow the steps below.
...
For connecting and communicating with DOORS-NG, Syndeia already comes with the necessary libraries (such as OSLC-related jars) that are installed in the libDOORS folder under the Syndeia plugin for SysML tools. No additional user action is required.
...
...
...
For connecting and communicating with JIRA, Syndeia already comes with the necessary libraries that are installed with the Syndeia plugin for SysML tools. No additional user action is required.
...
...
...
...
...
For connecting and communicating with NX models managed in local file system or Teamcenter, you will need to collect jar files from your NX installation. These jar files will be used for the Syndeia plugin for Rhapsody. Follow the instructions in this section to collect these jar files.
...
- NXOpen.jar
- NXOpenRemote.jar
- NXOpenRun.jar
- NXOpenUF.jar
- NXOpenUFRemote.jar
- NXOpenUFRun.jar
- NXOpenUI.jar
- NXOpenUIRemote.jar
- NXOpenUIRun.jar
...
...
...
Accessing NX models in Teamcenter using 4-tier Teamcenter rich client
...
If NX is launched successfully in managed mode (you can access Teamcenter from NX), then it implies that your NX and Teamcenter installations are ready to access NX models in Teamcenter using Syndeia.
Accessing NX models in Teamcenter using 2-tier Teamcenter rich client
- Set the Teamcenter tier type to TWO_TIER in the Syndeia settings (section 4.9.3) after installation.
- Set TC_ROOT environment variable as the location of TC installation (2-tier client) on the user's machine where NX is installed, e.g. C:\Alpha\SIEMENS\tcua91_2tier_tcdev06
- Set FMS_HOME as the location of tccs folder in TC_ROOT, e.g. %TC_ROOT%\tccs
- Set TC_DATA as the location of TC data folder on the server machine that should be accessible from the client, e.g. \\tcdev06\tce\apps\ugs\win\datadir\tcua91_tcdev06_data
- To verify these settings, open a command prompt and type the following commands:
...
...
...
...
...
Follow the steps in this section to gather jar files to connect and communicate with Teamcenter 9.
- Create a folder named libTC to collect all the jar files needed for Teamcenter 9. You will need to locate and gather jar files from two different locations and copy them in the libTC folder.
- The first location (Location 1) to gather the jar files from is your Teamcenter server installation disk, specifically the following folder on the disk. <Your TC installation disk>\Tc9.1_win32\ soa_client\java\libs.
- Copy all the 27 jar files listed for Location 1 (LHS column) in the table below to the libTC folder.
- The second location (Location 2) to gather the jar files from is the Teamcenter rich client installation, specifically the following folder.
<Your TC rich client installation>\portal\plugins\com.teamcenter.rac.external_9000.1.0
Note: You do not need the Teamcenter rich client installed on your computer for Syndeia to connect to your Teamcenter server. You just need the jar files listed below from a Teamcenter rich client installation, either on your computer or some other computer.
- Copy all the 13 jar files listed for Location 2 (RHS column) in the table below to the libTC folder.
- Copy all the jar files listed for Location 2 (RHS column) in the table below to the libTC folder.
- Now, the libTC folder should have 41 jar files—28 from Location 1 and 13 from Location 2. Keep the libTC at a known location. You will use it during Syndeia for Rhapsody plugin installation (section 2.4).
...
Jar files to copy from Location 1 to libTC
(Teamcenter Server Installation Disk)
...
Jar files to copy from Location 2 to libTC
(Teamcenter rich client installation)
...
- avalon-framework-4.1.5.jar
- commons-codec.jar
- commons-httpclient-3.1.jar
- commons-logging.jar
- fmsutil.jar
- jacorb.jar
- resolver.jar
- tccommservice.jar
- tcgatewaystubs.jar
- tcmemjavabinding.jar
- tcserverjavabinding.jar
- TcSoaBomStrong_9000.1.0.jar
- TcSoaBomTypes_9000.1.0.jar
- TcSoaCadStrong_9000.1.0.jar
- TcSoaCadTypes_9000.1.0.jar
- TcSoaClient_9000.1.0.jar
- TcSoaCommon_9000.1.0.jar
- TcSoaCoreStrong_9000.1.0.jar
- TcSoaCoreTypes_9000.1.0.jar
- TcSoaQueryStrong_9000.1.0.jar
- TcSoaQueryTypes_9000.1.0.jar
- TcSoaStrongModel_9000.1.0.jar
- teamcenter_sso_applib.jar
- teamcenter_sso_common.jar
- teamcenter_sso_proxy.jar
- teamcenter_sso_webtoolkit.jar
- xercesImpl.jar
- xml-apis.jar
...
...
Follow the steps in this section to gather jar files to connect and communicate with Windchill. You will need the following Windchill 10.1 jar files. You can use these to communicate with both Windchill 10.1 and 10.2 repositories.
...
...
Go to the following folder on your Windchill server: <Your Windchill Installation>\Windchill\codebase\WEB-INF\lib, e.g. D:\ptc\Windchill\codebase\WEB-INF\lib
...
- ie3rdpartylibs.jar
- ieWeb.jar
- wncWeb.jar
...