les avantages de l'architecture v6 de ds evolutivité ... · pdf fileles avantages...

Product Lifecycle Management Solutions

© 2009 IBM Corporation

IBM SWG IBM SWG –– Product Lifecycle ManagementProduct Lifecycle Management






Les avantages de l'architecture V6 de DS Les avantages de l'architecture V6 de DS

Evolutivité, flexibilité, sécurité

Sabine Prudhomme


© 2009 IBM Corporation2




V6 Architecture Introduction

Multi-Site and Content Synchronization

Web Conferencing and Global Collaboration

Internet Security and Remote Access

1

2

4

3

Agenda








1

2

4

3



Agenda






ENOVIA V6 Architecture Value Proposition

� Improve operational efficiency�New architecture for centralized data center�“Single source of truth”�Modularized open architecture

• Accelerate time to market

�Secure global collaboration�Integrated design chain�End-to-end product lifecycle management

• Decrease costs

�Horizontal scalability�Future-proof growth�Centralized administration






V6 Multi-Tier Architecture Principle

Database Server: Metadata RepositoryDatabase Server: Metadata Repository

File Server(s) (FCS)Representation and Content

Repository

File Server(s) (FCS)Representation and Content

Repository

HTTP

ClientsClients

Applications Server(s) (MCS)Applications Server(s) (MCS)

AAAA

Workstation ClientsEx.: CATIA V6, DELMIA V6, SIMULIA V6, xCAD…

Web ClientsEx.: ENOVIA business process

applications

Light Visualization ClientsEx.: ENOVIA 3DLive

(*) Optional.

Dat

aLo

gic

Pre

sent

atio

n

SSSSDDDD

FFFFIndex Servers *Indexing Repository

Index Servers *Indexing Repository






CATIA V63DLIVE.. V6

SIMULIA V6

DELMIA V6

HTTP

CATIA V5

xCAD

V6 GovernanceApplications

D A

F

Multi-Client Topology

A1

A2

A1 change image to V5 imageAuteur; 25/02/2009

A2 add Delmia image hereAuteur; 25/02/2009






• Reduces Total Cost of Ownership (TCO)

• Reduces Efforts to Create and Propagate Customizati ons & Upgrades

• Optimized for WAN access for remote users

A: ENOVIA Application Server (MCS)D: Database Server (DB)

F: ENOVIA File Server (FCS )

One Location

D A

F

V6 Centralized Database Architecture






Master Collaboration Server (MCS)- Business Logic and Web Access

File Collaboration Server (FCS)- Content and Stream Storage Data

Database Server (DB)- Metadata Storage Data

Advanced Search Server (IDOL)- Accelerated Retrieval of Textual Data

Conferencing Server (CNF)- Real-Time Lifelike Collaboration

3D Indexing Server (3D INDEX)- Accelerated Retrieval of 3D Data

Required

Optional

Advantages:• Single Database for “one source of

truth” isolated from direct user

interaction• Cost-reduction

via enablement of component architecture

• Modular architecture designed for future growth

Advantages:• Single Database for “one source of

truth” isolated from direct user

interaction• Cost-reduction

via enablement of component architecture

• Modular architecture designed for future growth

Note: Initials (MCS, CNF, etc) will be used as sho rt names on the following slides.

…

V6 IT Infrastructure ComponentsV6 IT Infrastructure Components






Other Servers and Equipment

� Batch, queue manager, or grid controller for background jobs

� DSLS (OEM of LUM V5) Licensing servers

� Report server for Crystal Reports for data mining in PLM database

� Others depending on optional offerings such as ERP integration

� SSL VPN Server for certificate management and authentication of users coming in from the internet over a VPN

� Reverse-Proxy Server for protecting the identity of the servers in the data center

� Storage bay for all content (indexes, database, and content) with backup and restore procedures

� Load-balancers for clustering servers






Index ServersFile ServerDatabase Server

Indexes

PLM Metadata for objects and relationships as well a s business logic

PLM Content including 3D representations, streams, of fice documents, etc. Note: No more file-based access!

PLM Indexes to accelerate access to data and geometry

MetadataContent

3D Rep

3D Stream

PLM1.doc

3D IndexPLM Object A.1

PLM Object A.2

PLM Object B.1

PLM2.pdf

Indexes

AdvancedSearchIndex

V6 Data Types






MCS

DB

FCS

