Document Mendix inside Teamcenter (public Beta, 11.12) by jdiehl · Pull Request #11384 · mendix/docs

jdiehl · 2026-06-19T10:24:55Z

Description

New reference page under /refguide/mendix-client/mendix-inside-teamcenter/ documenting how to embed a Mendix web app as a native component inside Siemens Teamcenter Active Workspace using the embedded client.

This builds on the embedded client documentation added by @WimJongeneel in #11204 and is tied to the 11.12 release.

Changes

New page: refguide/runtime/mendix-client/mendix-inside-teamcenter.md
Updated refguide/runtime/mendix-client/_index.md with a cross-reference to the new page

Coverage

The new page covers:

Version prerequisites (Beta: Mendix 11.12 / TC 2512; GA: Mendix 11.18 / TC 2612)
Adding an Embedded navigation profile in Studio Pro
Configuring CORS (concrete runtime settings and m2ee.yaml example)
Installing the MendixEmbedded AWC component and registering it on a page
Configuring the Teamcenter CSP (gateway/config.json directives)
Authentication via Teamcenter SSO (links to TC Connector docs)
Passing Teamcenter context as startup parameters (code example)
Known Beta limitations

CLAassistant · 2026-06-19T10:25:02Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Jonathan Diehl seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

wanchoorohan

Provided few suggestions.

wanchoorohan · 2026-06-19T13:10:49Z

+
+## Introduction
+
+Mendix inside Teamcenter lets you embed a Mendix web app as a native component inside Siemens Teamcenter Active Workspace (AWC). The Mendix app runs directly in the AWC page as a micro-frontend using the [Embedded Client](/refguide/mendix-client/embedding-the-client/) feature.


AWC is not the correct acronym. We use it internally but its not correct. AW is the correct one but its not used externally. It should be Active Workspace.

wanchoorohan · 2026-06-19T13:12:05Z

+
+| | Mendix | Teamcenter | Teamcenter Connector |
+| --- | --- | --- | --- |
+| **Beta** | 11.12 | 2512 | 2512.1.0 or above |


Don't you need TcC 2606 for the login enhancements? - https://mendix.slack.com/archives/C0B6TMJ3SUC/p1781199462908459

Yes indeed, the user should use TcC 2606 with the latest changes (which is compatible with 2512 if I understood correctly)

wanchoorohan · 2026-06-19T13:16:34Z

