Multi-Site Deployment Strategies

Matt Kelly Teamcenter Development Consulting

UGS Corp. 2007. All rights reserved.

Objective and Outline

Objective

To identify Teamcenter deployment options in support to implementations that span multiple sites.

Outline

Challenges of multiple sites Teamcenter deployment options Implementation strategies Expanding and consolidating sites Best practices Summary
UGS Corp. 2007. All rights reserved.

Teamcenter Engineering Global Deployment Intra-Company

Medium Latency Clients Low Latency Clients High Latency Network
Web Server Controlled Local File Server

Medium Latency Clients Low Latency Clients

Controlled Local File Server

Inter-Company
Low / Medium Latency Clients

Web Server

Controlled DMZ File Server

Medium Latency Clients Low Latency Clients

Business Logic Server

Database File Server Server

Almost any Latency Network

Business Logic Server

Lead Site
Web Server

Database File Server Server

Satellite Site
MultiMulti-Site connection Client / Server connection UGS Corp. 2007. All rights reserved.

Business Logic Server

Business Logic Server

Database Server

Database File Server Server

Supplier Site

Deployment Options
Based on business and user requirements

Identify the supporting Teamcenter functionality Define Teamcenter deployment architecture based on process and functional requirements

Examples

2-Tier RAC w/ CAD integration Multi-Site Design data sharing Supplier access by Web Client

Define hardware requirements to match target functionality

UGS Corp. 2007. All rights reserved.

Categorization Of Requirements
User Classes

Engineering Design, Manufacturing Management External Customer, Partner, Supplier

Business Process Support

Design data sharing Manufacturing build information, BOM etc. External data access for suppliers, vendors

Infrastructure

Hardware availability Intra-site connectivity User loads and hardware scalability Administration

UGS Corp. 2007. All rights reserved.

Infrastructure
Document target deployment environment

Hardware availability

Sizes, models, current usage Network connection details, loads, usage How many users per server, per site? Is admin support available at all sites? Is there an exiting hardware plan?

Connectivity LAN / WAN

Expected user support

Administration

Future Hardware plans

UGS Corp. 2007. All rights reserved.

Teamcenter 2005 Installations

Multi-tier install & configuration procedure involves multiple configuration elements:

Corporate Server Oracle Server Web Tier Rich Client(s)

Distribution Server

Optional Elements

Multi-Site Process Daemons Etc

UGS Corp. 2007. All rights reserved.

Implementation Strategies
Teamcenter 2005 supports several models

LAN Configuration

Typically a local LAN environment, campus, local WAN Often supported by 2-Tier RAC client deployment

Centralized WAN Configuration

Distributed clients with higher latency and distance profiles Typically supported by 4-Tier RAC, or Thin client deployment

Decentralized WAN Environment

Often autonomous sites with many users Typically supported by Multi-Site deployment

Combination

No functional restrictions to combining deployment models

UGS Corp. 2007. All rights reserved.

Teamcenter V9
Medium Latency CAD Clients Low Latency CAD Clients
Controlled Local File Server

Teamcenter V9

Medium Latency CAD Clients

Controlled Local File Server

Low Latency CAD Clients Medium Latency Network

Web Server

Web Server

Factors other than business needs drive use of Multi-Site to connect sites

Business Logic Server

Firewalls Security Network latency

Database File Server Server

Business Logic Server

Lead Site

Database File Server Server

Remote Site
MultiMulti-Site connection Client / Server connection
UGS Corp. 2007. All rights reserved.

2005 allows more flexibility

Teamcenter 2005
Teamcenter 2005 Onward

Medium Latency CAD Clients

Local FMS Cache Server

Medium Latency CAD Clients Low 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 Teamcenter Engineering 2005 allows all clients to use FMS caching Most clients HTTP and FMS enabled by Teamcenter Engineering 2005 SR1 Business Logic and SQL*Net can be enclosed in the Data Center Minimum ports to be opened in the firewall Less Teamcenter software on remote clients

Web Server

Medium Latency CAD Clients Medium Latency Network

Business Logic Server

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. 2. 3. 4. 5.

Semi-autonomous Installations Sites with high latency networks Sites with unreliable networks Supplier / OEM integration Secure projects (read corporate data, but do not share own data) On demand At Lifecycle steps Interval based Subscription Hub configuration (pull) (push) (push) (deferred push on change) (Store & forward; reduces point-to-point connections)

