9 Configuring Channels

9.1.1 System-Timestamped Channels

By default, channels are system-timestamped. In this case, Oracle CEP will assign a new time from the CPU clock under two conditions: when a new event arrives, and when the configurable heartbeat timeout expires.

For more information, see:

• Section 9.2.1, "How to Configure a System-Timestamped Channel Using Oracle CEP IDE for Eclipse"

• Section C.41, "heartbeat-timeout"

9.1.2 Application-Timestamped Channels

Optionally, you can configure a channel to be application-timestamped. In this case, the time-stamp of an event is determined by the configureable wlevs:expression tag. A common example of an expression is a reference to a property on the event. If no expression is specified, then the time-stamp may be propagated from a prior event. For example, this is the case when you have a system-timestamped channel from one Oracle CQL processor feeding events into an application-timestamped channel of another downstream Oracle CQL processor.

In addition, an application can use StreamSender.sendHeartbeat() to send an event of type heart-beat downstream to StreamSink listeners in the EPN.

For more information, see:

• Section 9.2.2, "How to Configure an Application-Timestamped Channel Using Oracle CEP IDE for Eclipse"

• Section D.3, "wlevs:application-timestamped"

• Section D.14, "wlevs:expression"

9.1.3 Channels Representing Streams and Relations

A channel can represent either a stream or a relation:

• A stream supports appends only. You specify a channel as a stream by setting EPN assembly element wlevs:channel attribute is-relation to false (the default).

• A relation supports inserts, deletes, and updates. You specify a channel as a realtion by setting EPN assembly element wlevs:channel attribute is-relation to true.

For more information, see Section 1.1.4, "Stream Sources and Stream Sinks and Relation Sources and Relation Sinks".

9.2.1 How to Configure a System-Timestamped Channel Using Oracle CEP IDE for Eclipse

This section describes how to create a system-timestamped channel.

The most efficient and least error-prone way to create and edit a channel configuration in the default component configuration file is to use the Oracle CEP IDE for Eclipse. Optionally, you can create a channel configuration file manually (see Section 9.2.3, "How to Create a Channel Component Configuration File Manually").

For more information, see:

• Section 9.1.1, "System-Timestamped Channels"

• Chapter 5, "Oracle CEP IDE for Eclipse and the Event Processing Network"

To configure a channel using Oracle CEP IDE for Eclipse:

1. Use Oracle CEP IDE for Eclipse to create a channel.

   See Section 5.4.1.1, "How to Create a Basic Node".

2. Optionally, override the default channel assembly file configuration by adding additional wlevs:channel attributes and child elements:

   1. Right-click the channel node and select Go To Assembly Source.

   2. Add the appropriate wlevs:channel attributes.

      In particular, specify whether this channel is a stream or relation by configuring attribute is-relation:

      • To specify this channel as stream , set is-relation to false (default).

      • To specify this channel as a relation, set is-relation to true.

      See Table D-9, "Attributes of the wlevs:channel Application Assembly Element".

   3. Add the appropriate wlevs:channel child elements.

      • Appendix D, "wlevs:instance-property"

      • Appendix D, "wlevs:listener"

      • Appendix D, "wlevs:property"

      • Appendix D, "wlevs:source"

3. In the Project Explorer, expand your META-INF/wlevs directory.

4. Choose the component configuration file you want to use:

   1. To use the default component configuration file, right-click the META-INF/wlevs/config.xml file and select Open With > XML Editor.

      The file opens in an XML Editor.

   2. To create a new component configuration file:

      • Right-click the wlevs directory and select New > File.

        The New File dialog appears.

      • Enter a file name.

        You can name the file anything you want but the name of the file must end in .xml.

      • Click Finish.

        Oracle CEP IDE for Eclipse adds the component configuration file to the wlevs directory.

5. Right-click the component configuration file you chose to use and select Open With > XML Editor.

   The file opens in an XML Editor.

6. If you created a new component configuration file, add the header and config element shown in Example 9-3. Otherwise, proceed to step 7.

   Example 9-3 Component Configuration File Header and config Element

   <?xml version="1.0" encoding="UTF-8"?>
   <n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/application wlevs_application_config.xsd" 
   xmlns:n1="http://www.bea.com/ns/wlevs/config/application" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   
   </config>
   