+2. Install the component into your Active Workspace stage repository under `src/repo`.
+3. Configure the component with the URL of your Mendix runtime.
+4. Optionally, set up context passing. For more information, see [Passing Context from Teamcenter](#passing-context).
+5. Rebuild Active Workspace.


Can we provide the command to do this? Is it awbuild?

Yes indeed, it is awbuild.cmd. I would assume the user to know this already though, not sure if we need to add it to the docs

wanchoorohan · 2026-06-19T13:17:10Z

+4. Optionally, set up context passing. For more information, see [Passing Context from Teamcenter](#passing-context).
+5. Rebuild Active Workspace.
+
+To verify the component was picked up correctly, check that its view model entry exists in the `pathMap.json` registry file in the build output.


Where does pathmap.json reside? Would the users know this?

It is located at src/repo/out/pathMap.json, not sure if this is common knowledge. Not sure if this is needed

wanchoorohan · 2026-06-19T13:17:53Z

+
+### Registering the Component on a Page
+
+To display the Mendix app on an Active Workspace page, add a card definition for it to the relevant `layoutsViewModel.json` file in your AWC stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime:


Same question for layoutsViewModel.json

This is located in the src/repo, but depends on which PL Home screen you want to add the card to. Would be nice if there is Teamcenter documentation we can link to, but I cannot find that.

brambrink · 2026-06-22T08:41:20Z

+
+The following example shows how the AWC component passes a selected Teamcenter item UID to the Mendix app:
+
+```js


This example corresponds more to the actual component:

(including PascalCase for parameter key)

const app = await import(/* webpackIgnore: true */ `${mendixUrl}'dist/embedded-index.js'`); cleanup = await app.render(container, { remoteUrl: mendixUrl, minHeight: '100vh', parameters: { SelectedItem: selectedItem } });

brambrink · 2026-06-22T08:57:00Z

+
+1. **Add an SSO Login Button to the Login Page**:
+
+    Add a Teamcenter SSO login button to the Mendix app's `login.html` so users can initiate the TcSS authentication flow. For instructions, see [Adding an SSO Login Button to Your Login Page](/appstore/modules/siemens-plm/configuring-connection-2512/#add-sso-login-button). Optionally, use JavaScript to trigger the authentication automatically. Note that browsers may block the popup unless it is triggered directly by a user action.


See above, this should be removed

brambrink · 2026-06-22T08:59:22Z

+
+1. **Configure User Provisioning**:
+
+    Set up user provisioning so that Mendix accounts are matched to Teamcenter users on login. For instructions, see [User Provisioning for SSO](/appstore/modules/siemens-plm/configuring-connection-2512/#user-provisioning-for-sso).


User provisioning should be setup for SSO with User Provisioning for Logged-In Use. Anonymous users should ideally be disabled.

brambrink · 2026-06-23T08:34:34Z

+
+## Configuring Authentication {#authentication}
+
+During Beta, authentication uses the Teamcenter Connector's Teamcenter SSO flow. The Mendix app login page shows an SSO button. When a user clicks it, they are redirected to Teamcenter Security Services (TcSS) for authentication. After a successful login, TcSS redirects back to the Mendix app, where the user is provisioned or matched to an existing Mendix account and a Teamcenter Connector session is established.


This part is incorrect. There is no need to add an SSO button, after setting up the Teamcenter connector, the authentication is done with the popup logic in the AW component, which uses the Tc Connector published REST endpoint, no need to change login.html.

brambrink · 2026-06-23T08:39:19Z

+1. **Add an SSO Login Button to the Login Page**:
+
+    Add a Teamcenter SSO login button to the Mendix app's `login.html` so users can initiate the TcSS authentication flow. For instructions, see [Adding an SSO Login Button to Your Login Page](/appstore/modules/siemens-plm/configuring-connection-2512/#add-sso-login-button). Optionally, use JavaScript to trigger the authentication automatically. Note that browsers may block the popup unless it is triggered directly by a user action.
+


Instead, for now the following needs to be configured (there are plans to improve this):

Add a JavaScript action called JS_CloseWindow with the following:

*/ export async function JS_CloseWindow() { // BEGIN USER CODE window.close(); // END USER CODE }

Add a Nanoflow that calls this JavaScript action

Add an empty page called 'AuthSuccess' to the application which contains an 'Component load' event that calls this Nanoflow

Change the DL_HandleSSOLoginMicroflow to show AuthSuccess instead of the home page as the last action in the Microflow.

MarkvanMents · 2026-06-23T13:06:03Z

@jdiehl
There still seems to be discussion on the content of this. Can you let me know when it is ready to be reviewed by the technical writers?
Thanks.

Document Mendix inside Teamcenter (public Beta, 11.12)

3abdf8f

MarkvanMents self-requested a review June 19, 2026 10:44

MarkvanMents self-assigned this Jun 19, 2026

MarkvanMents added Needs language review 11.12 LTS labels Jun 19, 2026

wanchoorohan reviewed Jun 19, 2026

View reviewed changes

brambrink suggested changes Jun 23, 2026

View reviewed changes


		## Introduction

		Mendix inside Teamcenter lets you embed a Mendix web app as a native component inside Siemens Teamcenter Active Workspace (AWC). The Mendix app runs directly in the AWC page as a micro-frontend using the [Embedded Client](/refguide/mendix-client/embedding-the-client/) feature.


		### Registering the Component on a Page

		To display the Mendix app on an Active Workspace page, add a card definition for it to the relevant `layoutsViewModel.json` file in your AWC stage repository. Set `declarativeKeyContext` to the URL of your Mendix runtime:


		The following example shows how the AWC component passes a selected Teamcenter item UID to the Mendix app:

		```js


		1. Add an SSO Login Button to the Login Page:

		Add a Teamcenter SSO login button to the Mendix app's `login.html` so users can initiate the TcSS authentication flow. For instructions, see [Adding an SSO Login Button to Your Login Page](/appstore/modules/siemens-plm/configuring-connection-2512/#add-sso-login-button). Optionally, use JavaScript to trigger the authentication automatically. Note that browsers may block the popup unless it is triggered directly by a user action.


		1. Configure User Provisioning:

		Set up user provisioning so that Mendix accounts are matched to Teamcenter users on login. For instructions, see [User Provisioning for SSO](/appstore/modules/siemens-plm/configuring-connection-2512/#user-provisioning-for-sso).


		## Configuring Authentication {#authentication}

		During Beta, authentication uses the Teamcenter Connector's Teamcenter SSO flow. The Mendix app login page shows an SSO button. When a user clicks it, they are redirected to Teamcenter Security Services (TcSS) for authentication. After a successful login, TcSS redirects back to the Mendix app, where the user is provisioned or matched to an existing Mendix account and a Teamcenter Connector session is established.

Conversation

jdiehl commented Jun 19, 2026

Description

Changes

Coverage

Uh oh!

CLAassistant commented Jun 19, 2026

Uh oh!

wanchoorohan left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MarkvanMents commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants