FMS Update

File Management System

Update

Page 2 May-09

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

Siemens PLM Software

Enterprise Knowledge Management

Page 3 May-09



Enterprise Knowledge Foundation

File Management System

Vision

FMS Overview

What’s New in Teamcenter 8

Copyright © Siemens AG 2008. All rights reserved.

Vision

Page 5 May-09



File Access and Delivery Drivers

File Sources are Geographically Distributed

Need to be managed where used

Users are Geographically Distributed

Corporate, partner, and supplier sites

Constrained LAN/WAN Bandwidth Resources

High latency, low bandwidth networks

Growing Volumes of Data

Larger file sizes of CAD, visualization, and simulation

High number of business files requiring management

Secure Data Access Requirements

Temporary persistence during access

No direct directory mounting and access

Page 6 May-09



File Management System Strategy

Requirement

Support globally distributed environments with high file access and

transfer performance and scalability of local and remote data access

Business Value

Teamcenter File Management Services delivers improved data access

and transfer performance across distributed global environments to

local and remote users

Page 7 May-09



`

FCC

Cache

`

FCC

Cache

`

FCC

Cache

FSC Vol

FSC Vol

FSC Vol

FSC Cache

LAN

LAN

WAN LAN

LAN

WAN

Teamcenter File Management System

Requirements

Enable Cache and File

Transfer Technologies

Provide High Speed LAN and

WAN File Access

Support Multiple Storage

Locations

Mitigate Single Point of

Failures using Redundancy

Distribute File Access with

Central Master Storage

Provide File Services for all

Teamcenter Modules

Page 8 May-09



FMS and Commercial Hardware Accelerators

FMS is designed to co-exist with commercial hardware acceleration

devices like Cisco WAAS and Riverbed technology

We expect most of the advantages of each technology are

preserved

For example, with FMS you should still gain the advantages of high

performance caching

Note that the optional WAN acceleration is not recommended when

using hardware accelerators

Anecdotal evidence from some customers are encouraging – both in

reliability and performance


Does not have access to detailed performance data

Does not currently have plans to certify specific brands or models


FMS Overview

Page 10 May-09



FMSTeamcenter Unified Architecture

Supplier & Partner

Applications

CAx

CRM

SRM

ERP

PDM

Office

Legacy

Resource Tier

Service Exposure

Database File Systems

J2EE .NET WSDL

Web Tier

PLM Private Services PLM Web Services

Enterprise

Application

Integration

Enterprise Tier

PLM UI Framework

PLM Business Logic

PLM Data Model

Product Process ResourcePlant

Business Modeler Extension Framework

Model Analysis

Web

Service

Integration

Client Tier

Thin Client Rich Client Visualization Tecnomatix CAx

SOA Framework PLM XML Framework

Requirement Schedule

Client

Application

Integration

Page 11 May-09



Teamcenter File Management System (FMS)

Data

Center

Master

File Server(s)

Distributed Cache

File Server(s)

Client

File Cache

Web Server(s)

Database

Server

Business Logic

Server(s)

Remote

Facility

Client

File Cache

Distributed Cache

File Server(s)

FMS benefits Enables centralized meta-data with

distributed files Makes heavy duty use cases such as

tight CAD integration usable by remote clients

Optimizes file download over Wide Area Networks

Provides configurable secure caching on clients and shared servers

Integrated with Teamcenter database access Critical component in Teamcenter

scalability Delivers files direct to the client desktop

after business logic has validated access rights

Page 12 May-09



Business Logic

File Server

DBMS File Store

Server

Cache

Teamcenter FMS Components

Web Tier

File Store

Rich Client

Browser Client

FMS Server

Cache

Client

Cache

Rich Client Cache – associated

with specific users on a

workstation, multiple user

caches supported, contains

whole and segmented files

Secondary Server Cache –

(optional) associated with

Primary Server Cache,

provides local access to remote

files, can provide aggregation

from multiple volume servers

Primary Server Cache –

associated with volume servers,

linked to secondary server caches

Local File

Server

FMS Volume Server –

associated with file

volumes

Page 13 May-09



File Management System Features

“Direct-to-Client” File Delivery

Separation of Functional and File Access Paths

FMS will always take the shortest route to read or write files

Secure File Streaming Between Server and Client Cache

The protocol used by FMS is TCP with HTTP headers. This allows it to

be recognised as HTTP by routers, proxy servers etc

Secure File Cache Access and Persistence

Optimized File Delivery

Parallel File Packet Transfer

Cache Server Best Routing and Chaining Capabilities

On-Demand or Pre-Population of Server Cache

No Direct Client Mounts

Multiple Client and Server Caches for optimized file uploads/downloads

Page 14 May-09



Introduced in Teamcenter 2007

FSC Configuration Reload

Don’t have to stop the FSC to reload configuration

FSC Pre-population

Batch capability to plan caching for specific files at specific FSCs

FSC Client Override

Capability to use the FSC that is for configuration download as the FSC

for actual file transfer

Volume Server failover

Capability to have multiple FSC mount a single volume

Client map with DNS name lookup

Alternative to IP based Client Maps

Includes better search in order of specific to least specific

FSC Internal Load Distribution

Capability to have equal priority (i.e. for assigned f sc)


What’s New in Teamcenter 8

Page 16 May-09



New in Teamcenter 8

Store and Forward

WAN File Compression

Multiple databases with a single FCC

Automatic and Manual FCC Reconfiguration

Page 17 May-09



FMS Store and Forward

Problem:

When saving files on a slow (high latency) network, the client pauses

waiting for the contents to upload

Solution:

Transfer the file and update the database as a background task

Benefits:

End user can return to productive work much more quickly

Page 18 May-09



Store and Forward Process

Transfer File

Change Volume

LocationTime: T + 480

Time: T + 180

Time: TFMS

Transfer

Request

WAN

Destination

Volume

(DestVol)

Initial

Volume

(SAFVol)

TCSERVER

File

2

File

FSC

`

