Teamcenter session management

0
Hi Team,I am looking for the solution where i want to embed MX application with Active workspace. Using mendix 10, we can embed iframe in Active Workspace. Default TC session is shared between AW and Mx.Question:Will that affect performance of AW due to shared TC session?As per understanding, only 1 TC licence is checked out. Please confirmIf performance of AW will be impacted dut to shared session, 3.1 can we create separate session for Mx? 3.2 Does it checkout second license for TC? 3.3 Is there anyway we can have separate session but only 1 licese will be checked out?Is ther any better solution possible using higher version of Mendix then please suggest the same.
asked
1 answers
0

Hi Vidula,

We've implemented a similar Active Workspace + Mendix integration, and I'd separate the discussion into session isolation and licensing.

Regarding performance, sharing the same Teamcenter session is generally not a licensing concern, but it can become a performance concern when Active Workspace and the Mendix application are generating significant Teamcenter traffic at the same time. Long-running searches, BOM expansions, or bulk operations initiated from Mendix can impact the responsiveness perceived by users in AW.

For your questions:

1. Will a shared TC session affect AW performance?

Potentially yes. If both applications are effectively operating through the same Teamcenter server context, heavy requests from one side can affect the user experience on the other side.

2. Will only one Teamcenter license be checked out?

In most SSO-based integrations, licensing follows the authenticated user rather than the number of sessions. However, licensing models vary between Teamcenter deployments, so I would still validate this with your Teamcenter administrator or Siemens representative before making architectural decisions based on it.

3. Can Mendix have a separate session?

Yes. The approach we used was to isolate the Mendix Teamcenter session while keeping the same user identity through SSO.

3.1 Separate session for Mendix?

Yes, this is possible and is generally the preferred approach when you want to shield AW from Mendix workload.

3.2 Does it consume a second license?

Typically licensing is tied to the user, not the session itself, but confirm this for your Teamcenter licensing model.

3.3 Separate session but one license?

This is usually achievable when both applications operate under the same authenticated user identity.

Also, if you're evaluating future architecture, I would strongly recommend looking at Mendix 11.12+ "Mendix Inside Teamcenter" instead of relying solely on iframe embedding. Besides providing a smoother user experience, it simplifies context sharing and avoids some of the iframe-related limitations we've had to handle in older implementations.

My recommendation would be:

  • Use SSO for a seamless user experience.
  • Isolate Mendix and AW sessions where possible.
  • Validate licensing assumptions with your Teamcenter admin team.
  • Consider upgrading to a newer Mendix version and evaluating the native Teamcenter integration capabilities before investing further in the iframe approach.

Hope this helps.


answered