Back to Main Page
The OpenFusion TAO IMR is made up of a single locator process (tao_imrd)
with 0 or more activator daemon processes (tao_activator). Registration
of running servers is on a per persistent POA basis.
An IMR manager utility (tao_imrd_mgr) is also provided to administer
the ImR.
New IMR Features:
- Supports registration of and forwarding to multi-profile object
references.
- Persistent POA registration and resolution is based on fully
qualified POA name (e.g. POAs parentPOA1/myPOA and parentPOA2/myPOA
will be distinguishable by the IMR and the registration of both will be
permitted).
- tao_activator's are identified by their object references rather
than the host name of the machine they run on. This means that it is
possible to run more than one tao_activator per host.
- There is no longer a need for an activator to run on every physical
machine on which ImR registered servers are to run, in fact, if
auto-activation is not to be used there is no requirement for any
activators to be run. Additionally, if auto-activation is used there is
no need for an activator to run on the same physical host as the
servers it starts.
Features from the original IMR not yet supported for this release:
- Activation per client.
- Repository data persistence.
- Shutdown of running servers using the tao_imr_mgr tool.
- Ability to run as NT service.
Changes to tao_imrd / tao_activator (previously ImplRepo_Service /
ImR_Activator) run-time options:
- -i - (previously -o) - option to specify the filename to output
the services.
- -s on / off - (previously -a) - permit servers to register
themselves with the IMR without their names needing to be
pre-registered with the tao_imrd_mgr tool.
- -a 1/3 (no previous option) = Aliveness policy. Value '1' will
cause the IMR to ping registered servers before forwarding a client to
the server. Value '3' (which is also the default if this option is not
specified) will not.
Changes to tao_imrd_mgr (previously tao_imr) run-time options:
- 'add' command. When adding a poa name to the repository, if a
start-up command is to be specified then the object ref location of the
activator which is to perform the activation must be specified. e.g.
tao_imrd_mgr add airplane_server -l file://activator.ior
-ORBInitRef ImplRepoService=file://imrd.ior -c "airplane_server
-ORBUseIMR 1 -ORBUseOFIMR 1"
- 'daemons' command. Will list the locations (in the form of corbaloc
URI's) of all running activators. e.g.
tao_imrd_mgr daemons -ORBInitRef ImplRepoService=file://imrd.ior

Top