CATIA/DELMIA/SIMULIA V6

Client-MCShttp/s protocol

3DLIVENavigator

Client-FCShttp/s protocol

Governance

3D INDEX

Client-3D Index Runtimehttp/s protocol

Client-3D Index Buildtimehttp protocol

IDOL

Client-IDOL Runtimehttp/s protocol

Client-IDOL Buildtimehttp/s protocol

Client-DBProprietary protocol

Logical Architecture for V6






MCS

DB

FCS


3DLIVENavigator


Governance CATIA V5/ Designer Central

IDOL

Client-IDOLhttp/s protocol


Logical Architecture for V6 /CATIA V5






3DCOM

VPM V4Client-MCShttp/s protocol



Client-3D Index Buildtime

http protocol

Client-IDOL Runtimehttp/s protocolClient-IDOL Buildtime

http/s protocol


CATIA V5

FCSMCS

DB

3D INDEX


IDOL

3DLIVENavigator

Governance

Client-VPMCORBA protocol VPM V4

VAULT

Logical Architecture for Co-existence V6/VPM V4






SmarTeam Editor




Client-3D Index Buildtime

http protocol

Client-IDOL Runtimehttp/s protocolClient-IDOL Buildtime

http/s protocol


Vault Server FCSMCS

DB

3D INDEX


IDOL

3DLIVENavigator Governance

Client-VPMCORBA protocol

Logical Architecture for Co-existence V6/SMARTEAM V5

SmarTeam Server






DB ServerDB ServerDB Server

MCS + FCS+DB+NDX

Demo

MCS + FCS+DB Client

+NDX

Sandbox /Training ProofofConcept

MCS+DB Client

FCS Server

ProductionPrototype

IDOL Server MCS+DB Client

FCS Server

3D Index Server

Conferencing Server

From demo environment to full-scale production prototyp e

ENOVIA V6 Flexibility






DB

DBServer

MCS FCS Server

MCS

MCS

MCS Load Balanced Cluster on LAN

FCS Server

Load-balancer

Load-balancer

Note that load balancer can either be in software or hardware and configured based

on load or IP address as appropriate

3D Index Server

Conferencing Server

IDOL Server

Load-balancer

3D Index Server

ENOVIA V6 Flexibility

A3

A3 comment outAuteur; 16/01/2009






Load balancing:Ability to dispatch load on different Application s ervers or File servers

Fail Over:In case of failure of an application server:o Subsequent transactions is dispatched on another ap plication servero No loss of service time for users connected to runn ing machine

http

Load Balancer• Hardware• Software

Phase 2

http

http

Phase 2

Phase 2

http

http

Load balancing and fail-over for MCS and FCS

A4

A4 add server namesAuteur; 16/01/2009






…………

…………

HTTP ServerHTTP Server

…

Horizontal Clustering

In-box Clustering

Web

App

S

erve

rW

eb A

pp

Ser

ver

Note: no direct 1:1 linear correlation between number of

users and number of DB connections

EN

OV

IA J

ava

Pro

cess

EN

OV

IA J

ava

Pro

cess

Web

App

S

erve

rW

eb A

pp

Ser

ver

Web

App

S

erve

rW

eb A

pp

Ser

ver

EN

OV

IA J

ava

Pro

cess

EN

OV

IA J

ava

Pro

cess

EN

OV

IA J

ava

Pro

cess

EN

OV

IA J

ava

Pro

cess

Zoom inside MCS for ScalibilityZoom inside MCS for Scalibility








1

2

4

3



Agenda






A: ENOVIA Application Server (MCS)D: Database Server (DB)F: ENOVIA File Server (FCS) FFFF

FFFF

FFFF

• Optimizes Performance by Eliminating Interactive Fi le Transfers Across WAN by Storing Content Closer to the Remote Users on File Collabor ation Servers (FCS)

• File transfer done via Synchonization Jobs

D A

F

V6 Centralized Architecture with Distributed Stores






� File storage management is based on ENOVIA Live Collaboration Server mechanisms

� The different concepts are:– STORE : MCS metadata stored in the database describing :

• The physical LOCATION of the various files• The association of users with their sites

– LOCATION = physical location of the data. On an FCS, it is the path to the file system where the files/streams are stored.

– SITE = geographical location of a user or group of users. LOCATION can be dedicated to SITE

– FCS = File server for the master site and/or the remote sites