Client

FSC

DB

fmstransfer

fmscleanup

Create

Dataset

3a

File

File

Delete File 4a

Scheduler

7 56

121110

8 4

21

9 3Event

Queue

Pull TransferGet File

1a

3b

3c

3d

1b

4b

Page 19 May-09



Store/Forward Details

Step 1 Import / Initial Check-in

File moves immediately to a local volume configured for specific group

or user

The Database is updated so the file is available to all end users at the

end of this step

Step 2 – Transfer Task

The a background task is scheduled with the Teamcenter Dispatcher

This step may be delayed through configuration

The task transfers the file to the normal User/Group Default Volume

Pull Solution

Streaming compression or WAN acceleration available

Can be configured to only transfers “latest” dataset Versions to

minimize unnecessary traffic

Task will “retry” automatically on failure

Step 3 – Cleanup

Empty local volume

Page 20 May-09



Store & Forward Data Flow

PLM

Client

LA N Desktop

PLM

Client

Embedded

xCAD Mgr

Web Server(s)

Database

Server

Business Logic

Server(s)

Embedded

xCAD Mgr

File

Client Cache

Main

Data

Center

File

Client Cache

Remote Desktop

DMZ 1

Web Server(s)

File

Server Cache

Store/Forward Volume

File Server(s)

TSTK

FMS Transfer Task

(3) Dataset List to Transfer(4) Transfer Tickets

(2) Request Object: Transfer Dataset

(1) Upload File

Page 21 May-09



Configuring Store and Forward

Define the default local volume using the Organization application

For information, see the Organization Guide

Enable store and forward functionality by setting the

TC_Store_and_Forward site preference to true

For more information, see the Preferences and Environment Variables

Reference

You can view the status of file transfers from the Request

Administration Console

For more information, see Getting Started with Dispatcher (Translation

Management)

Page 22 May-09



FMS WAN Compression

Problem:

Large file transfers consume too much bandwidth and time

Solution:

Compress file payload during transit

Benefit:

Saves both time and bandwidth

One Internal Test shows:

14x faster than default for text files; 2.5x for NX files

8x faster that WAN Acceleration for text files; 2x for NX files

Your mileage may vary

Page 23 May-09



Default (LAN) / Accelerated (WAN) / Compressed

File Transfer Comparisons

0

5

10

15

20

25

30

Lan Wan Compressed

Mb

/s

FMS Compression