7. Add a channel element for the channel as Example 9-4 shows.

   Example 9-4 Component Configuration File Channel Element

   <?xml version="1.0" encoding="UTF-8"?>
   <n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/application wlevs_application_config.xsd" 
   xmlns:n1="http://www.bea.com/ns/wlevs/config/application" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <processor>
           ...
       </processor>
       ...
       <channel>
       </channel>
   </config>
   

8. Add a name child element to the channel element.

   The name element value must match the corresponding EPN assembly file channel element's id attribute.

   For example, given the EPN assembly file channel element shown in Example 9-5, the corresponding configuration file channel element is shown in Example 9-6.

   Example 9-5 EPN Assembly File Channel Id: priceStream

   <wlevs:channel id="priceStream" event-type="PriceEvent">
       <wlevs:listener ref="filterFanoutProcessor" />
       <wlevs:source ref="PriceAdapter" />
   </wlevs:channel>
   

   Example 9-6 Component Configuration File Channel Name: priceStream

   <channel>
       <name>priceStream</name>
   </channel>
   

   Caution:

   Identifiers and names in XML files are case sensitive. Be sure to specify the same case when referencing the component's identifier in the EPN assembly file.

9. Optionally, override the default channel configuration by adding additional channel child elements:

   • Add a max-threads child element to specify the maximum number of threads that Oracle CEP server uses to process events for this channel.

     Setting this value has no effect when max-size is 0. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-threads>2</size>
     </channel>
     

     When set to 0, the channel acts as a pass-through. When max-threads > 0, the channel acts as classic blocking queue, where upstream components are producers of events and the downstream components are the consumers of events. The queue size is defined by the configuration max-size. There will be up to max-threads number of threads consuming events from the queue.

   • Add a max-size child element to specify the maximum size of the channel.

     Zero-size channels synchronously pass-through events.

     Non-zero size channels process events asynchronously, buffering events by the requested size. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-size>10000</size>
     </channel>
     

   • Add a heartbeat-timeout child element to specify the number of nanoseconds a channel can be idle before Oracle CEP generates a heartbeat event to advance time.

     The heartbeat child element applies to system-timestamped relations or streams only when no events arrive in the event channels that are feeding the processors and the processor has been configured with a statement that includes some temporal operator, such as a time-based window or a pattern matching with duration.

     <channel>
         <name>MatchOutputChannel</name>
         <heartbeat-timeout>10000</heartbeat-timeout>
     </channel>
     

   • Add a selector child element to specify which up-stream Oracle CQL processor queries are permitted to output their results to the channel.

     Figure 9-1 shows an EPN with channel filteredStream connected to an up-stream Oracle CQL processor filteredFanoutProcessor.

     Figure 9-1 EPN With Oracle CQL Processor and Down-Stream Channel

     
     Description of "Figure 9-1 EPN With Oracle CQL Processor and Down-Stream Channel"
     
     

     Example 9-7 shows the queries configured for the Oracle CQL processor.

     Example 9-7 filterFanoutProcessor Oracle CQL Queries

     <processor>
         <name>filterFanoutProcessor</name>
         <rules>
             <query id="Yr3Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="3_YEAR"
             ]]></query>
             <query id="Yr2Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="2_YEAR"
             ]]></query>
             <query id="Yr1Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="1_YEAR"
             ]]></query>
         </rules>
     </processor>
     

     If you specify more than one query for an Oracle CQL processor as Example 9-7 shows, then, by default, all query results are output to the processor's out-bound channel (filteredStream in Figure 9-1). Optionally, in the component configuration source, you can use the channel element selector attribute to specify a space-delimited list of one or more Oracle CQL query names that may output their results to the channel as Example 9-8 shows. In this example, query results for query Yr3Sector and Yr2Sector are output to filteredStream but not query results for query Yr1Sector.

     Example 9-8 Using selector to Control Which Query Results are Output

     <channel>
         <name>filteredStream</name>
         <selector>Yr3Sector Yr2Sector</selector>
     </channel>
     

     Note:

     The selector attribute is only applicable if the up-stream node is an Oracle CQL processor. For more information, see Chapter 10, "Configuring Oracle CQL Processors".

   For more information, see wlevs_application_config.xsd schema file.

