TC Extension Sample App v 5.1.0 & TC Connector 2512.1.1

0
Hi everyone,I've downloaded and tested TC_Extension_Sample_App V 5.1.0 against a self-hosted Teamcenter 2506 environment.The sample app was not originally using the latest Teamcenter Connector version, so I upgraded the connector in the sample app to Teamcenter Connector 2512.1.1.According to the compatibility matrix, Teamcenter Connector 2512.1.1 supports Teamcenter 2506.However, after creating a self-hosted configuration for Teamcenter 2506 and logging in, I get the following warning:No Teamcenter sessionCurrently there is no active Teamcenter Session. Please sign in first.The session appears to be created and marked as active, but the sample app still behaves as if no Teamcenter session exists. I then tested another configuration pointing to Teamcenter 2512, and that works correctly.After investigating, I found that the microflow DS_GetTcSessionByCurrentUser, located in the SampleApp module, appears to check for a specific cookie name: JSESSIONID.This works for our Teamcenter 2512 environment, where the session cookie is named JSESSIONID.However, in our Teamcenter 2506 environment, the session cookie is named ASP.NET_SessionId instead. Because of this, it looks like the sample app cannot detect the active Teamcenter session, even though login appears to complete successfully.I was able to modify the microflow to check for the correct cookie name used by our TC2506 environment, but the app still fails afterwards. I have not yet fully investigated the next failure point.I have not yet tested this in a completely new standalone Mendix app using only the Teamcenter Connector from scratch, so at the moment I am seeing this behaviour specifically in TC_Extension_Sample_App V 5.1.0, after upgrading its connector to 2512.1.1.Has anyone else seen this behaviour with Teamcenter 2506?Is this expected depending on the Teamcenter deployment/configuration, or could this be an issue in the SampleApp session-detection logic?Any advice would be appreciated.Thanks!
asked
2 answers
0

I have fix it by amendig both DS_GetTcSessionByCurrentUser and Rule_UserIsLoggedIntoTeamcenter rule to check for ASP.NET_SessionId cookie name instead.

answered
0

Hi Tomasz! It seems you managed to figure out the issue, so that's good. And you diagnosis makes sense. But just for posterity


  • Yes Teamcenter Connector 2512.1.1 is compatible with Teamcenter 2506,
  • Also it's fine to update the Teamcenter Connector within the sample app
  • The issue you encountered indeed relates that the Teamcenter Sample App assumes that there's a JSESSIONID cookie available, however in your case that's ASP.NET_SessionId. Possibly there's a IIS server somewhere in your setup instead.
  • The solution is to check for the different cookie name in DS_GetTcSessionByCurrentUser and Rule_UserIsLoggedIntoTeamcenter


To confirm: you are now able to succesfully log in to Teamcenter from the Sample App?

answered