Team Center Middle Tier Overview

Siemens PLM Connection
Teamcenter Middle Tier Overview

- Vikas Singh
Copyright © Siemens
Copyright
PLM©Software
SiemensInc.
AG 2008. All rights reserved.
Teamcenter Digital Lifecycle Management Solutions
Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Page 2 May-08 Siemens PLM Software
Enterprise Knowledge Management
Teamcenter Middle Tier Overview

Teamcenter 4-Tier Architecture
Key benefits
Reference Implementation Architecture
Horizontal Scalability and Failover
Server Assignment
Pool Configuration
Server Management Example
Double Failover Use Case
2-Tier and 4-Tier over WAN
Deployment
p y Scenarios

Introduction to the Teamcenter 4
4-Tier
Tier Architecture
File
Teamcenter’s unified platform Client Tier Client
Cache
architecture is built in 4 functional Rich Thin
tiers: Client Client
Separates different hardware
requirements to support Web Tier
scalability
l bilit
Web Session Manager File
Industry standard layout to Server
facilitate deployment in existing Web Services Cache
IT environments
All meta-data requests from clients Enterprise
are sent via the Web Tier to the Tier PLM Services
Enterprise Tier to be processed
All file access requests are sent PLM Business Logic
direct to file stores for direct, secure
file transfer
Resource Tier
DBMS File Stores

4
Introduction to the Teamcenter 4
4-Tier
Tier Architecture
Client Tier: File
Host client applications Client Tier Client
Cache
Provide user interface Rich Thin
Host secure file caches Client Client
Web Tier:
Route client requests
q to Web Tier
business logic Web Session Manager File
Serve static content Server
Process login requests Web Services Cache
Enterprise Tier:
Host business logic
Enterprise
Apply security rules Tier PLM Services
y
Serve dynamic content
PLM Business Logic
Resource Tier (DB)
Store persistent meta-data
Resource Tier
((tables)) and files
DBMS File Stores
5
T
Teamcenter
t 4-Tier
4 Ti Architecture
A hit t Key
K Benefits
B fit
Client Desktop
Teamcenter’s unified architecture: Client Tier

Scales
S l to allow ll thousands
h d off Client
users on a database File Cache
Supports clients both on a local

network and geographically Data
Center
distributed worldwide
Enables global collaboration Web Tier
Web Server(s)
within and across organizations
Distributed Cache
Leverages
L standards
t d d ffor File Server(s)
security, interoperability,
portability, deployment Enterprise Tier
Business Logic
Allows ggreat flexibility
y in Server(s)
deployment sizes and styles
Centralizes management of
Web and Enterprise Tiers Resource Tier
Database
Master
Server
File Server(s)
Teamcenter 4-tier
4 tier Additional Components
In addition to client and server processes in 2-tier, the 4-tier

architecture includes
Web Tier
Server Manager (on Enterprise Tier)
Technology stacks
J2EE
J2EE Web Tier application – Servlets,
Servlets JSPs,
JSPs EJBs,
EJBs JCA,
JCA CORBA,
CORBA
J2EE Application Servers, HTTP Web Servers, Proxies
.NET
.NET Web Tier application,
pp , ASP .NET 2.0,, C++/C# components
p
.NET remoting, IIS6.0, Windows 2003 Server, CORBA

Reference Implementation Architecture
Client File Caches Technology

Client Tier: CLIENT TIER Basis
J2SE, C++, .Net/C# rich clients
DHTML, Javascript, applets,
ActiveX
HTTP/S communications WEB TIER
Web Tier: File Cache Servers Fil
File Cache
C h Servers:
S
Secure TCP file transfer
Web – ASP, JSP, servlets, MS
.Net, SOAP, Web Services, IIOP
Apache, IIS ENTERPRISE TIER
Leadingg J2EE Application
pp
Servers
BEA, IBM, SUN, Oracle JBoss,…
Windows Server 2003 with .Net
Enterprise
p Tier:
C++, TCScript, CORBA, J2SE
Security/LDAP
Sun, Oracle, MS, IBM Resource Tier (Filestore)
Secure TCP file transfer
Resource Tier ((DB)) RESOURCE TIER RESOURCE
SOU C TIER
Unix, Windows, Linux (DB) (Filestore)
Oracle, SQL*Server
Teamcenter
ea ce te JJ2EE 4-Tier
e Architecture
c tectu e
Legend