� All of these are described by metadata stored in the database

� A user is assigned to one SITE

� A STORE can have several LOCATIONs

� A SITE can have several LOCATIONs

� For any particular unique version of content, there is one unique mapping of USER � SITE � STORE � LOCATION and this mapping is stored in the database

File storage concepts






Step1 . file1 ( ) on LOCATION1

Step2 . User on LOCATION3 requests file1

Step3 . The system synchronizes file1 on LOCATION3

FCS

MCS

File information about

LOCATION is saved in DB

Step1:

file1 on LOCATION1

Step3:

file1 on LOCATION1

file1 on LOCATION3

FCS

SITE 1

LOCATION1

FCS

SITE 2

LOCATION2

FCS

LOCATION3

SITE 3

Default Behavior

Optional Behavior

Synchronizations on demand






SITE 2

Synchronization commands in Interactive•MQL: “Sync store plmx from location LOCATIONx to store;”

•MQL: “Sync store plmx from location LOCATION1 to LOCATION3;”

and Schedule modes•every n minutes

•everydayat 6:00pm

•every 200 Mo to synchronize

MASTER

FCS

DB

FCS

SITE 1

LOCATION1

FCS

LOCATION2

FCS

LOCATION3

SITE 3

MCS

Default Behavior

Optional Behavior

Synchronizations by command








1

2

4

3



Agenda






Security Technology

Common Authentication & Administration

X509 Certificates for Identity Management

Authentication Shared by All Applications

Secure Socket Layer Packet Transport

Secure HTTP Web Transport over SSL

• Security rules easily modeled with PLM Modeling Studio functionality

• All data events stored in object history records

• All system access stored in log files

LDAPLDAPLDAPLDAP

Single Sign onSingle Sign onSingle Sign onSingle Sign on

SSLSSLSSLSSL

HTTPSHTTPSHTTPSHTTPS

DigitalDigitalDigitalDigitalCertificatesCertificatesCertificatesCertificates






� User authentication management– Option 1 - Default mechanism

• User information (authentication & ACL data) are defined in the P&O tables in database

– Option 2 - Users externalization• User information is stored in an LDAP directory and not in the P&O tables• The server performs the authentication through LDAP• P&O tables contain all ACL data

Phase 2Phase 2

http

http

http

third party

third party

P&O

Metadata

USERSUSERS

authentication

Information

1

LDAP

USERS

Authentication

Information

2

Collaboration Server

LDAP Directory Server

FCS

MCS RDBMS

Authentication






� Single Sign On– One unique login for all applications

• Governance: Plug-and-play into existing Single Sign-On infrastructure (such as Tivoli Identity Manager and SiteMinder)

• CATIA V6: On the client, CAA APIs manage SSO credentials: “User Exit”must retrieve and provide credentials to the server login

Phase 2Phase 2

http

third party

CAA client APIs to connect

to SSO mechanism

http

http

third party

third party

1

2

Single Sign-on Server

Collaboration Server LDAP Directory Server

FCS

MCS RDBMS

Authentication | Single Sign On

A5

A5 Need to check with Philippe GrilleresAuteur; 16/01/2009






Network securityFirewall management: Single port Access to V6 Serve rNAT and name translation

FirewallFirewall

OEM NetworkPublic Network

Firewall

DMZ

HTTP / SSL / IPSEC

Phase 2Phase 2

Phase 2Phase 2

Phase 2Phase 2

Phase 2Phase 2

VPN

Remote SiteNetwork

third party

1

2


FCS

MCS

RDBMS

Multi Site Private network infrastructure






Network securityFirewall management: Single port access to V6 Serve rNAT and name translationHTTPS is supported from client to reverse proxy

FirewallFirewall

OEM NetworkRemote SiteNetwork

Firewall

DMZ

ReverseProxyExisting

Proxy

HTTP / SSL / IPSEC

Phase 2Phase 2

Phase 2Phase 2

Phase 2Phase 2

Phase 2Phase 2

http /https

third party

third partythird party

Public Network

http /httpshttp /https

http /https

http /https

http


FCS

MCS

RDBMS

User on Public Internet

Multi Site Public network infrastructure






Local FCS

Firewall

Public Network

Proxy

http/https File synchronization

Phase 2Phase 2

third party

Remote SiteNetwork

Firewall

OEM Network

Firewall

DMZ

Phase 2Phase 2

