Skip to main content

Teamcenter Architecture

Teamcenter Architecture


 Teamcenter architecture provides two types of client-server software architecture pattern. In both two-tier and four-tier teamcenter architecture, separate modules are developed and maintained independently on same or separate platforms.

4-Tier Architecture
Four tier architecture model has following tiers:

  • Client Tier
Client tier comprises of rich client (java application), thin client(provides access to teamcenter through web browser, UI provides browser based view) and other clients that provides additional functionality to rich client such as Teamcenter Integration for NX, Lifecycle Visualization or Teamcenter Client for Microsoft Office. These additional client features require web-tier.
Four-tier rich client is installed over the network by over-the-web installer. It is launched from web browser, but after installation four-tier rich client does not need the web browser.
  • Web Tier
Web tier is a java application that runs web application server such as Oracle Weblogic. This is a third party application that is responsible for communication between client tier and enterprise tier. TreeCache is employed at both web tier and enterprise tier in a synchronized manner for the communication.
Web tier also provides configuration for thin client and four tier rich client installation on users machine. Web tier includes Web Application Manager, a distribution server and a distribution server instance. Only one distribution server is required to manage multiple distribution server instances. Distribution server instancecontains the Over-the-Web installer and Rich Client 4-tier solution to install particular configuration of rich client on different machines.URL is provided to users in network for the installation.
Web Application Manager builds EAR file .It is then deployed to web application server on web tier host. Users access the thin client from browser using web tier host.
  • Enterprise Tier
Enterprise tier comprises of server pool (teamcenter server processes) and a server manager (called pool manager for J2EE based server manager) to manage the pool.
In four tier environment, where large number of users login simultaneously and access data and files, it is good idea to maintain a server pool. This increases the re-usability and improves the overall performance of teamcenter. Users can login fast and retrieve or store information quickly.
Pooling is a process where cache of database connection objects is maintained. Creating connections again and again in four tier environment is too expensive and exhaustive. In the pool, connection objects are created ahead of time when server manager starts. This pool of connections is managed by pool manager/server manager. When user requests for a connection, pool manager disperses a connection object from the pool and when user is finished with teamcenter session, it returns the connection object back to pool.
Server Manager & TreeCache
A treecache is also configured for server manager to communicate with web application server. Information retrieved by teamcenter server in the pool is sent to web application server (in web tier) by server manager. Treecache parameters help server manager to find the web application server. The requested information will be further sent to client by web tier.
Also Note: Four-tier architecture allows maintaining multiple server managers. Each of the server manager will have a separate treecache configuration. Multiple server managers will be preferred, when huge number of users login and access data. Each server manager can then maintain a manageable pool of teamcenter servers without affecting performance.
  • Resouse Tier
Resource tier comprises of database server, database, volumes and file servers. It is recommended to run server manager and volume server (FSC running on same host, where volume is located) on the same host.


2-Tier Architecture


Two tier architecture model comprises of following tiers:

Client Tier

Two-tier rich client is installed only through TEM. Teamcenter server runs on client workstation. Since this architecture is intended for creating local standalone instance of teamcenter, there will be no enterprise tier( no need to maintain a server pool) and there is no need of web tier (no http protocol).So web tier and resource tier are skipped in two tier architecture and teamcenter server runs directly on client machine.

Resource Tier

Resource tier comprises of database server, database, volumes and file servers. Teamcenter File Management System (FMS) manages the rich client access to volumes:
  • The FMS server cache (FSC) process runs on the server hosting the volume.
  • The FMS client cache (FCC) process runs on the rich client host.

Comments

Post a Comment

Popular posts from this blog

Teamcenter Basic Interview Questions

Teamcenter Basic Interview Questions Explain Teamcenter Architecture. What is the difference between 2 tier client and 4 tier Client? What is the difference between thin client and rich client? How to add a new property? How many types are there? what is the difference between attribute and property? what is the compound property? what is the complex property? Explain the business object class hierarchy ? what is the difference between user exit and server exit? what is the difference between action handler and rule handler? How to create a new menu in Teamcenter? what is the linked list? Memory allocation? what are all the different types? how to free the allocated memory? How to create a new custom Action Handler How to create a new custom Rule Handler? What is the server exit?How to create a server exit? How to call the server...
Post a Comment
Read more