Consortium Solutions Middleware Forge MyObjectWeb | |||||||||
|
OpenCCM
|
Table of Contents
About Distributed OpenCCM ExecutionThis document describes how to run OpenCCM on top of a distributed system, e.g. five computers interconnected by a local area network (LAN). The OpenCCM Execution Tool Chain provides a set of scripts to start and stop the CORBA services (CosNaming, CosTrading and CosTransaction services), the OpenCCM Comanche HTTP server, standalone OpenCCM Component Servers, OpenCCM DCI Managers / AssemblyFactorys / Nodes, and the OpenCCM Browser in an OS and ORB independent way. The following sections describe how to distribute the execution of the OpenCCM scripts according to various scenarios:
Fully Centralized Execution
This scenario is the basic one where all OpenCCM scripts are executed
on a single node. As shown in the next figure, all OpenCCM daemons
will run on the node
The following table lists step by step the OpenCCM scripts to run
on the node
Let's note that steps 3 and 4 are optional and only required if the CosTrading and CosTransactions services will be used. Distributed ClientsThis scenario allows you to access to centralized OpenCCM services from remote nodes. The following table lists step by step the OpenCCM scripts to run on the various nodes.
Let's note that steps 3 and 13 are optional and only required if the CosTrading service will be used. Let's note that steps 4 and 14 are optional and only required if the CosTransactions service will be used. Distributed Component Servers
This scenario allows you to start a standalone OpenCCM Component Server on each node.
However all the main OpenCCM services continue to run on the single node The following table lists step by step the OpenCCM scripts to run on the various nodes.
Let's note that steps 17 to 20 could be executed in parallel as they have no dependency. Distributed Node Managers
This scenario allows you to start an OpenCCM DCI Node Manager on each node.
However all the main OpenCCM services continue to run on the single node The following table lists step by step the OpenCCM scripts to run on the various nodes.
Let's note that steps 17 to 20 could be executed in parallel as they have no dependency. Distributed CORBA Services
This scenario illustrates the distribution of CORBA services on distinct nodes.
All the OpenCCM DCI daemons still run on the single node The following table lists step by step the OpenCCM scripts to run on the various nodes. Let's note that steps 5 and 6 are optional and only required if the CosTrading service will be used. Let's note that steps 7 and 8 are optional and only required if the CosTransactions service will be used. Fully Distributed ExecutionThis scenario illustrates the distribution of all OpenCCM scripts on distinct nodes. The following table lists step by step the OpenCCM scripts to run on the various nodes. Let's note that steps 5 and 6 are optional and only required if the CosTrading service will be used. Let's note that steps 7 and 8 are optional and only required if the CosTransactions service will be used. Let's note that steps 9 to 13 could be executed in parallel as they have no dependency. Let's note that steps 17 to 21 could be executed in parallel as they have no dependency. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster | Last modified at 2005-07-07 02:04 PM |