10. Select File > Save.

    The EPN Editor adds a configuration badge to the channel as Figure 9-2 shows. For more information, see Section 5.2.4, "Configuration Badging".

    Figure 9-2 Channel With Configuration Badge

    
    Description of "Figure 9-2 Channel With Configuration Badge"
    
    

9.2.2 How to Configure an Application-Timestamped Channel Using Oracle CEP IDE for Eclipse

This section describes how to create an application-timestamped channel.

The most efficient and least error-prone way to create and edit a channel configuration in the default component configuration file is to use the Oracle CEP IDE for Eclipse. Optionally, you can create a channel configuration file manually (see Section 9.2.3, "How to Create a Channel Component Configuration File Manually").

For more information, see:

• Section 9.1.2, "Application-Timestamped Channels"

• Chapter 5, "Oracle CEP IDE for Eclipse and the Event Processing Network"

To configure a channel using Oracle CEP IDE for Eclipse:

1. Use Oracle CEP IDE for Eclipse to create a channel.

   See Section 5.4.1.1, "How to Create a Basic Node".

2. Optionally, override the default channel assembly file configuration by adding additional wlevs:channel attributes and child elements:

   1. Right-click the channel node and select Go To Assembly Source.

   2. Add the appropriate wlevs:channel attributes.

      In particular, specify whether this channel is a stream or relation by configuring attribute is-relation:

      • To specify this channel as stream , set is-relation to false (default).

      • To specify this channel as a relation, set is-relation to true.

      See Table D-9, "Attributes of the wlevs:channel Application Assembly Element".

   3. Add a wlevs:application-timestamped child element.

      Use this element to specify a wlevs:expression child element that Oracle CEP uses to generate timestamp values.

      Optionally, configure the wlevs:application-timestamped attributes:

      • is-total-order: specifies if the application time published is always strictly greater than the last value used.

        Valid values are true or false. Default: false.

      For more information, see Appendix D, "wlevs:application-timestamped".

   4. Add other appropriate wlevs:channel child elements.

      • Appendix D, "wlevs:instance-property"

      • Appendix D, "wlevs:listener"

      • Appendix D, "wlevs:property"

      • Appendix D, "wlevs:source"

3. In the Project Explorer, expand your META-INF/wlevs directory.

4. Choose the component configuration file you want to use:

   1. To use the default component configuration file, right-click the META-INF/wlevs/config.xml file and select Open With > XML Editor.

      The file opens in an XML Editor.

   2. To create a new component configuration file:

      • Right-click the wlevs directory and select New > File.

        The New File dialog appears.

      • Enter a file name.

        You can name the file anything you want but the name of the file must end in .xml.

      • Click Finish.

        Oracle CEP IDE for Eclipse adds the component configuration file to the wlevs directory.

5. Right-click the component configuration file you chose to use and select Open With > XML Editor.

   The file opens in an XML Editor.

6. If you created a new component configuration file, add the header and config element shown in Example 9-3. Otherwise, proceed to step 7.

   Example 9-9 Component Configuration File Header and config Element

   <?xml version="1.0" encoding="UTF-8"?>
   <n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/application wlevs_application_config.xsd" 
   xmlns:n1="http://www.bea.com/ns/wlevs/config/application" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   
   </config>
   

7. Add a channel element for the channel as Example 9-4 shows.

   Example 9-10 Component Configuration File Channel Element

   <?xml version="1.0" encoding="UTF-8"?>
   <n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/application wlevs_application_config.xsd" 
   xmlns:n1="http://www.bea.com/ns/wlevs/config/application" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <processor>
           ...
       </processor>
       ...
       <channel>
       </channel>
   </config>
   