Data Synchronization

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 Within a federation, ODS may be configured either as a separate site, or part of an existing site

Business Logic Server

Database Server

Site 1
Web 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.

Site 2
Web Server

Business Logic Server

Business Logic Server

Database Server

File Server

Database Server

File Server

UGS Corp. 2007. All rights reserved.

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 Item: the basic unit of sharing. Includes meta-data and files.

Business Logic Server

Database Server

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.

Business Logic Server

Database Server

File Server

Site 1
UGS Corp. 2007. All rights reserved.

Site 2

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

Web Server

Export: To push a replica of a master item from the owning site to a remote site.
Import / Export

Web Server

Business Logic Server

Business Logic Server

Database Server

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

File Server

Site 2

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 Replica: A read-only copy of the master.

Business Logic Server

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.
Synchronize

Web Server

Business Logic Server

Replica Item

Database Server

File Server

Site 1
UGS Corp. 2007. All rights reserved.

Site 2

Multi-Site Concepts: Remote checkout

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

Replica Item

Database Server

File Server

Site 1
UGS Corp. 2007. All rights reserved.

Site 2

Multi-Site Configuration
Teamcenter Site Preferences control many elements of Multi-Site functionality including:

Publishing and transfer controls

Object types Sites Functional access by User, Role, Group etc. Default behavior

Restrictions Notification Pre / Post actions Data compression

UGS Corp. 2007. All rights reserved.

Import Options

Ownership transfer Rules for what item revisions and dataset versions to replicate Product structure options Miscellaneous options

Include / exclude Reporting Action on error

18
UGS Corp. 2007. All rights reserved.

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

All calculations are dependant on usage profile CPU

Calculation based on demand rate * concurrent users SPECint_rate2000 for HPux is 0.044 average 0.132 peak SiR for Windows / Solaris is 0.026 average 0.062 peak Demand = SiR * # concurrent users Each concurrent user requires:

Memory

34mb Windows / Solaris 54mb - HPux

Reserved Swap Space

Each concurrent user requires:

Web Tier Web Application Server

Web Application Server (Bea WebLogic)

46mb Windows /Solaris 84mb - HPux

UGS Corp. 2005. All rights reserved.

All calculations are dependant on usage profile CPU

Example:

SPECint_rate2000=39.7 test server w/ 1000 users test Consumed 2.0 SiR = .002 SiR/user

Memory

Resource Tier Teamcenter Database Server

Oracle Database Server

Basic memory requirement for WLS Server is 1.5gb Example

Small deployment <1000 users requires 0.2mb /user Large deployment <5000 users requires 0.46mb/user

CPU

Reserved Swap Space

Negligible swap size requirement

Calculation results in CPU class designation in SPECint_rate2000 industry standard. CPU = ((# concurrent users * .0025) * 1.2) RAM = (# concurrent users * 4.2Mb) Swap = (# concurrent users * 6 Mb)

Memory

UGS Corp. 2005. All rights reserved.

Reserved Swap Space (Unix)

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

LAN To Multi-Site

Multi-Site To Centralized

Plan for number of users Size based on

Define & document

Use cases Data sharing needs Synchronization strategy

Analyze current conditions

Published data Shared data Ownership

Users Deployment Arch Future

Deploy sites

Choose central site Aggregate data to central site Redeploy

Deploy & Configure

Enable M-S functionality

Servers Clients

Share data

Publish and share required, not more Automate whenever possible

Clients / Servers Support infrastructure

E.g. FMS

UGS Corp. 2007. All rights reserved.

Best Practices Deployment & Support Plans

The deployment plan should include

Supported user and business cases Hardware and infrastructure plan Administration requirements Implementation schedule

Coordinated with important milestones

Hardware upgrades / purchases 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

Define use cases and functional requirements first Identify intra-site infrastructure and connectivity capabilities Review administration capabilities and availability Select Teamcenter capability and release that best fits requirements and implementation environment

Simple is always better whenever possible Deployments can expand and contract as needed

UGS Corp. 2007. All rights reserved.

Thank you
www.ugs.com

UGS Corp. 2007. All rights reserved.