Assembly

The assembly program provides one piece of infrastructure that is missing in the standard MicoCCM distribution. While the MicoCCM Daemon mico-ccmd implements the AssemblyFactory interface, it requires this tool as an implementation of the Assembly interface.

The Assembly and Deployment Toolkit do not depend on assembly, as the deployment option in the Assembly Tool and the Deployment Tool interact with the ComponentServer directly. This implementation of the Assembly interface is complementary, and can be used optionally to support the full range of the CORBA Component Packaging and Deployment interface chain.

The assembly program is usually spawned from the MicoCCM Daemon as result of a create operation on the AssemblyFactory interface. Therefore, if you want to make use of the Assembly interface, you should make sure that assembly is found by the running instance of mico-ccmd.

Optionally, assembly can also be run as a standalone program to host an Assembly, providing a CORBA interface to start (build) and stop (tear_down) components within that Assembly.

  assembly [<options>] <archive>

archive can be a file name or URL of an Assembly Archive (.aar) or CORBA Assembly Descriptor (.cad). The program will then listen for invocations of its Assembly interface (see the CORBA Components specification for details).

The following options are accepted:

--ccmd <IOR>

This option sets the address of the MicoCCM Daemon where the homes and components are to be deployed.

--host <host>[:portno]

This is an alternative option to set the address of the MicoCCM Daemon. The default address is localhost:1234, and assumes that mico-ccmd has been started with the command-line option -ORBIIOPAddr inet::1234.

--dont-call-configuration-complete

By default, the 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

By default, a new Component Server is created for each home in the assembly, effectively placing all homes into separate processes. If this option is set, only one Component Server will be used for all homes and components, so that all components are collocated with each other.

--token <name>

This option assigns a name for the Assembly. This option is passed by the MicoCCM Daemon to identify assemblies, but is not necessary if run as a standalone program.

--autoexit

Causes the program to exit after the assembly has been stopped using the tear_down operation of the Assembly interface. When run from the MicoCCM Daemon, the program is usually stopped as the result of the destroy operation of the AssemblyFactory interface. This option may make for more desirable behavior as a standalone program.

--ior <file>

Writes the object reference of the Assembly interface to the given file, or to standard output if a single hyphen is given as file name.

-ORBInitRef NameService=<url>

The Deployment Tool understands this standard option to configure the address of the Naming Service. You need to set the reference to the Naming Service if any part of the assembly references the Naming Service, e.g. components that are to be registered.

-v

Prints progress information to standard output.