8. Add a name child element to the channel element.

   The name element value must match the corresponding EPN assembly file channel element's id attribute.

   For example, given the EPN assembly file channel element shown in Example 9-5, the corresponding configuration file channel element is shown in Example 9-6.

   Example 9-11 EPN Assembly File Channel Id: priceStream

   <wlevs:channel id="priceStream" event-type="PriceEvent">
       <wlevs:listener ref="filterFanoutProcessor" />
       <wlevs:source ref="PriceAdapter" />
   </wlevs:channel>
   

   Example 9-12 Component Configuration File Channel Name: priceStream

   <channel>
       <name>priceStream</name>
   </channel>
   

   Caution:

   Identifiers and names in XML files are case sensitive. Be sure to specify the same case when referencing the component's identifier in the EPN assembly file.

9. Optionally, override the default channel configuration by adding additional channel child elements:

   • Add a max-threads child element to specify the maximum number of threads that Oracle CEP server uses to process events for this channel.

     Setting this value has no effect when max-size is 0. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-threads>2</size>
     </channel>
     

     When set to 0, the channel acts as a pass-through. When max-threads > 0, the channel acts as classic blocking queue, where upstream components are producers of events and the downstream components are the consumers of events. The queue size is defined by the configuration max-size. There will be up to max-threads number of threads consuming events from the queue.

   • Add a max-size child element to specify the maximum size of the channel.

     Zero-size channels synchronously pass-through events.

     Non-zero size channels process events asynchronously, buffering events by the requested size. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-size>10000</size>
     </channel>
     

   • Add a selector child element to specify which up-stream Oracle CQL processor queries are permitted to output their results to the channel.

     Figure 9-1 shows an EPN with channel filteredStream connected to an up-stream Oracle CQL processor filteredFanoutProcessor.

     Figure 9-3 EPN With Oracle CQL Processor and Down-Stream Channel

     
     Description of "Figure 9-3 EPN With Oracle CQL Processor and Down-Stream Channel"
     
     

     Example 9-7 shows the queries configured for the Oracle CQL processor.

     Example 9-13 filterFanoutProcessor Oracle CQL Queries

     <processor>
         <name>filterFanoutProcessor</name>
         <rules>
             <query id="Yr3Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="3_YEAR"
             ]]></query>
             <query id="Yr2Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="2_YEAR"
             ]]></query>
             <query id="Yr1Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="1_YEAR"
             ]]></query>
         </rules>
     </processor>
     

     If you specify more than one query for an Oracle CQL processor as Example 9-7 shows, then, by default, all query results are output to the processor's out-bound channel (filteredStream in Figure 9-1). Optionally, in the component configuration source, you can use the channel element selector attribute to specify a space-delimited list of one or more Oracle CQL query names that may output their results to the channel as Example 9-8 shows. In this example, query results for query Yr3Sector and Yr2Sector are output to filteredStream but not query results for query Yr1Sector.

     Example 9-14 Using selector to Control Which Query Results are Output

     <channel>
         <name>filteredStream</name>
         <selector>Yr3Sector Yr2Sector</selector>
     </channel>
     

     Note:

     The selector attribute is only applicable if the up-stream node is an Oracle CQL processor. For more information, see Chapter 10, "Configuring Oracle CQL Processors".

   For more information, see wlevs_application_config.xsd schema file.

10. Select File > Save.

    The EPN Editor adds a configuration badge to the channel as Figure 9-2 shows. For more information, see Section 5.2.4, "Configuration Badging".

    Figure 9-4 Channel With Configuration Badge

    
    Description of "Figure 9-4 Channel With Configuration Badge"
    
    

9.2.3 How to Create a Channel Component Configuration File Manually

Although the Oracle CEP IDE for Eclipse is the most efficient and least error-prone way to create and a channel configuration file (see Section 9.2.1, "How to Configure a System-Timestamped Channel Using Oracle CEP IDE for Eclipse"), alternatively, you can also create and maintain a channel configuration file manually.

For simplicity, the following procedure assumes that you are going to configure all components of an application in a single XML file.

To create a channel component configuration file manually:

1. Create an EPN assembly file and add a wlevs:channel element for each channel in your application.

   Uniquely identify each wlevs:channel with the id attribute.

   See Section 1.4, "Creating the EPN Assembly File" for details.

