Scribd
Upload
173 views15 pages

Teamcenter Architecture

Uploaded by

Nandini Kapure
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
173 views15 pages

Teamcenter Architecture

Uploaded by

Nandini Kapure
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Teamcenter Architecture

Teamcenter two-tier architecture

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.
2-Tier Architecture
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.
4-Tier Architecture

pool manager
From Client to Web Application Server

• Client interacts with Web Application


Server via HTTP protocol.
• Web Servers are good at serving files. Web
server takes request from client and maps
it to the file on file system and sends the
file back to the client.
• A cache is maintained for this static
content (files that are not generated or
modified) and it can reliably and effectively
find the file and send it back.
• For any logical (teamcenter queried
data) or dynamic content (files that are
generated or changed), web server cannot
do it on its own. It has to delegate the
request to enterprise tier, and this is
From Web Application Server to Teamcenter Server

 Web Application Server sends the


requests it cannot handle to server
manager at enterprise tier.
 TreeCache is maintained for web
application that tells it to send the
particular request to server
manager at enterprise tier.
 The host and port of server
manager at which the request has
to be sent is listed in its treecache.
There has to be a server with this
host and port to receive the request
at enterprise tier.
• After acknowledging the receipt of request, request is
processed and resulting logical or dynamic content is sent
back to web server for the client to receive it. To send the
information back to web tier, there is another treecache
employed for server manager at enterprise tier.
• This treecache will have information of port and host of
the web application where the content has to be sent
back. This mode of communication between web
application server and server manager is called TCP mode.
From Teamcenter Server to Database and File
Server

• Information is stored and retrieved


from database or file server. The
information is then passed back to
teamcenter server in enterprise tier
and eventually to client.
• For managing files, FMS Client
Cache (FCC) process runs on client
host. This FCC on client host
requests for files or upload files to
FMS Server Cache (FSC) running as
volume server.
FSC

• FSC know as FMS server cache and it work at server side.


• FSC it will communicate with volume and with the help of
volume they will fetch the data and they will store the
data(FSC serves does this).
• On server this FSC is there and master.xml
• In the master.xml ,we have FSC_ID+volume_path.
FMS

• FMS stands for file management system.


• When user send a request for some file then intitally FMS check in
its local cache if FMS get any latest information then it will open
the data from local cache or else it will get back to FMS master
and for volume reference then the data is open for user
FCC

 FCC is known for FMS client cache


 Basically this FCC work on client cache, where this FCC will
interacts with FSC for user request.
TC_data
 TC_Data=model+AM+workflow
 TC_data contains all the data models about BMIDE
 TC_Data has model directory like teamcenter schema directory a
POM_schema.
 Lilke in BMIDE we create our own data model and we can customies the
data model so that data model file is know by model folder.
 TC_data model is most important for teamcenter data model structure
 TC_profilevar.bat is one most important file in teamcenter which contains
all environment variable(path like license server path, java,database) are
present.so this is the main file which will communicate with database
TC_ROOT
 TC_ROOT=Bin+lib+FSC+include+log+data
 TC_ROOT has log files, in log there is installation. For EX: during
TC installation if installation fails then we get that installation
path in install, log in sys log folder
 TC_ROOT it contains include folder which has all header files
because server is on c++.
 TC_ROOT we have all kinds of folder like security, bin, BMIDE,
data.
TC_VOLUME

 VOLUME in Teamcenter is a physical vault where all your files


like the documents, Drawing Files, Models, etc. are stored in a
physical mode as we store the files on our own PCs in the Drives
or Folders.

You might also like