Showing results for 
Search instead for 
Do you mean 
Reply

TC Architecture

We are starting to plan and build our Teamcenter infrastructure. We would like to build it using an active/active approach where active web and business logic servers exist in two geographically separate (but close) data centers and all servers connect to one database server that resides in one of those data centers. We have heard that this may not work, mainly not perform well, but we feel it should as we have other very high availability systems using this same approach without issues.

 

Is anyone using an active/active architecture approach as opposed to an active/passive one? If so, have you experienced any challenges?

 

Thanks

 

4 REPLIES

Re: TC Architecture

The biggest problem with the active\active approach is keeping the databases in sync without incurring a significant performance hit. Once that's handled then you have to worry about maintaining two separate, yet identical with the exception of the db connection string, TC_DATA directories. You'll also need multiple flavors of the rich client, one for each location, so that the correct pool manager is called. However, clients will not fail-over to the other instance if there is a problem.

 

In other words, you're recreating multi-site without all the safe guards. Good luck in your endeavor.


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: TC Architecture

Hi. Just a little refinement. In our case, we will only have one active database. So we will have web servers, active workspace and corporate servers in two locations with an active database in one of those locations. The database has some failover functionality to the other location for DR purposes but they won't both be active at the same time. 

Re: TC Architecture

Then you're doomed. The database and pool manager need to be as close as possible to prevent significant performance issues. Although the chattiness has significantly improved, the tcserver's and db are still talkative. I can't predict how the "away" pool manager and tcserver's will react when trying to source the remote TC_DATA but I can guess that it will suffer. The site that is not the same as the db will have a reduced performance.


Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: TC Architecture

Thanks for the information and expert advice. I will pass it along accordingly.