Teamcenter .NET 4-Tier Architecture
Legend

Horizontal Scalability and Fail
Fail-Over
Over Support – J2EE Middle Tier

Horizontal Scalability and Fail
Fail-Over
Over Support – .NET Middle Tier

Server Assignment in Teamcenter J2EE Middle Tier
Client Tier WebTier Enterprise Tier
J2EE A
Application
li i S Server
Servlets Assign
EJBs Teamcenter
JSP Server Manager Server
Static Contents S
Server
Assigner Join
CORBA Teamcenter
Client
Request Server
Server Server
Assignment Assignment Login
Cache Cache
State Download
Teamcenter
Server
State
Replication
DBMS

Pool Configuration - Size (J2EE & .NET)
PROCESS_WARM – minimum number of unassigned servers

PROCESS_TARGET – desired number of servers
Syntax: <time> <target> [, <time> <target>]*
0000 5 – target=5, around the clock
0700 100
100, 1700 20 – target=100
target 100 from 7am to 5pm and 20 from 5pm to 7am
7am.
PROCESS_MAX – maximum number of servers
Unused Capacity
Unassigned Servers
Warm
Max Assigned
g Servers
Total
Servers
Target
Assigned

Pool Configuration – Timeouts (J2EE & .NET)
Timeout Types
Soft
S ft – Terminate
T i t idle
idl server when
h above
b ttargett tto gett b
back
k
down to target
Hard – Terminate idle server regardless of pool status
Panic – Terminate idle server when PROCESS_MAX
PROCESS MAX is
reached.
Query – Terminate active runaway server Statefulness
Modes

Server Management Example (J2EE & .NET)
Max
Target
PROCESS_
WARM Unused Capacity
Unassigned Servers
Assigned Servers

Deployment for Teamcenter J2EE Middle Tier
(Basic)
Client Tier Web Tier Enterprise Tier
Server Pool A
J2EE
Client
F Application
Server Teamcenter
I Server
R Teamcenter
Server
Shared
Client E Servlets
EJBs Assignment
Cache Server
JSP
W Mgr Teamcenter
Static Contents Server
A
Teamcenter
Client L Server

Deployment for Teamcenter J2EE Middle Tier (Clustering)
Client Tier Web Tier Enterprise Tier

J2EE Server Pool A
Application T
Teamcentert
Server Cluster Server
F Server 1
Teamcenter
Server
Client
Client I Servlets EJBs JSP
Static Contents Teamcenter
Server
R Serv
Teamcenter
er
E HTTP
Server 2
Servlets EJBs JSP Shared
Mgr Server
Static Contents
W Web Assignment
Client
Server C h
Cache
A Server 3 Server Pool B

Servlets EJBs JSP Teamcenter
L Static Contents Serv
er
Server
Client
Client L Mgr Teamcenter
Server
Server 4 Teamcenter
Servlets EJBs JSP Server
Static Contents
Teamcenter
Server

Deployment for Teamcenter J2EE Middle Tier
(Clustering with Load Balancer)
Client Tier DMZ Web Tier Enterprise Tier

J2EE Server Pool A
Application T
Teamcentert
Server Cluster Server
Client L Teamcenter
Client
Client O Server 1 Server
F A HTTP
Web
F Servlets EJBs JSP
Static Contents Teamcenter
I D Server I Serv
Server
R R Server 2 er
Mgr
Teamcenter
Server
Client Servlets EJBs JSP
Client E B HTTP E Static Contents
Shared
Assignment
Client Web
WA Server W C h
Cache
A L A Server 3 Server Pool B

