Dassault Enovia, a Case Study of CORBA

More documents

Recommendations

Info

Sample VaultClient.propreties Host A VaultClient_DefaultAliasName = Vault VaultClient_Vault_ReadVaultServerName = Vault VaultClient_Vault_ReadVaultServerHostName = X VaultClient_Vault_ReadVaultServerDaemonPort = 54270 VaultClient_Vault_WriteVaultServerName = Vault VaultClient_Vault_WriteVaultServerHostName = Z VaultClient_Vault_WriteVaultServerDaemonPort = 54270 Host B VaultClient_DefaultAliasName = Vault VaultClient_Vault_ReadVaultServerName = Vault VaultClient_Vault_ReadVaultServerHostName = Y VaultClient_Vault_ReadVaultServerDaemonPort = 54270 VaultClient_Vault_WriteVaultServerName = Vault VaultClient_Vault_WriteVaultServerHostName = Z VaultClient_Vault_WriteVaultServerDaemonPort = 54270
Naming Deamon Configuration ● ● Indirect Binding – Object persistence – <strong>Enovia</strong> LCA server Manager ( CATIAServerManager) – <strong>Enovia</strong> Vault Manager Orbix Implementation Repository – Text, editable .imp file – Read at runtime
Page 1 and 2: Dassault Enovia, a Case Study of CO
Page 3 and 4: Distributed Architecture of Enovia
Page 5 and 6: Accessibility Requirement ● ●
Page 7 and 8: Distributed Enovia Architecture
Page 9 and 10: scalability Requirement ● ● Geo
Page 11 and 12: Technical Implementation Details
Page 13: Centralized Dynamic Configuration
Page 17 and 18: Server Manager Details ● ● ●
Page 19 and 20: Vault Manager details ● ● ●

Dassault Enovia, a Case Study of CORBA

Create successful ePaper yourself

Delete template?

Save as template?