blob: 3a32ca42431760a9b133a65ddcf78325bf1301f5 (
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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
$Id$
README for Notify_Service
-------------------------
The Notify_Service executable starts up a Notification Service factory and
registers it with the Naming Service under the name "NotifyEventChannelFactory"
Command line arguments:
----------------------
"-?" : shows the options.
"-Factory factory_name" : Uses the <factory_name> as the default name for the
Channel Factory
The default is "NotifyEventChannelFactory".
"-Boot" : Flag asking that the <factory_name> be registered
in the IOR table.
The option is disabled by default.
See the "Using the Boot option" section below.
"-NameSvc" : Registers the Factory and if specified, an Event
Channel with the Naming Service.
if this option is used, a Naming Service must
be accessible.
This option is enabled by default.
"-NoNameSvc" : Asks to skip any registration with the
Naming Service.
This option is disabled by default.
"-IORoutput file_name" : The IOR is output to the file <file_name>.
By default, the IOR is printed out.
"-Channel" : If this option is specified, a EventChannel is
created and registered with the Naming Service.
This option is disabled by default.
"-ChannelName channel_name": Specifes the <channel_name> to register with the
Naming Service.
The default is "NotifyEventChannel".
"-Notify_TPReactor [threads]": Tells the Notify Service that the ORB
will use a TP reactor and specifies the
number of worker threads to utilize.
Note that the svc.conf file must instruct the oRB to use a TP reactor
e.g. static Resource_Factory "-ORBReactorType tp -ORBReactorMaskSignals 0"
Please look up the ORB configuration options to get more information
on this.
Running the Service:
-------------------
1. Start the Naming Service from $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service if you are using the "-NameSvc" options.
2.Start the Notify_Service from this directory. You should see a message saying
that the service has been started.
Using the Boot option:
----------------------
an example on how to locate the Notify Factory without the Naming Service -
./Notify_Service -Boot -NoNameSvc -d -ORBobjrefstyle url -ORBEndPoint "iiop://flamenco.cs:9999"
The Factory object reference is not registered with the Naming Service.
"-Boot" binds the Factory object reference with "NotifyEventChannelFactory" in
the IOR table.
See the $TAO_ROOT/docs/Options.html for details on "-ORBEndPoint"
A client program can obtain the factory object reference in the following
manner:
./client -ORBInitRef "NotifyEventChannelFactory=iioploc://flamenco.cs:9999/NotifyEventChannelFactory"
Note that the client uses:
resolve_initial_references ("NotifyEventChannelFactory");
to obtain the object reference.
The svc.conf options:
----------------------
The "Notify_Default_Event_Manager_Objects_Factory" service object accepts the following options:
"-MTDispatching" : Enable MT dispatching
"-DispatchingThreads [thread_count]" : How many threads for MT dispatching.
"-MTSourceEval" : Enable MT proxy consumer(source) filter evaluation.
"-SourceThreads [thread_count]" : How many threads for source filter evaluation.
"-MTLookup" : Enable MT subscription table lookup.
"-LookupThreads [thread_count]" : How many lookup threads.
"-MTListenerEval" : Enable MT proxy supplier (listener) filter evaluation.
"-ListenerThreads" : How many threads for listener filter evaluation.
"-Notify_TPReactor [threads]" : Tells the service that the ORB
is using a TP reactor and
specifies the number of worker
threads to deploy.
Note that you might have to
specify the TP reactor in the
svc.conf file.
(see the ORB configutrations
for details on this)
e.g. svc.conf
static Notify_Default_Event_Manager_Objects_Factory "-MTSourceEval -MTDispatching -DispatchingThreads 2"
This means that we want to enable MT proxy supplier filter evaluation
(default 1 thread) and MT event dispatching with 2 threads.
|
