The Deployment Tool allows you to deploy CORBA Component Assemblies. This is, in the world of components, the equivalent of starting a server. An assembly contains one or more component implementations (either contained within the Assembly, or referenced), component properties (intial values for attributes) and configuration information (connections between facets and receptacles or event sources and sinks).
The Deployment Tool reads an assembly, uploads each implementation to a Component Server, and then configures the assembly according to the given information.
The Deployment Tool is a console program that takes as single argument either a Component Assembly Descriptor (.cad) or a Component Assembly Archive (.aar). It also accepts the following options:
--ccmd <IOR>
--host <host>[:portno]
localhost:1234
, and
assumes that mico-ccmd
has been started with the
command-line option -ORBIIOPAddr inet::1234
.
--server [host:]<portno>
mico-ccmd
) is sent
an URL to download files from. This option changes the defaults
for the host name and port number (1235) that the internal
HTTPD server uses. You may need this option to set the host
name to something that the remote host (where
mico-ccmd
is running) understands.
--dont-call-configuration-complete
configuration_complete
operation
is called on each deployed component to indicate the end of
configuration and the start of normal operation. Use this
option if this behavior is not desired.
--collocated
-ORBInitRef NameService=<url>
-v
After starting the MicoCCM Daemon on host there
using
mico-ccmd -v -ORBIIOPAddr inet::1234you can then, on host
here
, deploy an assembly
mycomponents.aar
using
./deploy --host there mycomponents.aar
Note that the Deployment Tool allows to deploy an assembly on a remote
host - thanks to CORBA, this is entirely transparent. And even more,
the Deployment Tool allows to deploy assemblies straight from the Web,
as it is perfectly happy with an http
URL on the command
line instead of a filename.
Frank Pilhofer, fp@fpx.de