Multi-site.pdf
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Multi-site.pdf as PDF for free.
More details
- Words: 1,941
- Pages: 27
Multi-Site Deployment Strategies Matt Kelly Teamcenter Development Consulting
© UGS Corp. 2007. All rights reserved.
Objective and Outline f
Objective f
f
To identify Teamcenter deployment options in support to implementations that span multiple sites.
Outline f
Challenges of multiple sites
f
Teamcenter deployment options
f
Implementation strategies
f
Expanding and consolidating sites
f
Best practices
f
Summary © UGS Corp. 2007. All rights reserved.
Teamcenter Engineering Global Deployment Intra-Company Medium Latency Clients
Controlled Local File Server
Medium Latency Clients
Inter-Company
Controlled Local File Server
Low / Medium Latency Clients
Low Latency Clients
Low Latency Clients
Web Server
High Latency Network Web Server
Business Logic Server
Business Logic Server
Database File Server Server
Controlled DMZ File Server
Medium Latency Clients
Almost any Latency Network
Low Latency Clients
Lead Site Web Server
Database File Server Server
Satellite Site MultiMulti-Site connection Client ©/ Server UGS Corp.connection 2007. All rights reserved.
Business Logic Server
Database Server
Business Logic Server
Database File Server Server
Supplier Site
Deployment Options Based on business and user requirements f
Identify the supporting Teamcenter functionality
f
Define Teamcenter deployment architecture based on process and functional requirements f
f
Examples f
2-Tier RAC w/ CAD integration
f
Multi-Site Design data sharing
f
Supplier access by Web Client
Define hardware requirements to match target functionality
© UGS Corp. 2007. All rights reserved.
Categorization Of Requirements User Classes f
Engineering Design, Manufacturing
f
Management
f
External Customer, Partner, Supplier
Business Process Support f
Design data sharing
f
Manufacturing build information, BOM etc.
f
External data access for suppliers, vendors
Infrastructure f
Hardware availability
f
Intra-site connectivity
f
User loads and hardware scalability
f
Administration
© UGS Corp. 2007. All rights reserved.
Infrastructure Document target deployment environment f
Hardware availability f
f
Connectivity LAN / WAN f
f
How many users per server, per site?
Administration f
f
Network connection details, loads, usage
Expected user support f
f
Sizes, models, current usage
Is admin support available at all sites?
Future Hardware plans f
Is there an exiting hardware plan?
© UGS Corp. 2007. All rights reserved.
Teamcenter 2005 Installations Multi-tier install & configuration procedure involves multiple configuration elements: f
Corporate Server
f
Oracle Server
f
Web Tier
f
Rich Client(s) f
f
Distribution Server
Optional Elements f
Multi-Site
f
Process Daemons
f
Etc…
© UGS Corp. 2007. All rights reserved.
Implementation Strategies Teamcenter 2005 supports several models f
f
f
f
LAN Configuration f
Typically a local LAN environment, campus, local WAN
f
Often supported by 2-Tier RAC client deployment
Centralized WAN Configuration f
Distributed clients with higher latency and distance profiles
f
Typically supported by 4-Tier RAC, or Thin client deployment
Decentralized WAN Environment f
Often autonomous sites with many users
f
Typically supported by Multi-Site deployment
Combination f
No functional restrictions to combining deployment models
© UGS Corp. 2007. All rights reserved.
Teamcenter V9 Medium Latency CAD Clients
Medium Latency CAD Clients
Controlled Local File Server
Controlled Local File Server
Teamcenter V9 f
Low Latency CAD Clients
Web Server
Low Latency CAD Clients Medium Latency Network Web Server
Business Logic Server
Database File Server Server
Remote Site MultiMulti-Site connection Client / Server connection © UGS Corp. 2007. All rights reserved.
Business Logic Server
Database File Server Server
Lead Site f
Factors other than business needs drive use of Multi-Site to connect sites f
Firewalls
f
Security
f
Network latency
2005 allows more flexibility
Teamcenter 2005 Teamcenter 2005 Onward
Medium Latency CAD Clients
Medium Latency CAD Clients Local FMS Cache Server
Teamcenter Engineering 2005 allows all clients to connect across HTTP(S) to a Web Server instead of direct to Oracle
f
Teamcenter Engineering 2005 allows all clients to use FMS caching
f
Most clients HTTP and FMS enabled by Teamcenter Engineering 2005 SR1
f
Business Logic and SQL*Net can be enclosed in the Data Center
f
Minimum ports to be opened in the firewall
f
Less Teamcenter software on remote clients
Local FMS Cache Server
Low Latency CAD Clients
Web Server
Medium Latency CAD Clients
f
Business Logic Server
Medium Latency Network
Database File Server Server
Lead Site MultiMulti-Site connection Client / Server connection © UGS Corp. 2007. All rights reserved.
Teamcenter Multi-Site Collaboration Coordination of 1.
Semi-autonomous Installations
2.
Sites with high latency networks
3.
Sites with unreliable networks
4.
Supplier / OEM integration
5.
Secure projects (read corporate data, but do not share own data)
Data Synchronization f
On demand
(pull)
f
At Lifecycle steps
(push)
f
Interval based
(push)
f
Subscription
(deferred push on change)
f
Hub configuration
(Store & forward; reduces point-to-point connections)
Supports connection across installations that are running different versions (e.g., 9.1 ÅÆ 2005) © UGS Corp. 2007. All rights reserved.
Multi-Site Concepts: Site, IDSM, and ODS Object Directory Server (ODS) contains publication records. This is a “card catalog” that knows where data is hosted, but does not have a copy of the data itself
ODS
Business Logic Server
Within a federation, ODS may be configured either as a separate site, or part of an existing site
Database Server
Site 1 Web Server
Business Logic Server
Database Server
File Server
Each Site manages its own meta-data and files. It may also contain meta-data and files replicated from other sites. Integrated Distributed Services Manager ( IDSM) processes that manage user requests to transfer and update objects between other sites. Each site will initiate IDSM processes as needed to service user requests.
© UGS Corp. 2007. All rights reserved.
Site 2 Web Server
Business Logic Server
Database Server
File Server
Multi-Site Concepts: Item, Master, Publish Publish: To make a master item visible to the Federation by creating a Publication Record on the ODS.
ODS
Business Logic Server
Item: the basic unit of sharing. Includes meta-data and files.
Database Server
1
Publish
Web Server
Web Server
Business Logic Server
Database Server
File Server
Master Item
Master Item: The authoritative source of an item. This item is writable by users at the owning site.
Site 1 © UGS Corp. 2007. All rights reserved.
Business Logic Server
Database Server
Site 2
File Server
Multi-Site Concepts: Import, Export, Site Ownership Site Ownership: Refers to the site that owns an item. The owning site has the Master Item and information about where its replicas exist.
ODS
Business Logic Server
Database Server
Export: To push a replica of a master item from the owning site to a remote site.
Web Server
Business Logic Server
Database Server
Web Server
Business Logic Server
Import / Export
File Server
Master Item
Site 1 © UGS Corp. 2007. All rights reserved.
Import: To pull a replica of a master item from the owning site to a remote site.
Replica Item
Database Server
Site 2
File Server
Multi-Site Concepts: Master, Replica, Synchronization Master: The authoritative source of an item. Keeps track of where its replicas are and when they were last synchronized.
ODS
Business Logic Server
Replica: A read-only copy of the master.
Database Server
Web Server
Business Logic Server
Database Server
File Server
Master Item
Synchronization: To update a replica to reflect changes made to the master. Synchronization may be initiated by a remote user, by a regular scheduled activity, and/or by publish-subscribe.
Site 1 © UGS Corp. 2007. All rights reserved.
Synchronize
Web Server
Business Logic Server
Replica Item
Database Server
Site 2
File Server
Multi-Site Concepts: Remote checkout f
Remote checkout: Getting write access to a replica item. Remote checkout can apply to individual datasets “contained” in an item. Performing a remote checkout locks corresponding data on the owning site.
ODS
Business Logic Server
Database Server
Remote checkout allows a remote site to gain write access to specific data without migrating entire item. Site ownership does not change.
Web Server
Web Server
Business Logic Server
Business Logic Server
Database Server
File Server
Master Item
Site 1 © UGS Corp. 2007. All rights reserved.
Replica Item
Database Server
Site 2
File Server
Multi-Site Configuration Teamcenter Site Preferences control many elements of Multi-Site functionality including: f
Publishing and transfer controls f
Object types
f
Sites
f
Functional access by User, Role, Group etc.
f
Default behavior
f
Restrictions
f
Notification
f
Pre / Post actions
f
Data compression
© UGS Corp. 2007. All rights reserved.
Import Options f
Ownership transfer
f
Rules for what item revisions and dataset versions to replicate
f
Product structure options
f
Miscellaneous options f
Include / exclude
f
Reporting
f
Action on error 18 © UGS Corp. 2007. All rights reserved.
UGS Confidential
Multi-Site Support Features
© UGS Corp. 2007. All rights reserved.
Teamcenter 2005 Deployment Architecture Options
© UGS Corp. 2007. All rights reserved.
Hardware Sizing Enterprise Tier Teamcenter Server Teamcenter Server f
All calculations are dependant on usage profile
f
CPU
f
f
Calculation based on demand rate * concurrent users
f
SPECint_rate2000 for HPux is 0.044 average 0.132 peak
f
SiR for Windows / Solaris is 0.026 average 0.062 peak
f
Demand = SiR * # concurrent users
Memory f
f
Each concurrent user requires: f
34mb – Windows / Solaris
f
54mb - HPux
Reserved Swap Space f
Each concurrent user requires: f
46mb – Windows /Solaris
f
84mb - HPux
© UGS Corp. 2005. All rights reserved.
Web Tier Web Application Server Web Application Server (Bea WebLogic) f
All calculations are dependant on usage profile
f
CPU f
f
f
Example: f
SPECint_rate2000=39.7 test server w/ 1000 users test
f
Consumed 2.0 SiR = .002 SiR/user
Memory f
Basic memory requirement for WLS Server is 1.5gb
f
Example f
Small deployment <1000 users requires 0.2mb /user
f
Large deployment <5000 users requires 0.46mb/user
Resource Tier Teamcenter Database Server Oracle Database Server f
Reserved Swap Space f
Negligible swap size requirement
CPU f
Calculation results in CPU class designation in SPECint_rate2000 industry standard.
f
CPU = ((# concurrent users * .0025) * 1.2)
f
Memory
f
Reserved Swap Space (Unix)
f
© UGS Corp. 2005. All rights reserved.
f
f
RAM = (# concurrent users * 4.2Mb) Swap = (# concurrent users * 6 Mb)
Additional disk storage will be required for Oracle product installation and database storage.
© UGS Corp. 2005. All rights reserved.
© UGS Corp. 2007. All rights reserved.
Expanding and Consolidating Sites LAN To Centralized f
f
f
Plan for number of users
LAN To Multi-Site f
Size based on f
Users
f
Deployment Arch
f
Future
f
Servers
f
Clients
f
f
Analyze current conditions
f
Use cases
f
Data sharing needs
f
Published data
f
Synchronization strategy
f
Shared data
f
Ownership
Deploy sites f
Deploy & Configure f
Define & document
Multi-Site To Centralized
Enable M-S functionality
f
Choose central site
f
Aggregate data to central site
f
Redeploy
Share data f
f
Publish and share required, not more Automate whenever possible
f
Clients / Servers
f
Support infrastructure f
© UGS Corp. 2007. All rights reserved.
E.g. FMS
Best Practices Deployment & Support Plans The deployment plan should include f
Supported user and business cases
f
Hardware and infrastructure plan
f
Administration requirements
f
Implementation schedule f
f
Coordinated with important milestones f
Hardware upgrades / purchases
f
Software release dates
Test / acceptance plan
© UGS Corp. 2007. All rights reserved.
Supporting Documentation
© UGS Corp. 2007. All rights reserved.
GTAC Product Documentation http://support.ugs.com/docs/tc_eng/2005SR1/
© UGS Corp. 2007. All rights reserved.
Summary Things to remember f
Define use cases and functional requirements first
f
Identify intra-site infrastructure and connectivity capabilities
f
Review administration capabilities and availability
f
Select Teamcenter capability and release that best fits requirements and implementation environment f
Simple is always better whenever possible
f
Deployments can expand and contract as needed
© UGS Corp. 2007. All rights reserved.
Thank you www.ugs.com
© UGS Corp. 2007. All rights reserved.
© UGS Corp. 2007. All rights reserved.
Objective and Outline f
Objective f
f
To identify Teamcenter deployment options in support to implementations that span multiple sites.
Outline f
Challenges of multiple sites
f
Teamcenter deployment options
f
Implementation strategies
f
Expanding and consolidating sites
f
Best practices
f
Summary © UGS Corp. 2007. All rights reserved.
Teamcenter Engineering Global Deployment Intra-Company Medium Latency Clients
Controlled Local File Server
Medium Latency Clients
Inter-Company
Controlled Local File Server
Low / Medium Latency Clients
Low Latency Clients
Low Latency Clients
Web Server
High Latency Network Web Server
Business Logic Server
Business Logic Server
Database File Server Server
Controlled DMZ File Server
Medium Latency Clients
Almost any Latency Network
Low Latency Clients
Lead Site Web Server
Database File Server Server
Satellite Site MultiMulti-Site connection Client ©/ Server UGS Corp.connection 2007. All rights reserved.
Business Logic Server
Database Server
Business Logic Server
Database File Server Server
Supplier Site
Deployment Options Based on business and user requirements f
Identify the supporting Teamcenter functionality
f
Define Teamcenter deployment architecture based on process and functional requirements f
f
Examples f
2-Tier RAC w/ CAD integration
f
Multi-Site Design data sharing
f
Supplier access by Web Client
Define hardware requirements to match target functionality
© UGS Corp. 2007. All rights reserved.
Categorization Of Requirements User Classes f
Engineering Design, Manufacturing
f
Management
f
External Customer, Partner, Supplier
Business Process Support f
Design data sharing
f
Manufacturing build information, BOM etc.
f
External data access for suppliers, vendors
Infrastructure f
Hardware availability
f
Intra-site connectivity
f
User loads and hardware scalability
f
Administration
© UGS Corp. 2007. All rights reserved.
Infrastructure Document target deployment environment f
Hardware availability f
f
Connectivity LAN / WAN f
f
How many users per server, per site?
Administration f
f
Network connection details, loads, usage
Expected user support f
f
Sizes, models, current usage
Is admin support available at all sites?
Future Hardware plans f
Is there an exiting hardware plan?
© UGS Corp. 2007. All rights reserved.
Teamcenter 2005 Installations Multi-tier install & configuration procedure involves multiple configuration elements: f
Corporate Server
f
Oracle Server
f
Web Tier
f
Rich Client(s) f
f
Distribution Server
Optional Elements f
Multi-Site
f
Process Daemons
f
Etc…
© UGS Corp. 2007. All rights reserved.
Implementation Strategies Teamcenter 2005 supports several models f
f
f
f
LAN Configuration f
Typically a local LAN environment, campus, local WAN
f
Often supported by 2-Tier RAC client deployment
Centralized WAN Configuration f
Distributed clients with higher latency and distance profiles
f
Typically supported by 4-Tier RAC, or Thin client deployment
Decentralized WAN Environment f
Often autonomous sites with many users
f
Typically supported by Multi-Site deployment
Combination f
No functional restrictions to combining deployment models
© UGS Corp. 2007. All rights reserved.
Teamcenter V9 Medium Latency CAD Clients
Medium Latency CAD Clients
Controlled Local File Server
Controlled Local File Server
Teamcenter V9 f
Low Latency CAD Clients
Web Server
Low Latency CAD Clients Medium Latency Network Web Server
Business Logic Server
Database File Server Server
Remote Site MultiMulti-Site connection Client / Server connection © UGS Corp. 2007. All rights reserved.
Business Logic Server
Database File Server Server
Lead Site f
Factors other than business needs drive use of Multi-Site to connect sites f
Firewalls
f
Security
f
Network latency
2005 allows more flexibility
Teamcenter 2005 Teamcenter 2005 Onward
Medium Latency CAD Clients
Medium Latency CAD Clients Local FMS Cache Server
Teamcenter Engineering 2005 allows all clients to connect across HTTP(S) to a Web Server instead of direct to Oracle
f
Teamcenter Engineering 2005 allows all clients to use FMS caching
f
Most clients HTTP and FMS enabled by Teamcenter Engineering 2005 SR1
f
Business Logic and SQL*Net can be enclosed in the Data Center
f
Minimum ports to be opened in the firewall
f
Less Teamcenter software on remote clients
Local FMS Cache Server
Low Latency CAD Clients
Web Server
Medium Latency CAD Clients
f
Business Logic Server
Medium Latency Network
Database File Server Server
Lead Site MultiMulti-Site connection Client / Server connection © UGS Corp. 2007. All rights reserved.
Teamcenter Multi-Site Collaboration Coordination of 1.
Semi-autonomous Installations
2.
Sites with high latency networks
3.
Sites with unreliable networks
4.
Supplier / OEM integration
5.
Secure projects (read corporate data, but do not share own data)
Data Synchronization f
On demand
(pull)
f
At Lifecycle steps
(push)
f
Interval based
(push)
f
Subscription
(deferred push on change)
f
Hub configuration
(Store & forward; reduces point-to-point connections)
Supports connection across installations that are running different versions (e.g., 9.1 ÅÆ 2005) © UGS Corp. 2007. All rights reserved.
Multi-Site Concepts: Site, IDSM, and ODS Object Directory Server (ODS) contains publication records. This is a “card catalog” that knows where data is hosted, but does not have a copy of the data itself
ODS
Business Logic Server
Within a federation, ODS may be configured either as a separate site, or part of an existing site
Database Server
Site 1 Web Server
Business Logic Server
Database Server
File Server
Each Site manages its own meta-data and files. It may also contain meta-data and files replicated from other sites. Integrated Distributed Services Manager ( IDSM) processes that manage user requests to transfer and update objects between other sites. Each site will initiate IDSM processes as needed to service user requests.
© UGS Corp. 2007. All rights reserved.
Site 2 Web Server
Business Logic Server
Database Server
File Server
Multi-Site Concepts: Item, Master, Publish Publish: To make a master item visible to the Federation by creating a Publication Record on the ODS.
ODS
Business Logic Server
Item: the basic unit of sharing. Includes meta-data and files.
Database Server
1
Publish
Web Server
Web Server
Business Logic Server
Database Server
File Server
Master Item
Master Item: The authoritative source of an item. This item is writable by users at the owning site.
Site 1 © UGS Corp. 2007. All rights reserved.
Business Logic Server
Database Server
Site 2
File Server
Multi-Site Concepts: Import, Export, Site Ownership Site Ownership: Refers to the site that owns an item. The owning site has the Master Item and information about where its replicas exist.
ODS
Business Logic Server
Database Server
Export: To push a replica of a master item from the owning site to a remote site.
Web Server
Business Logic Server
Database Server
Web Server
Business Logic Server
Import / Export
File Server
Master Item
Site 1 © UGS Corp. 2007. All rights reserved.
Import: To pull a replica of a master item from the owning site to a remote site.
Replica Item
Database Server
Site 2
File Server
Multi-Site Concepts: Master, Replica, Synchronization Master: The authoritative source of an item. Keeps track of where its replicas are and when they were last synchronized.
ODS
Business Logic Server
Replica: A read-only copy of the master.
Database Server
Web Server
Business Logic Server
Database Server
File Server
Master Item
Synchronization: To update a replica to reflect changes made to the master. Synchronization may be initiated by a remote user, by a regular scheduled activity, and/or by publish-subscribe.
Site 1 © UGS Corp. 2007. All rights reserved.
Synchronize
Web Server
Business Logic Server
Replica Item
Database Server
Site 2
File Server
Multi-Site Concepts: Remote checkout f
Remote checkout: Getting write access to a replica item. Remote checkout can apply to individual datasets “contained” in an item. Performing a remote checkout locks corresponding data on the owning site.
ODS
Business Logic Server
Database Server
Remote checkout allows a remote site to gain write access to specific data without migrating entire item. Site ownership does not change.
Web Server
Web Server
Business Logic Server
Business Logic Server
Database Server
File Server
Master Item
Site 1 © UGS Corp. 2007. All rights reserved.
Replica Item
Database Server
Site 2
File Server
Multi-Site Configuration Teamcenter Site Preferences control many elements of Multi-Site functionality including: f
Publishing and transfer controls f
Object types
f
Sites
f
Functional access by User, Role, Group etc.
f
Default behavior
f
Restrictions
f
Notification
f
Pre / Post actions
f
Data compression
© UGS Corp. 2007. All rights reserved.
Import Options f
Ownership transfer
f
Rules for what item revisions and dataset versions to replicate
f
Product structure options
f
Miscellaneous options f
Include / exclude
f
Reporting
f
Action on error 18 © UGS Corp. 2007. All rights reserved.
UGS Confidential
Multi-Site Support Features
© UGS Corp. 2007. All rights reserved.
Teamcenter 2005 Deployment Architecture Options
© UGS Corp. 2007. All rights reserved.
Hardware Sizing Enterprise Tier Teamcenter Server Teamcenter Server f
All calculations are dependant on usage profile
f
CPU
f
f
Calculation based on demand rate * concurrent users
f
SPECint_rate2000 for HPux is 0.044 average 0.132 peak
f
SiR for Windows / Solaris is 0.026 average 0.062 peak
f
Demand = SiR * # concurrent users
Memory f
f
Each concurrent user requires: f
34mb – Windows / Solaris
f
54mb - HPux
Reserved Swap Space f
Each concurrent user requires: f
46mb – Windows /Solaris
f
84mb - HPux
© UGS Corp. 2005. All rights reserved.
Web Tier Web Application Server Web Application Server (Bea WebLogic) f
All calculations are dependant on usage profile
f
CPU f
f
f
Example: f
SPECint_rate2000=39.7 test server w/ 1000 users test
f
Consumed 2.0 SiR = .002 SiR/user
Memory f
Basic memory requirement for WLS Server is 1.5gb
f
Example f
Small deployment <1000 users requires 0.2mb /user
f
Large deployment <5000 users requires 0.46mb/user
Resource Tier Teamcenter Database Server Oracle Database Server f
Reserved Swap Space f
Negligible swap size requirement
CPU f
Calculation results in CPU class designation in SPECint_rate2000 industry standard.
f
CPU = ((# concurrent users * .0025) * 1.2)
f
Memory
f
Reserved Swap Space (Unix)
f
© UGS Corp. 2005. All rights reserved.
f
f
RAM = (# concurrent users * 4.2Mb) Swap = (# concurrent users * 6 Mb)
Additional disk storage will be required for Oracle product installation and database storage.
© UGS Corp. 2005. All rights reserved.
© UGS Corp. 2007. All rights reserved.
Expanding and Consolidating Sites LAN To Centralized f
f
f
Plan for number of users
LAN To Multi-Site f
Size based on f
Users
f
Deployment Arch
f
Future
f
Servers
f
Clients
f
f
Analyze current conditions
f
Use cases
f
Data sharing needs
f
Published data
f
Synchronization strategy
f
Shared data
f
Ownership
Deploy sites f
Deploy & Configure f
Define & document
Multi-Site To Centralized
Enable M-S functionality
f
Choose central site
f
Aggregate data to central site
f
Redeploy
Share data f
f
Publish and share required, not more Automate whenever possible
f
Clients / Servers
f
Support infrastructure f
© UGS Corp. 2007. All rights reserved.
E.g. FMS
Best Practices Deployment & Support Plans The deployment plan should include f
Supported user and business cases
f
Hardware and infrastructure plan
f
Administration requirements
f
Implementation schedule f
f
Coordinated with important milestones f
Hardware upgrades / purchases
f
Software release dates
Test / acceptance plan
© UGS Corp. 2007. All rights reserved.
Supporting Documentation
© UGS Corp. 2007. All rights reserved.
GTAC Product Documentation http://support.ugs.com/docs/tc_eng/2005SR1/
© UGS Corp. 2007. All rights reserved.
Summary Things to remember f
Define use cases and functional requirements first
f
Identify intra-site infrastructure and connectivity capabilities
f
Review administration capabilities and availability
f
Select Teamcenter capability and release that best fits requirements and implementation environment f
Simple is always better whenever possible
f
Deployments can expand and contract as needed
© UGS Corp. 2007. All rights reserved.
Thank you www.ugs.com
© UGS Corp. 2007. All rights reserved.
More Documents from "Raju Puttaswamy"
170_help Points List.pdf
October 2019 6
Hypermesh Analysis
October 2019 12
Multi-site.pdf
October 2019 6
Lane Dane
November 2019 41