summaryrefslogtreecommitdiff
path: root/TAO/CIAO/tools/ServerActivator/README
blob: 1335c11b1a7109d10edcea63b5a149c6a58c08c2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
$Id$

This directory contains an implementation of ServerActivator, which is
the per-host daemon process CIAO's deployment and assembling framework
uses to spawn new component servers on the host.  CIAO currently does
not define how the deployment and assembling framework can locate
ServerActivator's so it is recommended that you start up all your
ServerActivator processes at a specific host.

The ServerActivator implementation registers a simple ObjectKey
"ServerActivator" to the IORTable, so if you start up the
ServerActivator process with:

  ServerActivator -ORBEndpoint iiop://hostname:13000

You can get to the ServerActivator interface using the following
IOR:

  corbaloc:iiop:hostname:13000/ServerActivator


Other command line flags supported by ServerActivator include:

  * -n <pathname> : Specify the pathname ServerActivator uses to
                    startup a ComponentServer process.

  * -o <filename> : Specify the filename ServerActivator uses to
                    write the IOR.

  * -i <ior> : Specify the IOR for the ComponentInstallation interface.
               It will be passed as

                  "-ORBInitRef ComponentInstallation=<ior>"

               command line options to the ComponentServer.

  * -d <second> : Specify the time, in second, ServerActivator will
                  wait for the ComponentServer to callback to notify
                  ServerActivator their IOR.  ServerActivator
                  considers the activation fails if the
                  ComponentServer does not call back in time.

  * -c : Try creating a container and install a home.

There is also a simple test program in this directory called
ServerActivator_test_client.  It is used to debug ServerActivator
implementation.