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 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 .jar files from the libTC folder (collected in previous step) to the new TC sub-directory under lib of 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:

         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:

      # 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:

      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.

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:

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.