Siemens Teamcenter

The Teamcenter backend supports loading data over multiple addressing schemes. Items can be addressed by:

• Their Item ID and Revision.

• Their DataSet ID.

• Their Item UID.

Furthermore, it is possible to load assemblies either as a PLMXML export or directly via their native NX representation. Using the native representation is usually more performant as Teamcenter does not need to generate a PLMXML export on the fly.

To configure the backend, several options must be set:

teamcenter:
  # Whether the Teamcenter backend is enabled.
  enabled: false
  # The HTTP Teamcenter server URL under which HTTP endpoints are available.
  # Example: http://teamcenter.company.com:7001
  baseUrl:
  # The HTTP Teamcenter FMS URL under which file resources are available.
  # Example: http://teamcenter.company.com:4455
  fmsBaseUrl:
  # Options when using the PLMXML export path.
  plmxmlExport:
    # The internal Teamcenter UID of the revision rule to use.
    revisionRuleUid:
    # The internal Teamcenter UID of the transfer mode to use.
    transferModeUid:
  # Whether to use a technical user for accessing Teamcenter. If false,
  # a valid session token must be provided with each client request.
  useTechnicalUser: true
  # User credentials when using a technical user.
  user:
    name:
    password:
    group:
    role:

After configuration the following endpoints will be available to configure as URNs for data pool rules:

• /tc/plmxml/{id}: Returns a PLMXML for the Teamcenter ID. The configured revision rule and transfer mode are used.

• /tc/part/{id}: Returns a file for the given Teamcenter UID. This UID is usually found in PLMXML files as part of an ApplicationRef.

• /tc/prt/structure/{id}: Loads the UGMASTER of the given Item ID. The latest revision is used.

• /tc/prt/structure/{id}/{revision}: Loads the UGMASTER of the given Item ID and Revision.

• /tc/prt/part/{id}: Loads the file behind the given DataSet ID.

---

Was this page helpful? Please leave a thumbs up or down.

👍 Yes 👎 No