Each event processor that
you create can work with a single message stream. The common actions that you
perform through this editor are defining actions like simple filtering, routing, and
aggregations over a period of time (window). A simple example could be to create
an IEP that monitors the reservation process from different airlines over a period
of time.
The JBI container is part of the Sun Java System / GlassFish Application Server.
In order to work with the IEP Editor, you need to start this server and also the IEP
Service Engine highlighted in the following figure:
As discussed earlier, the IEP Service Engine internally uses the Java DB. Hence, make
sure that the Java DB is running through NetBeans.
When you start the IEP Service Engine for the first time, it creates a set of tables that
are either data tables containing data related to your IEP applications or internal tables
used by the Service Engine. Do not try to alter or delete the internal tables created by
the IEP Service Engine. The internal tables can include the following tables:
Chapter 8
[ 175 ]
EMS_PLAN: This table tracks deployment of event processors and assigns
an Instance ID. Each time you deploy an IEP, an entry appears indicating the
event processor has been deployed.
EMS_OUTPUT: This table is updated every time another table is updated.
Pages:
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161