Overview

The following steps will guide you to extract and install the Siemens Teamcenter library .jar files for use with Syndeia Cloud (SC). These jar files are required for Syndeia to communicate with Teamcenter using its SOA (Java) API.

Steps

1. Collect Siemens Teamcenter library (*.jar) files: Follow the instructions here Using Syndeia with Teamcenter to collect all the jar files needed from the Teamcenter server in a local directory named lib_TC(you can skip “Configure Syndeia to connect with Teamcenter” section for now)in the child page Appendix G2a - Gather Teamcenter library (jar files) to prepare a libTC folder with all the *.jar files needed for Syndeia to connect with Teamcenter.

2. Copy the Siemens Teamcenter libs: Copy the Siemens Teamcenter .jar files from the libTC folder (collected in previous step) to the new TC sub-directory under lib of each respective the teamcenter-impl microservice on the SC server, ie:

   1. On Linux 🐧 ,

      1. Copy the .jar files to /opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/lib/TC and ensure the user & group ownership of those files is set to syndeia-cloud:syndeia-cloud by running the below from a bash shell:

         Code Block
         language bash
         SC_HOME=/opt/icx/syndeia-cloud-current/ SC_snapshot_version=3.6-SP1 # update as needed if you are running a different version sudo -u syndeia-cloud mkdir "${SC_HOME}"/teamcenter-impl-"${SC_snapshot_version}"/lib/TC sudo cp ~/lib_TC/*.jar "${SC_HOME}"/teamcenter-impl-"${SC_snapshot_version}"/lib/TC/. sudo chown syndeia-cloud:syndeia-cloud "${SC_HOME}"/teamcenter-impl-"${SC_snapshot_version}"/lib/TC/*.jar

   2. On Windows 🪟 ,

      1. Copy the .jar files to, ex: c:\cygwin64\opt\icx\syndeia-cloud-current\teamcenter-impl-3.6-SP1\lib\TC

3. Set Environment Variables for Logging

   1. Administrators supporting Syndeia and any Teamcenter version should edit the file /etc/systemd/system/sc-tc.service to change the Environment= setting to this value:

      Code Block
      language bash
      # update as needed if you are running a different version Environment='SC_snapshot_version=3.6-SP1' 'SIEMENS_LOGGING_ROOT=/opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/logs" "TC_SOACLIENT_DATA=/opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/logs'

4. Restart the respective services, ie:

   1. On Linux 🐧 , sudo systemctl restart sc-tc

   2. On Windows 🪟 , use services.msc (Windows Services Manager) or from CMD.EXE run:

      Code Block
      language java
      sc.exe stop sc-tc sc.exe start sc-tc

Verification

1. Verify that the Teamcenter Service Starts and Stays Running

   1. Use sudo systemctl start sc-tc to start the microservice and then sudo systemctl status sc-tc to monitor that the service began and remains operational.
      
      Look for a report like this - which has a long and growing “Active” runtime.

      Code Block

      ● sc-tc.service - Syndeia Cloud 3.6 TEAMCENTER service: Integrated model-based engineering tool to generate, connect, compare and sync Loaded: loaded (/etc/systemd/system/sc-tc.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2024-10-01 12:41:15 EDT; 1 months 6 days ago Process: 256420 ExecStartPre=/bin/bash -c if [[ -e /run/syndeia-cloud/tc/RUNNING_PID ]]; then { if ! pgrep -F /run/syndeia-cloud/tc/RUNNING_PID; then rm /run/syndeia-cloud/tc/RUNNING_PID; else echo 'Syndeia Cloud: already running'; fi; } fi; (code=exited, status=0/SUCCESS) Main PID: 256464 (java) Tasks: 63 (limit: 102192) Memory: 88.6M CGroup: /system.slice/sc-tc.service └─256464 java -Dpidfile.path=/run/syndeia-cloud/tc/RUNNING_PID -Dconfig.file=/opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/conf/application.conf -Dlogger.file=/opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/conf/prod-logback.xml -Duser.dir=/opt/icx/syndei>

2. Verify Teamcenter Logging

   1. Confirm that the directory /opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/logs has a teamcenter.log file with the current day modification time

   2. Confirm that the SOA logging setting is effective by observing the file ForkJoinExecutorConfigurator$AkkaForkJoinTask_soa_<TIMESTAMP>.log in the directory /opt/icx/syndeia-cloud-current/teamcenter-impl-3.6-SP1/logs This file will appear soon after attempting to use the Teamcenter integration within the Syndeia Web Dashboard.

   3. Confirm that this file begins with content much like the following:

      Code Block
      language yaml
      2024/09/23-21:22:21.574 UTC - INFO - - 0A58CE5C5 - - - Teamcenter Services Client Version: V14000.3.0.20230530.00 2024/09/23-21:22:21.627 UTC - INFO - - 0A58CE5C5 - - - InitializePolicy Default/Default 2024/09/23-21:22:21.758 UTC - INFO - - 0A58CE5C5 - - - Connecting to Teamcenter server through http://myTCserver.domain.tld:7001/tc 2024/09/23-21:22:24.027 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR001 - Service Request: Core-2008-06-Session.login (Time: 1698ms, Request: 21bytes, Response: 10Kb ) 2024/09/23-21:22:24.520 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR002 - Service Request: Core-2011-06-Session.getTypeDescriptions (Time: 454ms, Request: 2Kb , Response: 858Kb ) 2024/09/23-21:22:24.757 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR003 - Service Request: Core-2011-06-Session.getTypeDescriptions (Time: 19ms, Request: 222bytes, Response: 14Kb ) 2024/09/23-21:22:24.794 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR004 - Service Request: Core-2011-06-Session.getTypeDescriptions (Time: 21ms, Request: 211bytes, Response: 14Kb ) 2024/09/23-21:22:24.834 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Service Request: Core-2007-01-Session.getTCSessionInfo (Time: 20ms, Request: 139bytes, Response: 5Kb ) 2024/09/23-21:22:24.842 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Server Information: 2024/09/23-21:22:24.842 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Version: V14000.3.0.20230530.00 2024/09/23-21:22:24.842 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Display Version: 14.3:20230530.00 2024/09/23-21:22:24.842 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Host Name: myTCserver.domain.tld 2024/09/23-21:22:24.842 UTC - INFO - - 0A58CE5C5 - - 0CD9A8B2FR005 - Log File: tcserver4039382.syslog

3. Validate Syndeia Teamcenter operation

   1. To validate (like an end-user) that the Syndeia Cloud Teamcenter service can connect with your Teamcenter server, follow the steps in the Teamcenter tutorial for the Syndeia Web Dashboard.

Exercise 11.1 - Teamcenter Integration