Phase 2Phase 2

Phase 2Phase 2

third party

third party

ReverseProxy


FCS

MCS

RDBMS

http /https

Multi Site Data storage






V6 Architecture

Multi Site



1

2

4

3

Agenda






Collaboration modesClient-Server : One to One, One to Many, Many to Ma ny Peer to peer ( LAN Only V6 to V6 )

Supported Middleware IBM Lotus Domino, Lotus Sametime 7.5.1Microsoft Live Communication Server : OCS 2007

Middleware architecture for conferencing is deploye d as defined by IBM or Microsoft

V6 Instant collaborative capabilities:3DLive : Co-review

Chat + 3DSnapshot + Co-review

CATIA V6 : Co-Review et Co-designShare design in edit mode

Other capabilities supported :Audio, video (3 rd party-based only, based on Sametime or OCS2007)

On-Line Conferencing Environment

Functionalities






Firewall Firewall

Proxy

OEM NetworkSupplier / PartnerNetwork

Public Network

Firewall

DMZ

http protocol

sip protocol

(Session Initiation Protocol)

Other third party protocol

(video, audio)


third party

Reverse Proxy

Sametime Gateway

third party

FCS

MCS

Sametime Server

RDBMS

On-line Collaboration Environment

Centralized Conferencing Server– Lotus Sametime






Firewall Firewall

Proxy

OEM NetworkSupplier / PartnerNetwork

Public Network

Firewall

DMZ


third party

Sametime Gatewaythird party

Sametime Gateway

Reverse Proxy

third party

Collab ServerSametime

third party

DMZ

sip protocol

(Session Initiation Protocol)

Other third party protocol

(video, audio)

SametimeServer

RDBMS

FCS

MCS

On-line Collaboration Environment

Distributed Conferencing Servers – Lotus Sametime






DF

��

��

��

ENOVIA 3DLive CollaborationRemote Access (with FCS)

PLM Exchanges via V6 Briefcase SolutionCATIA V5 Partner delivering in a V6 Project

3DXML Publishing

��

��

��

��

��

��

LivecollaborationAsynchronous collaboration

D F

F

A

A: ENOVIA Application Server (MCS)D: Database Server

F: ENOVIA File Server (FCS)

F

A

V6 Architecture

Optimized for Extended Enterprise & Supplier Collaboration - Examples









04/03/09

IBM Dassault SystèmesInternational Competency Center

Top






04/03/09

� IBM / Dassault Systèmes International Competency Center

(IDSICC) is a team of IBM and Dassault Systèmes people

supporting customer related activities by delivering:

– Performance, Scalability and Capacity Planning tests

– Proof-of-concept for Advanced Solutions

– Installation, Tuning, Sizing guidelines for PLM Solutions

– Implementation & Methodology guidelines

– Technical whitepapers on architecture

� Founded in 1999 by IBM and Dassault Systèmes

Integration and Optimization of Technologies

Dynamic Infrastructure

provided by IBM hardware,

storage and middleware for

Product Innovation

Tests of Performance, Capacity and

Scalability

Unique Partnership

Technologic Partnership between IBM and Dassault Systèmes

Functionalities






04/03/09

Performance with optimized end-user response time

Capacity with large databases

Scalability with large number of users

The IDSICC test environment for ENOVIA V6 relies on IBM hardware and middleware. IBM Power System and

IBM BladeCenter servers with POWER6 CPU technology are used for the performance, capacity a nd scalability “PCS” tests. IBM System Storage platform s

(DS4800, DS5000 & N5500) complement the IBM System Servers to provide a robust & scalable hardware infrastructure. IBM PowerVM is used to provide a

flexible virtualized environment at the IDSICC.

The middleware layer includes Information Managemen t DB2 Version 9.1, WebSphere Application Server 6.1 a nd

Lotus Sametime 7.5.

Optimizing the IBM technologies for top performance with the Dassault Systèmes software enables achievi ng the PCS illustrated in the three pictures below. Ge neral hardware server selection information resulting fro m the PCS testing for ENOVIA V6 may be obtained from

the IDSICC.

Version 6 on IBM Hardware and Middleware






04/03/09 39

ELLAPSE / DESIGNER – V6R2009






04/03/09 40

CPU CONSUMPTION / DESIGNER – V6R2009

les avantages de l'architecture v6 de ds evolutivité ... · pdf fileles avantages...

Documents