Servlets EJBs JSP Teamcenter
Client
L A HTTP L Static Contents Serv Server
Client
Client
L N Web
Server L er
Mgr Teamcenter
Server
C Server 4 Teamcenter
Servlets EJBs JSP Server
E Static Contents
Teamcenter
R Server

Business Logic and App Server Failover
Business Logic
Server1
App
Server 1
DBMS
App
pp Server
Cluster
Client App
Server 2
Business Logic
Server2

Business Logic
Server1
App
Server 1
DBMS
App
pp Server
Cluster
Client App
Server 2
Business Logic
Server2

(Terminate App Server 1)
Business Logic
Server1
App
Server 1
DBMS
App
pp
Server
Cluster
Client App
Server 2
Business Logic
Server2

(Terminate Business Server 1)
Business Logic
Server1
App
Server 1
DBMS
App
pp
Server
Cluster
Client App
Server 2
Business Logic
Server2

(Restart Server 1’s)
1 s)
Business Logic
Server1
App
Server 1
DBMS
App
pp
Server
Cluster
Client App
Server 2
Business Logic
Server2

(Terminate Server 2’s
2 s i.e. double failover)
Business Logic
Server1
App
Server 1
DBMS
App
pp
Server
Cluster
Client App
Server 2
Business Logic
Server2

WAN Performance 2-Tier
2 Tier vs. 4-Tier
4 Tier
2-Tier Client 4 Ti Client

4-Tier Cli t
Response
Business Logic Server Compression and Streaming
Coarse Grained
SOA Calls
High Latency/Low
Bandwidth ((WAN))
WebTier
LAN
E t
Enterprise
i TiTier
Low level Resource Tier access
Resource Tier (DBMS)

Deployment on 4 physical tiers
Client File Caches
Rich Java Client, Web client, CAD clients,
CLIENT TIER
Office clients, FMS Client Cache
J2EE Web Server + Web Container +

Application Server OR Microsoft Windows WEB TIER
Server 2003 with .Net
File Cache Servers
ENTERPRISE TIER
Teamcenter Business Logic Server Pools
Relational Database Management System RESOURCE TIER RESOURCE TIER

(Oracle or SQLServer) (DB) (Filestore)
ADVANTAGE: Great deployment flexibility,

flexibility
security BUT
The hardware for each tier can be configured Most complex to manage
independently to suit the processing load
Multiple machines can be used at each tier for THEREFORE
scalability and failure tolerance Most suitable for large scale deployments
Clients can operate across wide area networks where flexibility is the key consideration
and through firewalls
Deployment on 3 physical tiers
Client File Caches
Rich Java Client, Web client, CAD clients,
CLIENT TIER
Office clients, FMS Client Cache
J2EE Web Server + Web Container +

Application Server OR Microsoft Windows
COMBINED
Server 2003 with .Net,
Net WEB AND File Cache Servers
Teamcenter Business Logic Server Pools ENTERPRISE TIER
Relational Database Management

g System
y
(Oracle or SQLServer)
RESOURCE TIER RESOURCE TIER
(DB) (Filestore)
ADVANTAGE: Balance of flexibility and
complexity
H d
Hardware ffor some tiers
ti can be
b independently
i d d tl BUT
configured to suit the processing load
Multiple machines can be used at each tier for Cannot separately configure web and
scalability and failure tolerance, adding and enterprise tier hardware platforms
removing at run time as necessary THEREFORE
Cli t can operate
Clients t across wide
id area networks
t k Most suitable for medium scale
and through firewalls deployments where a balance between
flexibility and complexity is desired
2-Tier
2 Tier and 4-Tier
4 Tier Together
Remote
4-tier clients: Facility
Can connect from remote locations 4-tier Client Desktop
Are optimised for performance
Client
across a wide area network File Cache
Support secure access through
firewalls
Support all Teamcenter clients and 4 tier Client Desktop
4-tier Data
ata
Center
most integrations
2-tier clients Web Server(s)
Are optimised for performance in a
local area network Distributed Cache
File Server(s)
Are not recommended for use Client
across wide area networks or File Cache
through firewalls Business Logic
Do not support the web client or Server(s)
stand-alone Teamcenter
Visualization
You can deploy both 4-tier and 2-tier for
the same database as shown on the right Client
File Cache Database
Master
Server
2-tier Client Desktop File Server(s)
2-Tier
2 Tier and 4-Tier
4 Tier Together – on one client
Remote
Facility
4-tier Client Desktop
You can deploy both 4-tier and 2-tier for
the same database as shown on the right Client
You can mix styles on one client! File Cache
In the LAN, a client can be both for