2. Optionally, override the default channel assembly file configuration by adding additional wlevs:channel attributes and child elements:

   1. Add the appropriate wlevs:channel attributes.

      See Table D-9, "Attributes of the wlevs:channel Application Assembly Element".

   2. Add the appropriate wlevs:channel child elements.

      • Appendix D, "wlevs:application-timestamped"

      • Appendix D, "wlevs:instance-property"

      • Appendix D, "wlevs:listener"

      • Appendix D, "wlevs:property"

      • Appendix D, "wlevs:source"

3. Create an XML file using your favorite XML editor.You can name this XML file anything you want, provided it ends with the .xml extension.

   The root element of the configuration file is config, with namespace definitions shown in the next step.

4. For each channel in your application, add a channel child element of config.

   Uniquely identify each channel with the name child element. This name must be the same as the value of the id attribute in the channel element of the EPN assembly file that defines the event processing network of your application. This is how Oracle CEP knows to which particular channel component in the EPN assembly file this channel configuration applies. See Section 1.4, "Creating the EPN Assembly File" for details.

   For example, if your application has two streams, the configuration file might initially look like:

   <?xml version="1.0" encoding="UTF-8"?>
   <n1:config xmlns:n1="http://www.bea.com/ns/wlevs/config/application"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <helloworld:config
     xmlns:helloworld="http://www.bea.com/xml/ns/wlevs/example/helloworld">
     <processor>
      ...
     </processor>
     <channel>
       <name>firstStream</name>
       ...
     </channel>
     <channel>
       <name>secondStream</name>
       ...
     </channel>
   </helloworld:config>
   

   In the example, the configuration file includes two channels called firstStream and secondStream. This means that the EPN assembly file must include at least two channel registrations with the same identifiers:

   <wlevs:channel id="firstStream" ...>
     ...
   </wlevs:channel>
   <wlevs:channel id="secondStream" ...>
     ...
   </wlevs:channel>
   

   Caution:

   Identifiers and names in XML files are case sensitive, so be sure you specify the same case when referencing the component's identifier in the EPN assembly file.

5. Optionally, override the default channel configuration by adding additional channel child elements:

   • Add a max-threads child element to specify the maximum number of threads that Oracle CEP server uses to process events for this channel.

     Setting this value has no effect when max-size is 0. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-threads>2</size>
     </channel>
     

     When set to 0, the channel acts as a pass-through. When max-threads > 0, the channel acts as classic blocking queue, where upstream components are producers of events and the downstream components are the consumers of events. The queue size is defined by the configuration max-size. There will be up to max-threads number of threads consuming events from the queue.

   • Add a max-size child element to specify the maximum size of the channel.

     Zero-size channels synchronously pass-through events.

     Non-zero size channels process events asynchronously, buffering events by the requested size. The default value is 0.

     <channel>
         <name>priceStream</name>
         <max-size>10000</size>
     </channel>
     

   • Add a heartbeat-timeout child element to specify the number of nanoseconds a channel can be idle before Oracle CEP generates a heartbeat event to advance time.

     The heartbeat child element applies to system-timestamped relations or streams only when no events arrive in the event channels that are feeding the processors and the processor has been configured with a statement that includes some temporal operator, such as a time-based window or a pattern matching with duration.

     <channel>
         <name>MatchOutputChannel</name>
         <heartbeat-timeout>10000</heartbeat-timeout>
     </channel>
     

   • Add a selector child element to specify which up-stream Oracle CQL processor queries are permitted to output their results to the channel.

     Figure 9-1 shows an EPN with channel filteredStream connected to an up-stream Oracle CQL processor filteredFanoutProcessor.

     Figure 9-5 EPN With Oracle CQL Processor and Down-Stream Channel

     
     Description of "Figure 9-5 EPN With Oracle CQL Processor and Down-Stream Channel"
     
     

     Example 9-7 shows the queries configured for the Oracle CQL processor.

     Example 9-15 filterFanoutProcessor Oracle CQL Queries

     <processor>
         <name>filterFanoutProcessor</name>
         <rules>
             <query id="Yr3Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="3_YEAR"
             ]]></query>
             <query id="Yr2Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="2_YEAR"
             ]]></query>
             <query id="Yr1Sector"><![CDATA[ 
                 select cusip, bid, srcId, bidQty, ask, askQty, seq 
                 from priceStream where sector="1_YEAR"
             ]]></query>
         </rules>
     </processor>
     

     If you specify more than one query for an Oracle CQL processor as Example 9-7 shows, then, by default, all query results are output to the processor's out-bound channel (filteredStream in Figure 9-1). Optionally, in the component configuration source, you can use the channel element selector attribute to specify a space-delimited list of one or more Oracle CQL query names that may output their results to the channel as Example 9-8 shows. In this example, query results for query Yr3Sector and Yr2Sector are output to filteredStream but not query results for query Yr1Sector.

     Example 9-16 Using selector to Control Which Query Results are Output

     <channel>
         <name>filteredStream</name>
         <selector>Yr3Sector Yr2Sector</selector>
     </channel>
     

     Note:

     The selector attribute is only applicable if the up-stream node is an Oracle CQL processor. For more information, see Chapter 10, "Configuring Oracle CQL Processors".

   For more information, Section B.1, "Component Configuration Schema wlevs_application_config.xsd".

