blob: 8d7fd8f95b321b921199b2dded93e6bed9ed8d8e (
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
|
CORBA COS Event Service
-----------------------
The CosEvent_Service is a COS compilant Event Service.
The service is registered with the naming service with the name
"CosEventService" .It exposes the <EventChannel> interface which can be
used by suppliers and consumers to send and receive events.
To run the Event Channel:
------------------------
1. you should have a running Naming Service.
if not, start one at $TAO_ROOT/orbsvcs/Naming_Service/Naming_Service
2. if you want to use the -t option you should have a running
Real Time Event Channel.
if not, start one at $TAO_ROOT/orbsvcs/Event_Service/Event_Service
3. execute the CosEvent_Service.
Command line parameters:
------------------------
-n <COS Event Service name>
specifies the name with which to register the Event Service.
-r
specifies that a local Real Time Event Channel (Rtec) should be
created and used.
-t <Real Time Event Service name>
specifies the name with which to *look* for the RtEC.This option is
only useful along with the -r option.
The next 3 options are used to introduce a filtering mechanism for the
Event Channel based on event types and source ids.
-e ["EventType_1 EventType_2..."]
specifies the event types for the ConsumerQOS.When the Rtec is being
setup, the ConsumerQOS is specified.
The event types should start at >= ACE_ES_EVENT_UNDEFINED = 16.
e.g. -e "17 20 40" specifies that event types with ids 17, 20 and 40
should be passed to the consumers.
-o ["EventSourceID_1 EventSourceID_2.."]
specifies the source ids for the ConsumerQOS.
-p ["sourceID EventTypeID"]
specifies a pair of sourceid and event type for the Supplier QOS.
Author:
-------
Pradeep Gore <pradeep@cs.wustl.edu>
|
