Using Syndeia with Teamcenter.

Prerequisites for Teamcenter

Teamcenter is installed
The Teamcenter web service is operational
The network ports between the Teamcenter server and the Syndeia plugins and the Syndeia servers are open
The users who will use Syndeia must have Teamcenter accounts for the Teamcenter Default Group and Default Role
Users must provide proper Teamcenter account credentials.

Before proceeding, attempt to browse (in Chrome, Safari, IE, Edge) to the Teamcenter Web Service and authenticate as the user who will be the user operating the Syndeia applications. Confirm successful entry.

Note that the IT enterprise network may have “proxies” in place that alter hostnames and ports for browser sessions and may or may not do the same for machine-to-machine connections (like Syndeia makes).

Follow the steps in this section to gather assemble Teamcenter’s jars for machine-to-machine integrations.

Create a folder named libTC to collect all the jar files needed for Teamcenter. You will need to locate and gather jar files from two different locations and copy them in the libTC folder. The jar files in the first location are required. The jar files in the second location are optional.
The first location (Location 1) to gather the jar files from is your Teamcenter server installation. Each Teamcenter installation has a soa_client.zip file at the root level, e.g. <Your TC installation folder>\Tc9.1_win32\soa_client.zip.
1. Extract the contents of (unzip) soa_client.zip file.
2. Navigate to the java\libs sub-folder, e.g. <Your TC installation folder>\Tc9.1_win32\soa_client\java\libs.
3. Copy all the 27 jar files listed for Location 1 (LHS column) in the table below to the libTC folder.
Optional: The second location (Location 2) to gather the jar files from is the Teamcenter rich client installation, specifically the following folder.
1. For TC 9.x: <Your TC rich client installation>\portal\plugins\com.teamcenter.rac.external_9000.1.0
2. For TC 11.2: <Your TC installation folder>\TcRoot\portal\plugins\com.teamcenter.rac.external_11000.2.0
3. Copy all the 13 jar files listed for Location 2 (RHS column) in the table below to the libTC folder.
4. 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 40 jar files—27 from Location 1 and 13 from Location 2.
1. Keep the libTC at a known location.

Complete the installation of support for Teamcenter Repositories by providing this libTC folder to each workstation that will run the Syndeia Plugin

Standalone: Installation - Syndeia Standalone
MagicDraw: Install Syndeia plugin
Rhapsody: Install Syndeia plugin.

Syndeia Teamcenter jar files

If you do not find any jar files in the specified folders, please have your Teamcenter Administrator search for them in the context of the Teamcenter installation folders.

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation
avalon-framework-4.1.5.jar	activation.jar
commons-codec.jar	antlr-2.7.2.jar
commons-httpclient-3.1.jar	ApplicationRegistryClient.jar
fmsutil.jar	concurrent-1.3.2.jar
jacorb.jar	fccjavaclientproxy.jar
resolver.jar	fmsservercache.jar
tccommservice.jar	fscjavaclientproxy.jar
tcgatewaystubs.jar	idl.jar
tcmemjavabinding.jar	jgraph.jar
tcserverjavabinding.jar	mail.jar
TcSoaBomStrong_9000.1.0.jar	soap.jar
TcSoaBomTypes_9000.1.0.jar	TcGatewayWebService.jar
TcSoaCadStrong_9000.1.0.jar	wrapper-3.0.3.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

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation
avalon-framework-4.1.5.jar	activation.jar
commons-codec.jar	antlr-2.7.2.jar
commons-httpclient-3.1.jar	ApplicationRegistryClient.jar
fmsutil.jar	concurrent-1.3.2.jar
jacorb.jar	fccjavaclientproxy.jar
resolver.jar	fmsservercache.jar
tccommservice.jar	fscjavaclientproxy.jar
tcgatewaystubs.jar	idl.jar
tcmemjavabinding.jar	jgraph.jar
tcserverjavabinding.jar	mail.jar
TcSoaBomStrong_11000.2.0.jar	soap.jar
TcSoaBomTypes_11000.2.0.jar	TcGatewayWebService.jar
TcSoaCadStrong_11000.2.0.jar	wrapper-3.0.3.jar
TcSoaCadTypes_11000.2.0.jar
TcSoaClient_11000.2.0.jar
TcSoaCommon_11000.2.0.jar
TcSoaCoreStrong_11000.2.0.jar
TcSoaCoreTypes_11000.2.0.jar
TcSoaQueryStrong_11000.2.0.jar
TcSoaQueryTypes_11000.2.0.jar
TcSoaStrongModel_11000.2.0.jar
teamcenter_sso_applib.jar
teamcenter_sso_common.jar
teamcenter_sso_proxy.jar
teamcenter_sso_webtoolkit.jar
xercesImpl.jar
xml-apis.jar

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation

Files from the Teamcenter Server Installation Disk(s)	Files from the Teamcenter Rich Client Installation
avalon-framework-4.1.5.jar	activation.jar
commons-codec.jar	antlr-2.7.2.jar
commons-httpclient-3.1.jar	ApplicationRegistryClient.jar
fmsutil.jar	concurrent-1.3.2.jar
jacorb.jar	fccjavaclientproxy.jar
resolver.jar	fmsservercache.jar
tccommservice.jar	fscjavaclientproxy.jar
tcgatewaystubs.jar	idl.jar
tcmemjavabinding.jar	jgraph.jar
tcserverjavabinding.jar	mail.jar
TcSoaBomStrong_12000.4.0.jar	soap.jar
TcSoaBomTypes_12000.4.0.jar	TcGatewayWebService.jar
TcSoaCadStrong_12000.4.0.jar	wrapper-3.0.3.jar
TcSoaCadTypes_12000.4.0.jar
TcSoaClient_12000.4.0.jar
TcSoaCommon_12000.4.0.jar
TcSoaCoreStrong_12000.4.0.jar
TcSoaCoreTypes_12000.4.0.jar
TcSoaQueryStrong_12000.4.0.jar
TcSoaQueryTypes_12000.4.0.jar
TcSoaStrongModel_12000.4.0.jar
teamcenter_sso_applib.jar
teamcenter_sso_common.jar
teamcenter_sso_proxy.jar
teamcenter_sso_webtoolkit.jar
xercesImpl.jar
xml-apis.jar

Syndeia Teamcenter

The workstation you use does not have to be provisioned as a Teamcenter Rich Client. For Syndeia to connect to your Teamcenter server, Syndeia’s libTC directory must contain the proper versioned jar files from a Teamcenter Rich Client that were found on some computer, yours or any that is provisioned as a Teamcenter Rich Client, or off Teamcenter installation media.