SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 142 | Next

Frank Jennings, David Salter

"Building SOA-Based Composite Applications Using NetBeans IDE 6"


Intelligent Event Processor
[ 164 ]
IEP processes inbound business events through 'windows' or data streams in units
of time. Within the JBI Runtime, Binding Components and other Service Engines
can act as containers too. Service Units (SU) can be deployed to installed Binding
Components and Service Engines. The Service Unit can describe what services are
provided and consumed by the component.
Input Endpoints Output Endpoints
Intelligent Event Processor
Table
Stream
Relation
Table
Stream
Event processors can receive events from any number of Input Endpoints. There are
basically two kinds of Input Endpoints:
1. Stream Input Endpoint: A web service, which other applications can invoke
to send events. Streams are similar to event histories.
2. Table Input Endpoint: Denotes a SQL database table. The event processor
can read from the table, while the other applications can write to the table.
The event processors deliver events to other applications through its Output
Endpoints. It can have multiple Output Endpoints. There are three kinds of
Output Endpoints:
1. Stream Output Endpoint: A web service, which other applications can
invoke to receive events created by the event processor.
2. Relation Output Endpoint: A web service, which other applications can
invoke to receive updates to a relation created by the event processor.


Pages:
130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154