Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section provides details on configuring the Teamcenter integration for the Syndeia Rhapsody plugin. It consists of the following two stages.

Pre

...

-requisites

Syndeia / Teamcenter admins and end users should read and confirm that they satisfy the pre-requisites below.

  1. User should have access to the Teamcenter server /(repository) to connect with Syndeia.

  2. User should have an account to log in to the Teamcenter server that works with the default group and role on that Teamcenter server.

  3. User should be able to connect to the Teamcenter server from their machine. This should be verified by using one of the following clients:

    1. Active Workspace Client from a web browser on the user’s machine

    2. Teamcenter Web Client from a web browser on the user’s machine

    3. Teamcenter Rich Client installed on the user’s machine

  4. Additional notes:

    1. Syndeia directly connects with the Teamcenter server and does not use any of the clients listed above. The clients above are mentioned only for user’s users to verify their accounts and connection to the Teamcenter server from their machine.

    2. An IT enterprise network may have “proxies” in place that alter hostnames and ports for browser sessions to redirect to the Teamcenter server. When connecting Syndeia with Teamcenter, users must directly use the host URL and port for the Teamcenter server.

Anchor
Collect-Teamcenter-jars
Collect-Teamcenter-jars
Collect Teamcenter jar files

Follow the The steps in this section to gather and assemble Teamcenter jar files. These are required for Syndeia to connect with Teamcenter using its published API.

  1. Create a folder named libTC to collect all the jar files needed for Teamcenter.

  2. The last section on this page - List of Teamcenter jar files - lists all the jar files that need to be collected from your Teamcenter server for each supported Teamcenter version.

  3. 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.

    1. The second set is “optional” because they are only required to be present if the user optionally intends to be using the Teamcenter Rich Client. If not, then those files under “Files from the Teamcenter Rich Client Installation” are not required for Syndeia use.

  4. The first location (Location 1) to gather the jar files from is your Teamcenter install media (or server installation). The Teamcenter install media (or server installation) has a soa_client.zip file at the root level, e.g. <Your TC installation media>/TC-14.3.0/lnx64/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 media>/TC-14.3.0/lnx64/soa_client/java/libs.

    3. Copy all the jar files listed for Location 1 (LHS column) in the table below to the libTC folder.

  5. Optional: The second location (Location 2) to gather the jar files from is the Teamcenter rich client installation from any machine where it is installed, e.g. <Your TC rich client installation>\portal\plugins\com.teamcenter.rac.external_11000.2.0 OR <Your TC rich client installation>\TcRoot\portal\plugins\com.teamcenter.rac.external_11000.2.0

    1. Copy all the jar files listed for Location 2 (RHS column) in the table below to the libTC folder.

  6. Now, the libTC folder should have all the jar files, as listed in the section List of Teamcenter jar files from Location 1 and optionally from Location 2.

  7. Keep the libTC folder at a known location.

  8. Additional notes:

    1. 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.

    2. As we expand Syndeia’s capabilities with each release, the list of jar files required may update, i.e. additional jar files may be needed. The section List of Teamcenter jar files will be revised in that case.

Configure Syndeia to connect with Teamcenter

...

stage should be performed once by Syndeia / Teamcenter admins for all users of the Syndeia Rhapsody plugin.

  1. Syndeia / Teamcenter admins should collect the *.jar files in the Teamcenter SOA library that are required for connecting with Teamcenter. Refer to the details on the following page: ​Appendix G2a - Gather Teamcenter library (jar files).

  2. The libTC folder provided in the step above can be used for all Syndeia clients - Cameo/Rhapsody plugins, Standalone, and Syndeia Web Dashboard.

Anchor
Syndeia-connect-Teamcenter
Syndeia-connect-Teamcenter
Configure Syndeia Rhapsody plugin to connect with Teamcenter

The steps in this stage should be performed by all users of the Syndeia Rhapsody plugin that will be connecting with Teamcenter.

  1. Your Syndeia / Teamcenter admin should have provided you a libTC folder with *.jar files, based on the instructions above.

  2. Copy the libTC folder to the Syndeia Rhapsody plugin location, as stated in Step 5 of the Syndeia Rhapsody plugin installation instructions: Install Syndeia plugin.

  3. Complete the Syndeia Rhapsody plugin installation process.

  4. In the Syndeia Dashboard, add a Teamcenter repository by following the instructions here: Adding a Repository.

  5. Follow the Syndeia Teamcenter tutorials - Part 11 - SysML-Teamcenter Capabilities. - to learn more.

List of Teamcenter jar files

The list of Teamcenter jar files you will need for each supported Teamcenter version is provided below.

Copy all the jar files from the same Teamcenter server installation (version), and do not mix and match them from different Teamcenter installations in your organization.

...

titlelibTC File set for Teamcenter 9

...

Location 1 - Files from the Teamcenter Server Installation Disk(s) / Media

...

Location 2 - Files from the Teamcenter Rich Client Installation

...

avalon-framework-4.1.5.jar

...

activation.jar

...

commons-codec.jar

...

  1. .

...

commons-httpclient-3.1.jar

...

ApplicationRegistryClient.jar

