Dassault Enovia, a Case Study of CORBA. Introduction Distributed Architecture Orbix Im plem entation Detail Conlcusion

Transcription

1 Dassault Enovia, a Case Study of CORBA Introduction Distributed Architecture Orbix Im plem entation Detail Conlcusion

2 Introduction What's a PLM solution? Who uses PLM products? The distributed requirem ent of the users

3 Distributed Architecture of Enovia Relevant components Client, VPM Navigator Enovia LCA Server Manager Enovia Vault Manager Relational Database Engine Requirements Accessibility Transparency Openness Scalability

4 Basic Enovia Architecture

5 Accessibility Requirement Different disciplines Aerospace Engineer Industrial Engineer Repeairman Integration with existing Authentication mechanism Difference in measure systems Difference in language

6 Transparency Requirement Access: hide physical representation of data Different IT infrastructure Location: Hide the real location of a data Server Manager proxies requests Distributed Vaults Migration: No reconfigurations required DNS, IP Aliases Replication: Hide data replication Using master vault and read-only vault

7 Distributed Enovia Architecture

8 Openness Requirement Extendability CORBA CAA C/C++/Java API

9 scalability Requirement Geographically Distributed vaults Remote invocation using CORBA Load wise Clustering of independent vault managers Scalable underlying technologies Oracle NFS

10 IONA Orbix CORBA3 Compliant Orb Most Deployed in the industry Available for leading applicative platforms Linux, Windows, UNIX Advanced Features DII Bidirectional GIOP etc

11 Technical Implementation Details Client configuration VPM Navigator Orbix naming daemon host:port VaultClient.properties 3DCom Web Client Naming Daemon configuration Implementation Repository Server Manager Configuration Vault Manager Configuration

12 Client Configuration Centralized Ease of administration Consistent across all sites Single point of failure can be avoided Dynamic configuration Load balancing Failover Use of local vault replica

13 Centralized Dynamic Configuration

14 Sample VaultClient.propreties Host A VaultClient_DefaultAliasName = Vault VaultClient_Vault_ReadVaultServerName = Vault VaultClient_Vault_ReadVaultServerHostName = X VaultClient_Vault_ReadVaultServerDaemonPort = VaultClient_Vault_WriteVaultServerName = Vault VaultClient_Vault_WriteVaultServerHostName = Z VaultClient_Vault_WriteVaultServerDaemonPort = Host B VaultClient_DefaultAliasName = Vault VaultClient_Vault_ReadVaultServerName = Vault VaultClient_Vault_ReadVaultServerHostName = Y VaultClient_Vault_ReadVaultServerDaemonPort = VaultClient_Vault_WriteVaultServerName = Vault VaultClient_Vault_WriteVaultServerHostName = Z VaultClient_Vault_WriteVaultServerDaemonPort = 54270

15 Naming Deamon Configuration Indirect Binding Object persistence Enovia LCA server Manager ( CATIAServerManager) Enovia Vault Manager Orbix Implementation Repository Text, editable.imp file Read at runtime

16 Vault Manager.imp file Name : Vault Comms : cdr/tcp Activation : shared Owner : root Launch : ;all; Invoke : ;all; ImpRep Version : 2 no. of servers : 1 server's port : 0 Marker Launch Command * /...somepath.../runenovvaultstarter

17 Server Manager Details Started by indirect binding Responsible for activating object for clients VPM example See following chart

18 Flow of initial VPM invocation

19 Vault Manager details Started by Indirect binding Takes requests from Server Manager to setup file transfers Only one servant is required to handle file transfers Only receives incoming connections from clients.

20 Conclusion Enovia is a Distributed system Accessible Transparent Open Scalable CORBA is a key component in making it possible Remote invocation Naming service & indirect binding Openness & Extendability