Teamcenter Connector

Content Type: Module
Categories: Connectors

Overview

This module allows you to connect to Teamcenter, the Siemens product lifecycle management system that brings together people and processes, and call SOAs to read and write data.

Teamcenter customers can receive support via Siemens Support Center at https://support.sw.siemens.com/

 

For an enhanced low-code experience, check out Teamcenter Extension. Built atop the Teamcenter Connector, the Teamcenter Extension enables developers to effortlessly harness the full capabilities of the Connector. It simplifies the visualization and access to the Teamcenter data model while automating the creation of Mendix domain models and microflows.

Documentation

The Teamcenter SOA connector allows app developers to connect to Teamcenter and call SOAs to read and write data. A named user in Mendix App using/reading/consuming data from and authoring data in a Siemens DI SW application (Ex: Teamcenter) will need at a minimum a corresponding named user consumer license or author license of the Siemens DI SW application (Ex: Teamcenter).

See documentation at: Teamcenter Connector Documentation

 

TcConnector Documentation to connect to TcX

 

The TcConnector module is intended to allow Mendix users to connect to On-prem/Cloud Teamcenter instance.

Following document describes configuration changes required to be done if Mendix App is to be configured to work with Teamcenter Instance on cloud ( TcX ).

Pre-requisite: Ensure that OIDC module and its dependent modules are added in Mendix app by referring to OIDC SSO Mendix documentation. 

Get the below details from CApS team:

  • SamAuth Mendix App client id, secret
  • SamAuth Token Exchange App client id, secret, token end point
  • SamAuth TcX App client id
  • TcX environment details(tcurl, fmsurl)

 

Installation Steps:

Please follow the given steps to configure OIDC with TcConnector

  1. Assign Users 
    1. Admin and User roles to their respective equivalents. 
  2. Give access for admin and user role for the below elements in OIDC module 
    1. Microflow: DS_GetClientConfigurationList, GetAuthorizationURL 
    2. Nanoflow: ACT_StartWebSignIn, DS_GetReturnURL, DS_StartWebLogin 
    3. Entities: ClientConfig, ClientConfig_Ext  
    4. Page: Login_Web_Button 
  3. Get the SAM Authentication details(client id, secrent automatic config url, scopes) and TcX Configuration details(tcurl, fmsurl, etc) from the Admin

 

Runtime Configuration:

  1. Launch the app and navigate to the Teamcenter configuration page.
  2. Set Is TcX Env to Yes. Enter the client id, secret and token endpoint of the token exchange app, and the client id for TcX App.

 

 

Releases

Version: 2412.0.0
Framework Version: 10.4.0
Release Notes: Release Notes (Teamcenter Connector version 2412.0.0) Following is the list of improvements/bug fixes in Teamcenter Connector version Tc2412.0.0 Note: This version of TcConnector is supported on Mendix 10.4.0 onwards Improvements: 1. Provided support for connection to TcX using SAM Auth Note: Refer Document snippet for more detailed steps on how to setup Mendix application to communicate with TcX using SAM Authentication. 2. Cleaned up some unused jars
Version: 2406.3.0
Framework Version: 10.0.0
Release Notes: Following is the list of improvements/bug fixes in Teamcenter Connector version Tc2406.0003.0 Bug fixes: 1. Upgraded TcSS jars and modified SSORedirectRequestHandler.processCallback to allow create SSO App session using JSON type. XML Type is no more supported. 2. Added Access Rules for TcConnector.Image and TcConnector.ImanFile entity. 3. Mendix Teamcenter Connector now can upload Dataset named references defined with * 4. Changed length of POM_application_object.object_string and BOMLine.object_string to 4000 to match with Teamcenter data model 5. Cleaned up userlib folder by removing unrequired jars. 6. Setting up timeout for SendService microflow to 300s.
Version: 2406.0.0
Framework Version: 10.0.0
Release Notes: Following are the list of improvements in Teamcenter Connector version Tc2406. 1. Added following associations on BomWindow • top_line (BOMWindow 1-1 BOMLine) • revision_rule (BOMWindow 1-1 BOMLine) 2. Added following associations on BomLine: • bl_revision (BOMLine 1-1 ItemRevision) 3. TcConnector.FileDocument now captures Dataset UID and ImanFile UID. • Introduced new java action GetImanFiles which retrieves ImanFile information for a given dataset. • If ImanFile's lastModifiedDate is later than the creation date of corresponding FileDocument/Image then consumer can download the file again. 4. Introduced new java action DownloadImages which downloads the ImanFile as an TcConnector.Image. Application/Consumer decides whether to download a dataset as FileDocument or an Image based on input dataset's _Type property value. 5. Multiplicity of association release_status_list is corrected (many-to-many) 6. PropertyResolver's static variable XSD_FORMAT of type SimpleDateFormat and is not thread safe. Making it local variable so as not to cause issue when gets executed through various threads. 7. Added locale support for SSO login. 8. Added action ExecuteSavedQueryWithObjectRefresh. Every time the saved query is executed using this call, a refreshed object is returned.
Version: 3.6.1
Framework Version: 10.0.0
Release Notes: This is a compatibility release only. Tc Connector was made compatible with Studio Pro version 10 onwards. No bug fixes are provided as part of this release.
Version: 3.6.0
Framework Version: 9.18.2
Release Notes: 1) Provided L10N support for SavedQuery execution Search criteria entities are used as input for invoking Teamcenter service Query-2008-06-SavedQuery/executeSavedQueries through Mendix service 'Toolbox/Teamcenter/Saved Query Search' Attributes on these input entities should be defined based on Teamcenter L10NKeys for its corresponding search criteria attribute. e.g. If the Teamcenter Saved Query has search criteria entry for 'Item ID' and its corresponding L10NKey is ItemID, then in Mendix, define the Search Criteria Entity with 'ItemID' as attribute name. Note: Criteria attribute L10NKeys does not change for locale and thus works for non-english locales too. e.g. Refer to Teamcenter Query Locale keys from \lang\textserver\en_US\qry_user_entry_names_locale.xml 2) Performance Improvements: a) Avoided instantiation of undesired types. Only the types specified in Business Object mappings are instantiated. Consuming application needs to make sure to have entries in the Business Object mappings if specific type of Model object needs to be consumed. b) BOM Expand APIs takes extra configuration parameter to decide whether to populate service data with Model objects. If consuming application does not refer to Model Objects directly from Service Data, then this new configuration parameter can be set to false during consumption.
Version: 3.5.0
Framework Version: 9.1.1
Release Notes: Bug fixes and performance improvements