...

commons-logging.jar

...

concurrent-1.3.2.jar

...

fmsutil.jar

...

fccjavaclientproxy.jar 

...

jacorb.jar

...

fmsservercache.jar 

...

log4j.jar

...

fscjavaclientproxy.jar 

...

resolver.jar

...

idl.jar

...

tccommservice.jar

...

jgraph.jar

...

tcgatewaystubs.jar

...

mail.jar

...

tcmemjavabinding.jar

...

soap.jar

...

tcserverjavabinding.jar

...

TcGatewayWebService.jar 

...

TcSoaBomStrong_9000.1.0.jar

...

wrapper-3.0.3.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

...

titlelibTC File set for Teamcenter 11

...

Location 1 - Files from the Teamcenter Server Installation Disk(s) / Media

...

Location 2 - 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

...

commons-logging.jar

...

concurrent-1.3.2.jar

...

fmsutil.jar

...

fccjavaclientproxy.jar 

...

jacorb.jar

...

fmsservercache.jar 

...

log4j.jar

...

fscjavaclientproxy.jar 

...

resolver.jar

...

idl.jar

...

tccommservice.jar

...

jgraph.jar

...

tcgatewaystubs.jar

...

mail.jar

...

tcmemjavabinding.jar

...

soap.jar

...

tcserverjavabinding.jar

...

TcGatewayWebService.jar 

...

TcSoaBomStrong_11000.2.0.jar

...

wrapper-3.0.3.jar

...

TcSoaBomTypes_11000.2.0.jar

...

TcSoaCadStrong_11000.2.0.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

...

titlelibTC File set for Teamcenter 12

...

Location 1 - Files from the Teamcenter Server Installation Disk(s) / Media

...

Location 2 - 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

...

commons-logging.jar

...

concurrent-1.3.2.jar

...

fmsutil.jar

...

fccjavaclientproxy.jar 

...

jacorb.jar

...

fmsservercache.jar 

...

log4j.jar

...

fscjavaclientproxy.jar 

...

resolver.jar

...

idl.jar

...

tccommservice.jar

...

jgraph.jar

...

tcgatewaystubs.jar

...

mail.jar

...

tcmemjavabinding.jar

...

soap.jar

...

tcserverjavabinding.jar

...

TcGatewayWebService.jar 

...

TcSoaBomStrong_12000.4.0.jar

...

wrapper-3.0.3.jar

...

TcSoaBomTypes_12000.4.0.jar

...

TcSoaCadStrong_12000.4.0.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

...

titlelibTC File set for Teamcenter 13

...

Location 1 - Files from the Teamcenter Server Installation Disk(s) / Media

...

Location 2 - 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

...

commons-logging.jar

...

concurrent-1.3.2.jar

...

fmsutil.jar

...

fccjavaclientproxy.jar 

...

jacorb.jar

...

fmsservercache.jar 

...

log4j.jar

...

fscjavaclientproxy.jar 

...

resolver.jar

...

idl.jar

...

tccommservice.jar

...

jgraph.jar

...

tcgatewaystubs.jar

...

mail.jar

...

tcmemjavabinding.jar

...

soap.jar

...

tcserverjavabinding.jar

...

wrapper-3.0.3.jar

...

TcSoaBomStrong_13000.0.0.jar

...

TcSoaCadStrong_13000.0.0.jar

...

TcSoaClient_13000.0.0.jar

...

TcSoaCommon_13000.0.0.jar

...

TcSoaCoreStrong_13000.0.0.jar

...

TcSoaCoreTypes_13000.0.0.jar

...

TcSoaQueryStrong_13000.0.0.jar

...

TcSoaStrongModel_13000.0.0.jar

...

teamcenter_sso_applib.jar

...

teamcenter_sso_common.jar

...

xerceslmpl.jar

...

xml-apis.jar

...

titlelibTC File set for Teamcenter 14

...

Location 1 - Files from the Teamcenter Server Installation Disk(s) / Media

...

Location 2 - 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

...

commons-logging.jar

...

concurrent-1.3.2.jar

...

fmsutil.jar

...

fccjavaclientproxy.jar 

...

jacorb.jar

...

fmsservercache.jar 

...

log4j.jar

...

fscjavaclientproxy.jar 

...

resolver.jar

...

idl.jar

...

tccommservice.jar

...

jgraph.jar

...

tcgatewaystubs.jar

...

mail.jar

...

tcmemjavabinding.jar

...

soap.jar

...

tcserverjavabinding.jar

...

wrapper-3.0.3.jar

...

TcLogging.jar

...

TcSoaBomStrong_14000.3.0.jar

...

TcSoaCadStrong_14000.3.0.jar

...

TcSoaClient_14000.3.0.jar

...

TcSoaCommon_14000.3.0.jar

...

TcSoaCoreStrong_14000.3.0.jar

...

TcSoaCoreTypes_14000.3.0.jar

...

TcSoaQueryStrong_14000.3.0.jar

...

TcSoaStrongModel_14000.3.0.jar

...

teamcenter_sso_applib.jar

...

teamcenter_sso_common.jar

...

xerceslmpl.jar

...