Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS Intelligent Event Processor (IEP) User's Guide Java CAPS Documentation |
Designing Intelligent Event Processor (IEP) Projects
Intelligent Event Processor Overview
Complex Event Processing and Event Stream Processing
IEP Design-Time and Runtime Components
Creating an Intelligent Event Processing Module Project
To Create an Intelligent Event Processing Module Project
To Add an Event Processor to the Project
Adding and Configuring IEP Operators
To Add IEP Operators to an Event Processor
To Configure IEP Operators in an Event Processor
Disabling the Generation of Bindings and Services
To Disable the Generation of Bindings and Services
Creating and Deploying the Composite Application Project
To Create a Composite Application Project
To Add the IEP Module Project to the Composite Application Project
To Define the Binding Components and Connections
To Deploy the Composite Application Project
IEP Operator Inputs and Outputs
To Create a Relation Aggregator Operator
To Create a Time Based Aggregator Operator
To Create a Tuple Based Aggregator Operator
Correlation and Filter Operators
To Create a Relation Map Operator
To Create a Stream Projection and Filter Operator
To Create a Tuple Serial Correlation Operator
To Create an External Table Polling Stream Operator
To Create a Replay Stream Operator
To Create a Stream Input Operator
To Create a Table Input Operator
To Create a Batched Stream Output Operator
To Create an Invoke Stream Operator
To Create a Relation Output Operator
To Enable the Save Stream Operator Dynamically at Runtime
To Disable the Save Stream Operator Dynamically at Runtime
To Create a Delete Stream Operator
To Create an Insert Stream Operator
To Create a Notification Stream Operator
To Create a Relation Stream Operator
To Create an Intersect Operator
To Create a Union All Operator
To Create a Contiguous Order Operator:
To Create a Gap Window Operator:
To Create an Attribute Based Window Operator
To Create a Partitioned Window Operator
To Create a Time Based Window Operator
To Create a Tuple Based Window Operator
WSDL Documents in IEP Module Projects
Data Types in the WSDL Document
Message Objects in the WSDL Document
Bindings and Services in the WSDL Document
Generating Concrete WSDL Documents
Generating Abstract WSDL Documents
Understanding the IEP Database
Configuring the IEP Database to Use Oracle
To Create the IEP User in the Oracle Database
To Install the Oracle Database Driver in the Application Server
To Create the Non-XA Connection Pool
To Create the Non-XA JDBC Resource
To Create the XA Connection Pool
To Create the XA JDBC Resource
To Enable Automatic Recovery of XA Transactions
To Configure the IEP Service Engine to Use the JDBC Resources
To Restart the IEP Service Engine and Create the Database Tables
Configuring the IEP Database to Use MySQL
To Create the IEP User in the MySQL Database
To Install the MySQL Database Driver in the Application Server
To Create the Non-XA Connection Pool
To Create the Non-XA JDBC Resource
To Create the XA Connection Pool
To Create the XA JDBC Resource
To Enable Automatic Recovery of XA Transactions
To Configure the IEP Service Engine to Use the JDBC Resources
To Restart the IEP Service Engine and Create the Database Tables
IEP Service Engine-Specific Database Tables
Event Process-Specific Database Tables
Operator-Specific Database Tables
Configuring Message Reliability in an IEP Module Project
Output operators enable you to send data from an event process to an external source.
The Batched Stream Output operator enables you to output events in batches, rather than one event at a time.
Depending on the downstream JBI component, this approach can improve performance. For example, if you are using IEP with the File Binding Component, sending 10 events at a time might be faster than sending one event at a time.
The property editor opens. Notice that the component has inherited the schema of its input stream.
For example, assume that the batch size is 10 and the maximum delay is 30 seconds. If 30 seconds have passed since the previous batch was sent, and only eight events have arrived, then the operator sends the eight events.
The Invoke Stream operator enables you to send a stream of data from one event process directly to another event process. The stream does not go through the Normalized Message Router.
For example, you could create two event processes:
The first event process contains a Stream Input operator and a Stream Output operator.
The second event process contains a Stream Input operator and an Invoke Stream operator.
You could then configure the Invoke Stream operator in the second event process to send data to the first event process.
The property editor opens.
The Select Stream Input dialog box appears.
Now you can deploy both event processes. When an event is sent to the stream input of the second event process, the Invoke Stream operator sends the event to the stream input of the first event process.
The Relation Output operator sends out groups of tuples that reflect its input. When an event triggers a change in a relation result, the operator sends out changes rather than an entire result each time a triggering event is received.
The Relation Output operator sends out groups of tuples that reflect changes in the relation result. Whenever an event triggers a change in the relation result, the operator sends out records with a tag on the end. If the tag is a plus sign (+), then the record has been added. If the tag is a minus sign (-), then the record has been deleted.
If a change occurs as a result of the triggering event such that a record changes, IEP sends a delete record matching the changed record. IEP sends an add record when there is an updated or new version of that record. The operator only sends out change events rather than repeatedly sending the entire result.
If a triggering event enters into the event process, but the result of the final relation from that event does not change, then the relation output is not triggered and data is not sent.
Use the Relation Output operator to provide a summary of data that has been added or deleted.
The property editor opens.
The Save Stream and Replay Stream operators are intended to help you perform diagnostics. For example, you can use these operators when the output from an IEP Module project is not the expected output.
You first enable the Save Stream operator to begin saving an input stream to a database table. You then use the Replay Stream operator to replay the events that the Save Stream operator saved to the database table.
Before you begin, you must deploy an event process that contains a Stream Input operator.
Note - If you know up front that you want to save an input stream to a database table, then you can use the Save Stream operator at design time. The property editor enables you to configure the same properties described in the following procedure.
The command returns a list of plan names. For example:
[IEP] listIEP CompositeApp1-IepModule1 test_iep
The command returns a list of the operators in the event process. For example:
[IEP] listOperators test_iep StreamInput0 StreamOutput0
The command returns the name of the Save Stream operator that was added. For example:
[IEP] addSaveStream test_iep StreamInput0 jdbc/iepseDerbyNonXA STOCKTRANSACTIONS false The result is StreamInput0SaveStream0
[IEP] removeSaveStream test_iep StreamInput0SaveStream0
If the Is Global parameter of the addSaveStream command was set to true, then the table and its data are not deleted. However, if you subsequently modify the schema of the stream input (for example, by adding a column) and re-enable the Save Stream operator, then the table and its data are deleted at that time.
If the Is Global parameter of the addSaveStream command was set to false, then the table and its data are deleted.
The Stream Output operator enables you to convert a stream of events into outgoing messages that can be sent to the Normalized Message Router and received by any JBI component.
When the WSDL document for the event processor is automatically generated, IEP uses the Stream Output operator to define various WSDL elements. For example, if the Stream Output operator is called SuspiciousTransactions, then the WSDL document contains an operation called SuspiciousTransactions and a message called SuspiciousTransactions_Msg.
The property editor opens. Notice that the component has inherited the schema of its input stream.
The Table Output operator provides static output in the form of relational tables.
Use the Table Output operator to provide relational table output from an event processor.
The property editor opens.
The table related to the Table Output is created if it does not exist. The table remains after the undeployment or redeployment of the IEP process that contains it. IEP generates an additional column for every table that is output.