different purposes Data
ata
4 tier Client Desktop
4-tier
2-tier for Rich client and CAD Center
applications
4-tier for visualization and web Web Server(s)
client Distributed Cache
This is the only way to support File Server(s)
stand-alone Teamcenter Client
File Cache
Visualization and the Web Client
on one machine together with 2- Business Logic
Server(s)
tier CAD integration deployment
Must install Rich Client as either 2
or 4 tier – this cannot switch at run
time (but have both on 1 machine)
Client
File Cache Database
Master
Server
2/4-tier Client Desktop File Server(s)
Teamcenter deployed using the 4 tier architecture
is scalable
Horizontal scalability Client Desktop with

File Cache
Client Desktop with
Ability to add/remove servers at run- File Cache
Client Desktop with
time File Cache
Web Tier and Enterprise Tier are

independently scalable
Web Tier can be load balanced using
off the shelf solutions Load Balancer + Proxy (Option)
Web Tier handles load balancing
across Enterprise Tier servers
Vertical scalability Web/App

W b/A Server(s)
S ( )
Distributed Cache
Server machines at each tier can be File Server(s)
independently configured
Load on each Enterprise Tier machine
is managed and can be configured to
suit the machine’s capabilities Business Logic
Server(s)
Network between client and web tier
can have significant latency – up to
200ms for rich client
client, 400ms for web
client Master
Database File Server(s)
Server
Contact
Vikas Singh
Software Development Manager
E-mail: singh.vikas@siemens.com
www.siemens.com/plm

Thank You
Copyright © Siemens
Copyright
PLM©Software
SiemensInc.
AG 2008. All rights reserved.

Team Center Middle Tier Overview

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Team Center Middle Tier Overview

Hochgeladen von

Copyright:

Verfügbare Formate

Siemens PLM Connection

Teamcenter Middle Tier Overview

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Teamcenter Middle Tier Overview

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

DBMS File Stores

Teamcenter’s unified architecture: Client Tier

 Supports clients both on a local

 In addition to client and server processes in 2-tier, the 4-tier

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Client File Caches Technology

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Client Tier WebTier Enterprise Tier

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

PROCESS_WARM – minimum number of unassigned servers

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Client Tier Web Tier Enterprise Tier

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Client Tier Web Tier Enterprise Tier

A Server 3 Server Pool B

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Client Tier DMZ Web Tier Enterprise Tier

A L A Server 3 Server Pool B

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

2-Tier Client 4 Ti Client

Low level Resource Tier access

Resource Tier (DBMS)

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

J2EE Web Server + Web Container +

Relational Database Management System RESOURCE TIER RESOURCE TIER

ADVANTAGE: Great deployment flexibility,

J2EE Web Server + Web Container +

Relational Database Management

 In the LAN, a client can be both for

Horizontal scalability Client Desktop with

 Web Tier and Enterprise Tier are

Vertical scalability Web/App

Copyright © Siemens PLM Software Inc. 2008. All rights reserved.

Das könnte Ihnen auch gefallen

Supports clients both on a local

In addition to client and server processes in 2-tier, the 4-tier

In the LAN, a client can be both for

Web Tier and Enterprise Tier are