diff options
Diffstat (limited to 'TAO/orbsvcs/tests/EC_Multiple/README')
| -rw-r--r-- | TAO/orbsvcs/tests/EC_Multiple/README | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/TAO/orbsvcs/tests/EC_Multiple/README b/TAO/orbsvcs/tests/EC_Multiple/README new file mode 100644 index 00000000000..14119bdfd87 --- /dev/null +++ b/TAO/orbsvcs/tests/EC_Multiple/README @@ -0,0 +1,34 @@ +# $Id$ + + This test ilustrates how to connect multiple ECs; it has many +options and can be configured to run a single EC, two ECs connected +through a Gateway, short-circuit the EC, use a global, local or +precomputed schedule, etc. + + Please see the scripts for typical configurations. + + A simple test is that uses a pre-computed schedule would be: + +# Run the Naming Service +$ ../../Naming_Service/Naming_Service + -p NameService.pid -o NameService.ior +# If the multicast location does not work for your use: +# +# NameService=`cat NameService.ior` +# export NameService +# +# or other commands that suit your shell. +# + +# Run the first EC, supplier generates events <1> and <2> consumer +# subscribes to events <1> and <3> +$ ./EC_Multiple -l ECM1 -r ECM2 -s runtime -p ECM1.pid \ + -h 1,1,1,250000,100,1,2,1,3 + +# Run the second EC, supplier generates events <4> and <3> consumer +# subscribes to events <4> and <2> +$ ./EC_Multiple -l ECM2 -r ECM1 -s runtime -p ECM2.pid \ + -h 1,1,1,250000,100,4,3,4,2 + +# Notice how the consumer receives both local and remote events, but +# not all the local neither all the remote events. |