6. Save and close the configuration file.

9.3.1 Channel Component Configuration File

Example 9-17 shows a sample component configuration file that configures the two channels shown in Figure 9-6.

<?xml version="1.0" encoding="UTF-8"?>
<n1:config xmlns:n1="http://www.bea.com/ns/wlevs/config/application"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <processor>
        <name>filterFanoutProcessor</name>
        <rules>
            <query id="Yr3Sector"><![CDATA[ 
                select cusip, bid, srcId, bidQty, ask, askQty, seq 
                from priceStream where sector="3_YEAR"
            ]]></query>
        </rules>
    </processor>
    <channel>
        <name>priceStream</name>
        <max-size>10000</max-size>
        <max-threads>4</max-threads>
    </channel>
    <channel>
        <name>filteredStream</name>
        <max-size>5000</max-size>
        <max-threads>2</max-threads>
    </channel>
</n1:config>

9.3.2 Channel EPN Assembly File

Example 9-18 shows a EPN assembly file that configures the two channels shown in Figure 9-6.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:osgi="http://www.springframework.org/schema/osgi"
    xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
    xmlns:cqlx="http://www.oracle.com/schema/cqlx"
    xsi:schemaLocation="
  http://www.springframework.org/schema/beans
  http://www.springframework.org/schema/beans/spring-beans.xsd
  http://www.springframework.org/schema/osgi
  http://www.springframework.org/schema/osgi/spring-osgi.xsd
  http://www.bea.com/ns/wlevs/spring
  http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_0_0_0.xsd">
 
    <wlevs:event-type-repository>
        <wlevs:event-type type-name="PriceEvent">
            <wlevs:properties>
                <wlevs:property name="cusip" type="java.lang.String" />
                <wlevs:property name="bid" type="java.lang.Double" />
                <wlevs:property name="srcId" type="java.lang.String" />
                <wlevs:property name="bidQty" type="java.lang.Integer" />
                <wlevs:property name="ask" type="java.lang.Double" />
                <wlevs:property name="askQty" type="java.lang.Integer" />
                <wlevs:property name="seq" type="java.lang.Long" />
                <wlevs:property name="sector" type="java.lang.String" />
            </wlevs:properties>
        </wlevs:event-type>
        <wlevs:event-type type-name="FilteredPriceEvent">
            <wlevs:properties>
                <wlevs:property name="cusip" type="java.lang.String" />
                <wlevs:property name="bid" type="java.lang.Double" />
                <wlevs:property name="srcId" type="java.lang.String" />
                <wlevs:property name="bidQty" type="java.lang.Integer" />
                <wlevs:property name="ask" type="java.lang.Double" />
                <wlevs:property name="askQty" type="java.lang.Integer" />
                <wlevs:property name="seq" type="java.lang.Long" />
            </wlevs:properties>
        </wlevs:event-type>
        <wlevs:event-type type-name="BidAskEvent">
            <wlevs:properties>
                <wlevs:property name="cusip" type="java.lang.String" />
                <wlevs:property name="bidseq" type="java.lang.Long" />
                <wlevs:property name="bidSrcId" type="java.lang.String" />
                <wlevs:property name="bid" type="java.lang.Double" />
                <wlevs:property name="askseq" type="java.lang.Long" />
                <wlevs:property name="askSrcId" type="java.lang.String" />
                <wlevs:property name="ask" type="java.lang.Double" />
                <wlevs:property name="bidQty" type="java.lang.Integer" />
                <wlevs:property name="askQty" type="java.lang.Integer" />
                <wlevs:property name="intermediateStrategy" type="java.lang.String" />
                <wlevs:property name="correlationId" type="java.lang.Long" />
                <wlevs:property name="priority" type="java.lang.Integer" />
            </wlevs:properties>
        </wlevs:event-type>
        <wlevs:event-type type-name="FinalOrderEvent">
            <wlevs:properties>
                <wlevs:property name="cusip" type="java.lang.String" />
                <wlevs:property name="bidseq" type="java.lang.Long" />
                <wlevs:property name="bidSrcId" type="java.lang.String" />
                <wlevs:property name="bid" type="java.lang.Double" />
                <wlevs:property name="bidQty" type="java.lang.Integer" />
                <wlevs:property name="bidSourceStrategy" type="java.lang.String" />
                <wlevs:property name="askseq" type="java.lang.Long" />
                <wlevs:property name="askSrcId" type="java.lang.String" />
                <wlevs:property name="ask" type="java.lang.Double" />
                <wlevs:property name="askQty" type="java.lang.Integer" />
                <wlevs:property name="askSourceStrategy" type="java.lang.String" />
                <wlevs:property name="correlationId" type="java.lang.Long" />
            </wlevs:properties>
        </wlevs:event-type>
    </wlevs:event-type-repository>
 
    <!-- Assemble EPN (event processing network) -->
    <wlevs:adapter advertise="true" id="PriceAdapter"
        provider="csvgen">
        <wlevs:instance-property name="port" value="9008" />
        <wlevs:instance-property name="eventTypeName"
            value="PriceEvent" />
        <wlevs:instance-property name="eventPropertyNames"
            value="srcId,sector,cusip,bid,ask,bidQty,askQty,seq" />
    </wlevs:adapter>
 
    <wlevs:channel id="priceStream" event-type="PriceEvent">
        <wlevs:listener ref="filterFanoutProcessor" />
        <wlevs:source ref="PriceAdapter" />
    </wlevs:channel>
 
    <!-- By default, CQL is used for OCEP 11.0 -->
    <wlevs:processor id="filterFanoutProcessor" >
    </wlevs:processor>
 
    <wlevs:channel id="filteredStream"
        event-type="FilteredPriceEvent">
        <wlevs:listener ref="bbaProcessor" />
        <wlevs:listener ref="analyticsProcessor" />
        <wlevs:source ref="filterFanoutProcessor" />
    </wlevs:channel>
 
    <!-- Explicitly specify provider CQL -->
    <wlevs:processor id="bbaProcessor" provider="cql">
        <wlevs:listener ref="bidAskBBAStream" />
    </wlevs:processor>
 
    <wlevs:processor id="analyticsProcessor">
        <wlevs:listener ref="bidAskAnalyticsStream" />
    </wlevs:processor>
 
    <wlevs:channel id="bidAskBBAStream" event-type="BidAskEvent">
        <wlevs:listener ref="selectorProcessor" />
    </wlevs:channel>
    
    <wlevs:channel id="bidAskAnalyticsStream" event-type="BidAskEvent">
        <wlevs:listener ref="selectorProcessor" />
    </wlevs:channel>
 
    <wlevs:processor id="selectorProcessor">
        <wlevs:listener ref="citipocOut" />
    </wlevs:processor>
 
    <wlevs:channel id="citipocOut" event-type="FinalOrderEvent" advertise="true">
        <wlevs:listener>
            <!-- Create business object -->
            <bean id="outputBean"
                class="com.bea.wlevs.POC.citi.OutputBean"
                autowire="byName" />
        </wlevs:listener>
    </wlevs:channel>
</beans>