Text File

NX Part File

All tests at same latency.

MB

/Se

c

Page 24 May-09



FMS WAN Compression – Notes

Appropriate for Web Client Downloads and Volume to Volume or

FSC to FSC whole file transfers

Not available for Rich or SOA clients

Configurable

Can coexist with optional WAN acceleration but will not be used in

combination

“Exclusion List” of file extensions to restrict to file types known to

compress well

Excluded file types will use WAN Acceleration if configured

Introduced at Teamcenter (Unified Architecture) 2007.1.3b

Page 25 May-09



Accessing Multiple Databases through a Single FCC

Problem:

It is difficult to use a single client installation with multiple server

installations (different Site IDs) because the FMS topologies are

different

Solution:

You can access files controlled by multiple Teamcenter databases

through a single FMS client cache (FCC) using one of two approaches

to interconnect the FMS networks

Page 26 May-09



Example1: Multiple FMS Networks

A part supplier with multiple customers, requiring access to each

customer’s PLM data, where the customers are in direct

competition with each other

The part supplier’s FCC loads configuration information from its local

fcc.xml file on startup. Its FCC also downloads configuration

information from the primary site. Using these two sources of

configuration information, the FCC determines from which customer

FMS server caches (FSCs) to request additional site data

Page 27 May-09



Example1: Multiple FMS Networks

LAN Site

Web Server

Business Logic

Server

Database

Server

Users

Web Server

Business Logic

Server

Database

Server

Web Server

Business Logic

Server

Database

Server

LAN Site LAN Site

Independent Databases

3 Independent FSC Connections

Client or Server Managed

Fcc.xml

Fmsmaster.xml

File Server File ServerFile Server

Page 28 May-09



Example2: Shared FMS Network

Example2: A single company with multiple databases. Users may

need data from any one of a number of remote distributed

databases at any time

A “master FSC” which controls configuration for FSCs at all sites

implements a Shared FMS Network

“Single” FMS_HOME

Page 29 May-09



Example2: Shared FMS Network

LAN Site

Web Server

Business Logic

Server

Database

Server

UsersUsers

Users

Web Server

Business Logic

Server

Database

Server

Web Server

Business Logic

Server

Database

Server

LAN Site LAN Site

FSCs Are Shared

Volumes Owned by Database

Rich Client Direct to Volume

To All Local DBs

Eliminates LAN Cache

Eliminates Multi-Site “Imports”

File Server

Page 30 May-09



Configuring Multiple Databases

Configure either your fmsmaster.xml files or fcc.xml files to support

multiple databases by including valid configuration elements

referencing at least one parent FSC that supports each of the other

databases to which the client may connect

For more information about configuration examples, see the System

Administration Guide

The proper multisite FCC client configuration must be present in

the FMS_HOME directory from which the FCC is started.

Siemens PLM Software recommends that you use a single

FMS_HOME environment variable setting to point to the combined

configuration

FSC servers for all databases must be online, properly configured, of

the proper version, and functional

Page 31 May-09



FCC Reconfiguration

Problem:

Central administrative changes to the master configuration file require

FCC shutdown and restart – not effective until the user session is

ended

Solution:

FMS client caches (FCCs) now detect changes to the master

configuration file on the fly

When you reconfigure the master configuration file, the changes are

propagated through all necessary FMS server caches (FSCs), both

masters and slaves

Running FCC processes detect the changes and attempt to reconfigure

themselves, without user interaction or interruption of the client

Some configuration changes still may require FCC shutdown

Client Caches can also be manually reconfigured if desired

Page 32 May-09



Related Sessions

What’s New in 4 Tier

Tuesday 10:15 – 10:55

Building Large Scale Teamcenter Systems

Wednesday 10:15 – 10:55

Deploying Teamcenter in a Secure Environment

Wednesday 4:30 – 5:15

Page 33 May-09



Related Material

Teamcenter System Administration Guide

Teamcenter Deployment Guide

Teamcenter 2007 Advanced Deployments White Paper

Contact for obtaining additional material

Louis Boydstun

[email protected]

Office – (513) 576-2628

Javeed Nizami, PhD

Manager

Teamcenter Development Design Office

[email protected]

Documents

FMS Update