17 Configuring High Availability

17.1.1 How to Configure Simple Failover

You configure simple failover using the Oracle CEP sliding window output adapter with a sliding window size of zero (0).

This procedure starts with the example EPN that Figure 17-1 shows and adds the required components to configure it for simple failover. Example 17-1 shows the corresponding EPN assembly file and Example 17-2 shows the corresponding component configuration file.

For more information about this Oracle CEP high availability quality of service, see Section 16.2.1, "Simple Failover".

Figure 17-1 Simple Failover EPN

Description of "Figure 17-1 Simple Failover EPN"

<?xml version="1.0" encoding="UTF-8"?>
<beans ...>

    <wlevs:event-type-repository>
        <wlevs:event-type type-name="HelloWorldEvent">
            <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
        </wlevs:event-type>
    </wlevs:event-type-repository>

    <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
        <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
    </wlevs:adapter>

    <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
        <wlevs:listener ref="helloworldProcessor"/>
        <wlevs:source ref="helloworldAdapter"/>
    </wlevs:channel>

    <wlevs:processor id="helloworldProcessor" />
    
    <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
        <wlevs:listener>
            <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
        </wlevs:listener>
        <wlevs:source ref="helloworldProcessor"/>
    </wlevs:channel>

</beans>

<?xml version="1.0" encoding="UTF-8"?>
<wlevs:config 
        xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
        xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
    <processor>
        <name>helloworldProcessor</name>
        <rules>
            <query id="helloworldRule">
                <![CDATA[ select * from helloworldInputChannel [Now] ]]>
            </query>
        </rules>
    </processor>
</wlevs:config>

To configure simple failover:

1. Create a multi-server domain using Oracle Coherence.

   For more information, see:

   • "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

   • "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

2. Create an Oracle CEP application.

   For more information, see Section 3.2, "Creating Oracle CEP Projects".

3. Edit the MANIFEST.MF file to add the following Import-Package entries:

   • com.bea.wlevs.ede.api.cluster

   • com.oracle.cep.cluster.hagroups

   • com.oracle.cep.cluster.ha.adapter

   • com.oracle.cep.cluster.ha.api

   For more information, see Section 3.7.2, "How to Add an OSGi Bundle to an Oracle CEP Project".

4. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability sliding window output adapter as Example 17-3 shows.

   • Add a wlevs:adapter element with provider set to ha-buffered after channel helloworldOutputChannel.

   • Update the wlevs:listener element in channel helloworldOutputChannel to reference the ha-buffered adapter by its id.

   • Add a wlevs:listener element to the ha-buffered adapter that references the HelloWorldBean class.

   Example 17-3 Simple Failover EPN Assembly File: Sliding Window Output Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="HelloWorldEvent">
               <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
           <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
       </wlevs:adapter>
   
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
       </wlevs:channel>
   
       <wlevs:processor id="helloworldProcessor" />
   
       <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
           <wlevs:listener ref="myHaSlidingWindowAdapter"/>
           <wlevs:source ref="helloworldProcessor"/>
       </wlevs:channel>
   
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
       </wlevs:adapter>
   
   </beans>
   

5. Optionally, configure the channel downstream from the input adapter (helloworldInputChannel) to configure an application timestamp based on an appropriate event property as Example 17-4 shows.

   For simple failover, you can use system timestamps because events are not correlated between servers. However, it is possible that slightly different results might be output from the buffer if application timestamps are not used.

   In this example, event property arrivalTime is used.

   The wlevs:expression should be set to this event property.

   Example 17-4 Application Timestamp Configuration

   ...
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
           <wlevs:source ref="myHaInputAdapter"/>
           <wlevs:application-timestamped>
               <wlevs:expression>arrivalTime</wlevs:expression>
           </wlevs:application-timestamped>
       </wlevs:channel>
   ...
   

6. Configure the Oracle CEP high availability sliding window output adapter.

   Set the instance property windowLength to zero (0) as Example 17-5 shows.

   Example 17-5 Configuring windowLength in the Sliding Window Output Adapter

   ...
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
           <wlevs:instance-property name="windowLength" value="0"/>
       </wlevs:adapter>
   ...
   

   For more information, see Section 17.2.2.1, "Sliding Window Output Adapter EPN Assembly File Configuration".

7. Optionally, configure the component configuration file to include the Oracle CEP high availability sliding window output adapter as Example 17-6 shows.

   Example 17-6 Simple Failover Component Configuration File With High Availability Adapters

   <?xml version="1.0" encoding="UTF-8"?>
   <wlevs:config 
           xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
           xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
       <processor>
           <name>helloworldProcessor</name>
           <rules>
               <query id="helloworldRule">
                   <![CDATA[ select * from helloworldInputChannel [Now] ]]>
               </query>
           </rules>
       </processor>
   
       <ha:ha-buffered-adapter>
           <name>myHaSlidingWindowAdapter</name>
           <window-length>0</window-length>
       </ha:ha-buffered-adapter>
   
   </wlevs:config>
   

   For more information, see:

   • Section 17.2.2.2, "Sliding Window Adapter Component Configuration File Configuration"

8. Deploy your application to the deployment group you created in step 1.

   For more information, see Section 20.4, "Deploying Oracle CEP Applications".

   Oracle CEP automatically selects one of the Oracle CEP servers as the primary.

17.1.2 How to Configure Simple Failover With Buffering

You configure simple failover using the Oracle CEP sliding window output adapter with a sliding window size greater than zero (0).

This procedure starts with the example EPN that Figure 17-2 shows and adds the required components to configure it for simple failover with buffering. Example 17-7 shows the corresponding EPN assembly file and Example 17-8 shows the corresponding component configuration file.

For more information about this Oracle CEP high availability quality of service, see Section 16.2.2, "Simple Failover with Buffering".

Figure 17-2 Simple Failover With Buffering EPN

Description of "Figure 17-2 Simple Failover With Buffering EPN"

<?xml version="1.0" encoding="UTF-8"?>
<beans ...>

    <wlevs:event-type-repository>
        <wlevs:event-type type-name="HelloWorldEvent">
            <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
        </wlevs:event-type>
    </wlevs:event-type-repository>

    <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
        <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
    </wlevs:adapter>

    <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
        <wlevs:listener ref="helloworldProcessor"/>
        <wlevs:source ref="helloworldAdapter"/>
    </wlevs:channel>

    <wlevs:processor id="helloworldProcessor" />
    
    <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
        <wlevs:listener>
            <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
        </wlevs:listener>
        <wlevs:source ref="helloworldProcessor"/>
    </wlevs:channel>

</beans>

<?xml version="1.0" encoding="UTF-8"?>
<wlevs:config 
        xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
        xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
    <processor>
        <name>helloworldProcessor</name>
        <rules>
            <query id="helloworldRule">
                <![CDATA[ select * from helloworldInputChannel [Now] ]]>
            </query>
        </rules>
    </processor>
</wlevs:config>

To configure simple failover with buffering:

1. Create a multi-server domain using Oracle Coherence.

   For more information, see:

   • "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

   • "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

2. Create an Oracle CEP application.

   For more information, see Section 3.2, "Creating Oracle CEP Projects".

3. Edit the MANIFEST.MF file to add the following Import-Package entries:

   • com.bea.wlevs.ede.api.cluster

   • com.oracle.cep.cluster.hagroups

   • com.oracle.cep.cluster.ha.adapter

   • com.oracle.cep.cluster.ha.api

   For more information, see Section 3.7.2, "How to Add an OSGi Bundle to an Oracle CEP Project".

4. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability sliding window output adapter as Example 17-3 shows.

   • Add a wlevs:adapter element with provider set to ha-buffered after channel helloworldOutputChannel.

   • Update the wlevs:listener element in channel helloworldOutputChannel to reference the ha-buffered adapter by its id.

   • Add a wlevs:listener element to the ha-buffered adapter that references the HelloWorldBean class.

   Example 17-9 Simple Failover EPN Assembly File: Sliding Window Output Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="HelloWorldEvent">
               <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
           <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
       </wlevs:adapter>
   
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
       </wlevs:channel>
   
       <wlevs:processor id="helloworldProcessor" />
   
       <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
           <wlevs:listener ref="myHaSlidingWindowAdapter"/>
           <wlevs:source ref="helloworldProcessor"/>
       </wlevs:channel>
   
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
       </wlevs:adapter>
   
   </beans>
   

5. Optionally, configure the channel downstream from the input adapter (helloworldInputChannel) to configure an application timestamp based on an appropriate event property as Example 17-10 shows.

   For simple failover with buffering, you can use system timestamps because events are not correlated between servers. However, it is possible that slightly different results might be output from the buffer if application timestamps are not used.

   In this example, event property arrivalTime is used.

   The wlevs:expression should be set to this event property.

   Example 17-10 Application Timestamp Configuration

   ...
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
           <wlevs:source ref="myHaInputAdapter"/>
           <wlevs:application-timestamped>            <wlevs:expression>arrivalTime</wlevs:expression>
           </wlevs:application-timestamped>
       </wlevs:channel>
   ...
   

6. Configure the Oracle CEP high availability sliding window output adapter.

   Set the instance property windowLength to a value greater than zero (0) as Example 17-11 shows.

   Example 17-11 Configuring windowLength in the Sliding Window Output Adapter

   ...
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
           <wlevs:instance-property name="windowLength" value="15000"/>
       </wlevs:adapter>
   ...
   

   For more information, see Section 17.2.2.1, "Sliding Window Output Adapter EPN Assembly File Configuration".

7. Optionally, configure the component configuration file to include the Oracle CEP high availability sliding window output adapter as Example 17-12 shows.

   Example 17-12 Simple Failover With Buffering Component Configuration File

   <?xml version="1.0" encoding="UTF-8"?>
   <wlevs:config 
           xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
           xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
       <processor>
           <name>helloworldProcessor</name>
           <rules>
               <query id="helloworldRule">
                   <![CDATA[ select * from helloworldInputChannel [Now] ]]>
               </query>
           </rules>
       </processor>
   
       <ha:ha-buffered-adapter>
           <name>myHaSlidingWindowAdapter</name>
           <window-length>15000</window-length>
       </ha:ha-buffered-adapter>
   
   </wlevs:config>
   

   For more information, see:

   • Section 17.2.2.2, "Sliding Window Adapter Component Configuration File Configuration"

8. If your application is an Oracle CEP high availability Type 1 application (the application must generate exactly the same sequence of output events as existing secondaries), configure the warm-up-window-length for the sliding window output adapter.

   For more information, see:

   • Section 16.3.2.5, "Choose an Adequate warm-up-window Time"

   • Section 17.2.2.2, "Sliding Window Adapter Component Configuration File Configuration"

9. Deploy your application to the deployment group you created in step 1.

   For more information, see Section 20.4, "Deploying Oracle CEP Applications".

   Oracle CEP automatically selects one of the Oracle CEP servers as the primary.

17.1.3 How to Configure Light-Weight Queue Trimming

You configure light-weight queue trimming using the Oracle CEP high availability input adapter and the broadcast output adapter.

This procedure starts with the example EPN that Figure 17-3 shows and adds the required components to configure it for light-weight queue trimming. Example 17-13 shows the corresponding EPN assembly file and Example 17-14 shows the corresponding component configuration file.

For more information about this Oracle CEP high availability quality of service, see Section 16.2.3, "Light-Weight Queue Trimming".

Figure 17-3 Light-Weight Queue Trimming EPN

Description of "Figure 17-3 Light-Weight Queue Trimming EPN"

<?xml version="1.0" encoding="UTF-8"?>
<beans ...>

    <wlevs:event-type-repository>
        <wlevs:event-type type-name="HelloWorldEvent">
            <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
        </wlevs:event-type>
    </wlevs:event-type-repository>

    <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
        <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
    </wlevs:adapter>

    <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
        <wlevs:listener ref="helloworldProcessor"/>
        <wlevs:source ref="helloworldAdapter"/>
    </wlevs:channel>

    <wlevs:processor id="helloworldProcessor" />
    
    <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
        <wlevs:listener>
            <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
        </wlevs:listener>
        <wlevs:source ref="helloworldProcessor"/>
    </wlevs:channel>

</beans>

<?xml version="1.0" encoding="UTF-8"?>
<wlevs:config 
        xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
        xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
    <processor>
        <name>helloworldProcessor</name>
        <rules>
            <query id="helloworldRule">
                <![CDATA[ select * from helloworldInputChannel [Now] ]]>
            </query>
        </rules>
    </processor>
</wlevs:config>

To configure light-weight queue trimming:

1. Create a multi-server domain using Oracle Coherence.

   For more information, see:

   • "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

   • "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

2. Create an Oracle CEP application.

   For more information, see Section 3.2, "Creating Oracle CEP Projects".

3. Edit the MANIFEST.MF file to add the following Import-Package entries:

   • com.bea.wlevs.ede.api.cluster

   • com.oracle.cep.cluster.hagroups

   • com.oracle.cep.cluster.ha.adapter

   • com.oracle.cep.cluster.ha.api

   For more information, see Section 3.7.2, "How to Add an OSGi Bundle to an Oracle CEP Project".

4. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability input adapter as Example 17-15 shows:

   • Add a wlevs:adapter element with provider set to ha-inbound after the regular input adapter helloworldAdapter.

   • Add a wlevs:listener element to the regular input adapter helloworldAdapter that references the ha-inbound adapter by its id.

   • Add a wlevs:source element to the helloworldInputChannel that references the ha-inbound adapter by its id.

   Example 17-15 Light-Weight Queue Trimming EPN Assembly File: High Availability Input Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="HelloWorldEvent">
               <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
           <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
           <wlevs:listener ref="myHaInputAdapter"/>
       </wlevs:adapter>
   
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
       </wlevs:adapter>
   
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
           <wlevs:source ref="myHaInputAdapter"/>
       </wlevs:channel>
   
       <wlevs:processor id="helloworldProcessor" />
   
       <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
           <wlevs:source ref="helloworldProcessor"/>
       </wlevs:channel>
   
   </beans>
   

5. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability broadcast output adapter as Example 17-16 shows.

   • Add a wlevs:adapter element with provider set to ha-broadcast after channel helloworldOutputChannel.

   • Update the wlevs:listener element in channel helloworldOutputChannel to reference the ha-broadcast adapter by its id.

   • Add a wlevs:listener element to the ha-broadcast adapter that references the HelloWorldBean class.

   Example 17-16 Light-Weight Queue Trimming EPN Assembly File: Broadcast Output Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="HelloWorldEvent">
               <wlevs:class>com.bea.wlevs.event.example.helloworld.HelloWorldEvent</wlevs:class>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="helloworldAdapter" class="com.bea.wlevs.adapter.example.helloworld.HelloWorldAdapter" >
           <wlevs:instance-property name="message" value="HelloWorld - the current time is:"/>
           <wlevs:listener ref="myHaInputAdapter"/>
       </wlevs:adapter>
   
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
       </wlevs:adapter>
   
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
           <wlevs:source ref="myHaInputAdapter"/>
       </wlevs:channel>
   
       <wlevs:processor id="helloworldProcessor" />
   
       <wlevs:channel id="helloworldOutputChannel" event-type="HelloWorldEvent" advertise="true">
           <wlevs:listener ref="myHaBroadcastAdapter"/>
           <wlevs:source ref="helloworldProcessor"/>
       </wlevs:channel>
   
       <wlevs:adapter id="myHaBroadcastAdapter" provider="ha-broadcast" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
       </wlevs:adapter>
   
   </beans>
   

6. Configure the Oracle CEP high availability input adapter.

   Consider the following example configurations:

   • Example 17-17, "High Availability Input Adapter: Default Configuration"

   • Example 17-18, "High Availability Input Adapter: Tuple Events"

   • Example 17-19, "High Availability Input Adapter: Key of One Event Property"

   • Example 17-20, "High Availability Input Adapter: Key of Multiple Event Properties"

   For more information, see Section 17.2.1.1, "High Availability Input Adapter EPN Assembly File Configuration".

   Example 17-17 High Availability Input Adapter: Default Configuration

   This example shows a high availability input adapter configuration using all defaults. The mandatory key is based on all event properties and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
       </wlevs:adapter>
   ...
   

   Example 17-18 High Availability Input Adapter: Tuple Events

   This example shows a high availability input adapter configuration using all defaults. The mandatory key is based on all event properties and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime. Because the events are tuple-based events, you must specify the event type (MyEventType) using the eventType property.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
           <wlevs:instance-property name="eventType" value="MyEventType"/>
       </wlevs:adapter>
   ...
   

   Example 17-19 High Availability Input Adapter: Key of One Event Property

   This example shows a high availability input adapter configuration where the mandatory key is based on one event property (named id) and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="keyProperties" value="id"/>
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
       </wlevs:adapter>
   ...
   

   Example 17-20 High Availability Input Adapter: Key of Multiple Event Properties

   This example shows a high availability input adapter configuration where the mandatory key is based on more than one event property (properties orderID and accountID) and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime. A compound key Java class (com.acme.MyCompoundKeyClass) is mandatory and its implementation is shown in Example 17-21. The hashCode and equals methods are required. When you specify a keyClass, the keyProperties instance property is ignored: Oracle CEP assumes that the compound key is based on all the getter methods in the keyClass.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
           <wlevs:instance-property name="keyClass" value="com.acme.MyCompoundKeyClass"/>
       </wlevs:adapter>
   ...
   

   Example 17-21 MyCompoundKeyClass Implementation

   package com.acme;
   
   public class MyCompoundKeyClass {
       private int orderID;
       private int accountID;
   
       public MyCompoundKeyClass() {}
   
       public int getOrderID() {
           return orderID;
       }
       public setOrderID(int orderID) {
           this.orderID = orderID;
       }
       public int getAccountID() {
           return accountID;
       }
       public setOrderID(int accountID) {
           this.accountID = accountID;
       }
   
       public int hashCode() {
       int hash = 1;
       hash = hash * 31 + orderID.hashCode();
       hash = hash * 31 + (accountID == null ? 0 : accountID.hashCode());
       return hash;
       }
   
       public boolean equals(Object obj) {
           if (obj == this) return true;
           if (obj == null) return false;
           if (!(obj instanceof MyCompoundKeyClass)) return false;
           MyCompoundKeyClass k = (MyCompoundKeyClass) obj;
           return k.accountID == accountID && k.orderID == orderID;
       }
   }
   

7. Configure the channel downstream from the high availability input adapter (helloworldInputChannel) to configure an application timestamp based on the high availability input adapter timeProperty setting as Example 17-22 shows.

   The wlevs:expression should be set to the timeProperty value.

   Example 17-22 Application Timestamp Configuration

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="keyProperties" value="id"/>
           <wlevs:instance-property name="eventType" value="HelloWorldEvent"/>
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
       </wlevs:adapter>
   
       <wlevs:channel id="helloworldInputChannel" event-type="HelloWorldEvent" >
           <wlevs:listener ref="helloworldProcessor"/>
           <wlevs:source ref="myHaInputAdapter"/>
           <wlevs:application-timestamped>            <wlevs:expression>arrivalTime</wlevs:expression>
           </wlevs:application-timestamped>
       </wlevs:channel>
   ...
   

8. Configure the Oracle CEP high availability broadcast output adapter.

   Consider the following example configurations:

   • Example 17-23, "Broadcast Output Adapter: Default Configuration"

   • Example 17-24, "Broadcast Output Adapter: Key of One Event Property"

   • Example 17-25, "Broadcast Output Adapter: Key of Multiple Event Properties"

   For more information, see Section 17.2.3.1, "Broadcast Output Adapter EPN Assembly File Configuration".

   Example 17-23 Broadcast Output Adapter: Default Configuration

   This example shows a broadcast output adapter configuration using all defaults. The mandatory key is based on all event properties, key values are nonmonotonic (do not increase continually) and total order (unique).

   ...
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
       </wlevs:adapter>
   ...
   

   Example 17-24 Broadcast Output Adapter: Key of One Event Property

   This example shows a broadcast output adapter configuration where the mandatory key is based on one event property (named timeProperty), key values are monotonic (they do increase continually) and not total order (not unique).

   ...
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
           <wlevs:instance-property name="keyProperties" value="timeProperty"/>
           <wlevs:instance-property name="monotonic" value="true"/>
           <wlevs:instance-property name="total-order" value="false"/>
       </wlevs:adapter>
   ...
   

   Example 17-25 Broadcast Output Adapter: Key of Multiple Event Properties

   This example shows a broadcast output adapter configuration where the mandatory key is based on more than one event property (properties timeProperty and accountID), key values are monotonic (they do increase continually) and total order (unique). A compound key Java class (com.acme.MyCompoundKeyClass) is mandatory and its implementation is shown in Example 17-26. The hashCode and equals methods are required. When you specify a keyClass, the keyProperties instance property is ignored: Oracle CEP assumes that the compound key is based on all the getter methods in the keyClass.

   ...
       <wlevs:adapter id="myHaSlidingWindowAdapter" provider="ha-buffered" >
           <wlevs:listener>
               <bean class="com.bea.wlevs.example.helloworld.HelloWorldBean"/>
           </wlevs:listener>
           <wlevs:instance-property name="keyClass" value="com.acme.MyCompoundKeyClass"/>
           <wlevs:instance-property name="monotonic" value="true"/>
           <wlevs:instance-property name="total-order" value="true"/>
       </wlevs:adapter>
   ...
   

   Example 17-26 MyCompoundKeyClass Implementation

   package com.acme;
   
   public class MyCompoundKeyClass {
       private int timeProperty;
       private int accountID;
   
       public MyCompoundKeyClass() {}
   
       public int getTimeProperty() {
           return orderID;
       }
       public setTimeProperty(int timeProperty) {
           this.timeProperty = timeProperty;
       }
       public int getAccountID() {
           return accountID;
       }
       public setOrderID(int accountID) {
           this.accountID = accountID;
       }
   
       public int hashCode() {
       int hash = 1;
       hash = hash * 31 + timeProperty.hashCode();
       hash = hash * 31 + (accountID == null ? 0 : accountID.hashCode());
       return hash;
       }
   
       public boolean equals(Object obj) {
           if (obj == this) return true;
           if (obj == null) return false;
           if (!(obj instanceof MyCompoundKeyClass)) return false;
           MyCompoundKeyClass k = (MyCompoundKeyClass) obj;
           return k.accountID == accountID && k.orderID == orderID;
       }
   }
   

9. Optionally, configure the component configuration file to include the Oracle CEP high availability input adapter and sliding window output adapter as Example 17-27 shows.

   Example 17-27 Light-Weight Queue Trimming Component Configuration File

   <?xml version="1.0" encoding="UTF-8"?>
   <wlevs:config 
           xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
           xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
       <processor>
           <name>helloworldProcessor</name>
           <rules>
               <query id="helloworldRule">
                   <![CDATA[ select * from helloworldInputChannel [Now] ]]>
               </query>
           </rules>
       </processor>
   
       <ha:ha-inbound-adapter>
           <name>myHaInputAdapter</name>
       </ha:ha-inbound-adapter>
    
       <ha:ha-broadcast-adapter>
           <name>myHaBroadcastAdapter</name>
           <trimming-interval units="events">10</trimming-interval>
       </ha:ha-broadcast-adapter>
   
   </wlevs:config>
   

   For more information, see:

   • Section 17.2.1.2, "High Availability Input Adapter Component Configuration File Configuration"

   • Section 17.2.3.2, "Broadcast Output Adapter Component Configuration File Configuration"

10. If your application is an Oracle CEP high availability Type 1 application (the application must generate exactly the same sequence of output events as existing secondaries), configure the warm-up-window-length for the broadcast output adapter.

    For more information, see:

    • Section 16.3.2.5, "Choose an Adequate warm-up-window Time"

    • Section 17.2.3.2, "Broadcast Output Adapter Component Configuration File Configuration"

11. Deploy your application to the deployment group you created in step 1.

    For more information, see Section 20.4, "Deploying Oracle CEP Applications".

    Oracle CEP automatically selects one of the Oracle CEP servers as the primary.

17.1.4 How to Configure Precise Recovery With JMS

You configure precise recovery with JMS using the Oracle CEP high availability input adapter and correlating output adapter.

This procedure describes how to create the example EPN that Figure 17-4 shows. Example 17-28 shows the corresponding EPN assembly file and Example 17-29 shows the corresponding component configuration file.

For more information about this Oracle CEP high availability quality of service, see Section 16.2.4, "Precise Recovery with JMS".

Figure 17-4 Precise Recovery With JMS EPN

Description of "Figure 17-4 Precise Recovery With JMS EPN"

<?xml version="1.0" encoding="UTF-8"?>
<beans ... >

    <wlevs:event-type-repository>
        <wlevs:event-type type-name="StockTick">
            <wlevs:properties>
                <wlevs:property name="lastPrice" type="double" />
                <wlevs:property name="symbol" type="char" />
            </wlevs:properties>
        </wlevs:event-type>
    </wlevs:event-type-repository>

    <wlevs:adapter id="JMSInboundAdapter" provider="jms-inbound">
        <wlevs:listener ref="myHaInputAdapter"/>
    </wlevs:adapter>

    <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
        <wlevs:instance-property name="keyProperties" value="sequenceNo"/>
        <wlevs:instance-property name="timeProperty" value="inboundTime"/>
    </wlevs:adapter>

    <wlevs:channel id="channel1" event-type="StockTick">
        <wlevs:listener ref="processor1" />
        <wlevs:source ref="myHaInputAdapter"/>
        <wlevs:application-timestamped>
            <wlevs:expression>inboundTime</wlevs:expression>
        </wlevs:application-timestamped>
    </wlevs:channel>

    <wlevs:processor id="processor1">
        <wlevs:listener ref="channel2" />
    </wlevs:processor>

    <wlevs:adapter id="myHaCorrelatingAdapter" provider="ha-correlating" >
        <wlevs:instance-property name="correlatedSource" ref="clusterCorrelatingOutstream"/> 
        <wlevs:instance-property name="failOverDelay" value="2000"/> 
        <wlevs:listener ref="JMSOutboundAdapter"/>
    </wlevs:adapter>

    <wlevs:channel id="channel2" event-type="StockTick">
        <wlevs:listener ref="myHaCorrelatingAdapter" />
    </wlevs:channel>

    <wlevs:adapter id="JMSOutboundAdapter" provider="jms-outbound">
    </wlevs:adapter>

    <wlevs:adapter id="JMSInboundAdapter2" provider="jms-inbound">
    </wlevs:adapter>

    <wlevs:channel id="clusterCorrelatingOutstream" event-type="StockTick" advertise="true">
        <wlevs:source ref="JMSInboundAdapter2"/>
    </wlevs:channel> 
</beans>

<?xml version="1.0" encoding="UTF-8"?>
<wlevs:config 
        xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
        xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
    <processor>
        <name>processor1</name>
        <rules>
            <query id="helloworldRule">
                <![CDATA[ select * from channel1 [Now] ]]>
            </query>
        </rules>
    </processor>
</wlevs:config>

To configure precise recovery with JMS:

1. Create a multi-server domain using Oracle Coherence.

   For more information, see:

   • "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

   • "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence" in the Oracle CEP Administrator's Guide.

2. Create an Oracle CEP application.

   For more information, see Section 3.2, "Creating Oracle CEP Projects".

3. Edit the MANIFEST.MF file to add the following Import-Package entries:

   • com.bea.wlevs.ede.api.cluster

   • com.oracle.cep.cluster.hagroups

   • com.oracle.cep.cluster.ha.adapter

   • com.oracle.cep.cluster.ha.api

   For more information, see Section 3.7.2, "How to Add an OSGi Bundle to an Oracle CEP Project".

4. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability input adapter as Example 17-30 shows:

   • Add a wlevs:adapter element with provider set to ha-inbound after the regular input adapter JMSInboundAdapter.

   • Add a wlevs:listener element to the regular input adapter JMSInboundAdapter that references the ha-inbound adapter by its id.

   • Add a wlevs:source element to the channel channel1 that references the ha-inbound adapter by its id.

   Example 17-30 Precise Recovery With JMS EPN Assembly File: High Availability Input Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="StockTick">
               <wlevs:properties>
                   <wlevs:property name="lastPrice" type="double" />
                   <wlevs:property name="symbol" type="char" />
               </wlevs:properties>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="JMSInboundAdapter" provider="jms-inbound">
           <wlevs:listener ref="myHaInputAdapter"/>
       </wlevs:adapter>
   
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
       </wlevs:adapter>
   
       <wlevs:channel id="channel1" event-type="StockTick">
           <wlevs:listener ref="processor1" />
           <wlevs:source ref="myHaInputAdapter"/>
       </wlevs:channel>
   
   ...
   
   </beans>
   

5. Configure your Oracle CEP application EPN assembly file to add an Oracle CEP high availability correlating output adapter as Example 17-31 shows.

   • Add a wlevs:adapter element with provider set to ha-correlating after channel channel2.

   • Update the wlevs:listener element in channel channel2 to reference the ha-correlating adapter by its id.

   • Add a wlevs:listener element to the ha-correlating adapter that references the regular output adapter JMSOutboundAdapter.

   Example 17-31 Precise Recovery With JMS EPN Assembly File: Correlating Output Adapter

   <?xml version="1.0" encoding="UTF-8"?>
   <beans ...>
   
       <wlevs:event-type-repository>
           <wlevs:event-type type-name="StockTick">
               <wlevs:properties>
                   <wlevs:property name="lastPrice" type="double" />
                   <wlevs:property name="symbol" type="char" />
               </wlevs:properties>
           </wlevs:event-type>
       </wlevs:event-type-repository>
   
       <wlevs:adapter id="JMSInboundAdapter" provider="jms-inbound">
           <wlevs:listener ref="myHaInputAdapter"/>
       </wlevs:adapter>
   
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
       </wlevs:adapter>
   
       <wlevs:channel id="channel1" event-type="StockTick">
           <wlevs:listener ref="processor1" />
           <wlevs:source ref="myHaInputAdapter"/>
       </wlevs:channel>
   
       <wlevs:processor id="processor1">
           <wlevs:listener ref="channel2" />
       </wlevs:processor>
   
       <wlevs:channel id="channel2" event-type="StockTick">
           <wlevs:listener ref="myHaCorrelatingAdapter" />
       </wlevs:channel>
   
       <wlevs:adapter id="myHaCorrelatingAdapter" provider="ha-correlating" >
           <wlevs:listener ref="JMSOutboundAdapter"/>
       </wlevs:adapter>
   
       <wlevs:adapter id="JMSOutboundAdapter" provider="jms-outbound">
       </wlevs:adapter>
   
   ...
   
   </beans>
   

6. Configure the Oracle CEP high availability input adapter.

   Consider the following example configurations:

   • Example 17-32, "High Availability Input Adapter: Default Configuration"

   • Example 17-33, "High Availability Input Adapter: Tuple Events"

   • Example 17-34, "High Availability Input Adapter: Key of One Event Property"

   • Example 17-35, "High Availability Input Adapter: Key of Multiple Event Properties"

   For more information, see Section 17.2.1.1, "High Availability Input Adapter EPN Assembly File Configuration".

   Example 17-32 High Availability Input Adapter: Default Configuration

   This example shows a high availability input adapter configuration using all defaults. The mandatory key is based on all event properties and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
       </wlevs:adapter>
   ...
   

   Example 17-33 High Availability Input Adapter: Tuple Events

   This example shows a high availability input adapter configuration using all defaults. The mandatory key is based on all event properties and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime. Because the events are tuple-based events, you must specify the event type (MyEventType) using the eventType property.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
           <wlevs:instance-property name="eventType" value="MyEventType"/>
       </wlevs:adapter>
   ...
   

   Example 17-34 High Availability Input Adapter: Key of One Event Property

   This example shows a high availability input adapter configuration where the mandatory key is based on one event property (named sequenceNo) and the event property that the high availability input adapter assigns a time value to is an event property named inboundTime.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="keyProperties" value="sequenceNo"/>
           <wlevs:instance-property name="timeProperty" value="inboundTime"/>
       </wlevs:adapter>
   ...
   

   Example 17-35 High Availability Input Adapter: Key of Multiple Event Properties

   This example shows a high availability input adapter configuration where the mandatory key is based on more than one event property (properties orderID and accountID) and the event property that the high availability input adapter assigns a time value to is an event property named arrivalTime. A compound key Java class (com.acme.MyCompoundKeyClass) is mandatory and its implementation is shown in Example 17-36. The hashCode and equals methods are required. When you specify a keyClass, the keyProperties instance property is ignored: Oracle CEP assumes that the compound key is based on all the getter methods in the keyClass.

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
           <wlevs:instance-property name="keyClass" value="com.acme.MyCompoundKeyClass"/>
       </wlevs:adapter>
   ...
   

   Example 17-36 MyCompoundKeyClass Implementation

   package com.acme;
   
   public class MyCompoundKeyClass {
       private int orderID;
       private int accountID;
   
       public MyCompoundKeyClass() {}
   
       public int getOrderID() {
           return orderID;
       }
       public setOrderID(int orderID) {
           this.orderID = orderID;
       }
       public int getAccountID() {
           return accountID;
       }
       public setOrderID(int accountID) {
           this.accountID = accountID;
       }
   
       public int hashCode() {
       int hash = 1;
       hash = hash * 31 + orderID.hashCode();
       hash = hash * 31 + (accountID == null ? 0 : accountID.hashCode());
       return hash;
       }
   
       public boolean equals(Object obj) {
           if (obj == this) return true;
           if (obj == null) return false;
           if (!(obj instanceof MyCompoundKeyClass)) return false;
           MyCompoundKeyClass k = (MyCompoundKeyClass) obj;
           return k.accountID == accountID && k.orderID == orderID;
       }
   }
   

7. Configure the channel downstream from the high availability input adapter (channel1) to configure an application timestamp based on the high availability input adapter timeProperty setting as Example 17-37 shows.

   The wlevs:expression should be set to the timeProperty value.

   Example 17-37 Application Timestamp Configuration

   ...
       <wlevs:adapter id="myHaInputAdapter" provider="ha-inbound" >
           <wlevs:instance-property name="eventType" value="HelloWorldEvent"/>
           <wlevs:instance-property name="keyProperties" value="sequenceNo"/>
           <wlevs:instance-property name="timeProperty" value="inboundTime"/>
       </wlevs:adapter>
   
       <wlevs:channel id="channel1" event-type="StockTick">
           <wlevs:listener ref="processor1" />
           <wlevs:source ref="myHaInputAdapter"/>
           <wlevs:application-timestamped>
               <wlevs:expression>inboundTime</wlevs:expression>
           </wlevs:application-timestamped>
       </wlevs:channel>
   ...
   

8. Configure the Oracle CEP high availability correlating output adapter failOverDelay.

   Example 17-38 shows a correlating output adapter configuration where the failOverDelay is 2000 milliseconds.

   Example 17-38 Correlating Output Adapter Configuration: failOverDelay

   ...
       <wlevs:adapter id="myHaCorrelatingAdapter" provider="ha-correlating" >
           <wlevs:listener ref="JMSOutboundAdapter"/>
           <wlevs:instance-property name="failOverDelay" value="2000"/>
       </wlevs:adapter>
   ...
   

   For more information, see Section 17.2.4.1, "Correlating Output Adapter EPN Assembly File Configuration".

9. Create a second regular JMS input adapter.

   Example 17-39 shows a JMS adapter named JMSInboundAdapter2.

   Example 17-39 Inbound JMS Adapter Assembly File

   ...
       <wlevs:adapter id="JMSInboundAdapter2" provider="jms-inbound">
       </wlevs:adapter>
   ...
   

   This JMS input adapter must be configured identically to the first JMS input adapter (in this example, JMSInboundAdapter). Example 17-40 shows the component configuration file for both the JMS input adapters. Note that both have exactly the same configuration, including the same provider.

   Example 17-40 Inbound JMS Adapter Component Configuration File

   <?xml version="1.0" encoding="UTF-8"?>
   <wlevs:config 
           xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
           xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
       ...
       <jms-adapter>
           <name>JMSInboundAdapter</name>
           <jndi-provider-url>t3://localhost:7001</jndi-provider-url>
           <destination-jndi-name>./Queue1</destination-jndi-name>
           <user>weblogic</user>
           <password>weblogic</password>
           <work-manager>JettyWorkManager</work-manager>
           <concurrent-consumers>1</concurrent-consumers>
       </jms-adapter>
   
       <jms-adapter>
           <name>JMSInboundAdapter2</name>
           <jndi-provider-url>t3://localhost:7001</jndi-provider-url>
           <destination-jndi-name>./Queue1</destination-jndi-name>
           <user>weblogic</user>
           <password>weblogic</password>
           <work-manager>JettyWorkManager</work-manager>
           <concurrent-consumers>1</concurrent-consumers>
       </jms-adapter>
       ...
   </wlevs:config>
   

10. Create a channel to function as the correlated source.

    You must configure this channel with the second regular JMS input adapter as its source.

    Example 17-41 shows a correlated source named clusterCorrelatingOutstream whose source is JMSInboundAdapter2.

    Example 17-41 Creating the Correlated Source

    ...
        <wlevs:adapter id="JMSInboundAdapter2" provider="jms-inbound">
        </wlevs:adapter>
    
        <wlevs:channel id="clusterCorrelatingOutstream" event-type="StockTick" advertise="true">
            <wlevs:source ref="JMSInboundAdapter2"/>
        </wlevs:channel> 
    

11. Configure the Oracle CEP high availability correlating output adapter with the correlatedSource.

    Example 17-38 shows a correlating output adapter configuration where the correlatedSource is clusterCorrelatingOutstream.

    Example 17-42 Correlating Output Adapter: correlatedSource

    ...
        <wlevs:adapter id="myHaCorrelatingAdapter" provider="ha-correlating" >
            <wlevs:listener ref="JMSOutboundAdapter"/>
            <wlevs:instance-property name="failOverDelay" value="2000"/>
            <wlevs:instance-property name="correlatedSource" value="clusterCorrelatingOutstream"/>
        </wlevs:adapter>
    ...
    

    For more information, see Section 17.2.4.1, "Correlating Output Adapter EPN Assembly File Configuration".

12. If your application is an Oracle CEP high availability Type 1 application (the application must generate exactly the same sequence of output events as existing secondaries), configure the warm-up-window-length for the correlating output adapter.

    For more information, see:

    • Section 16.3.2.5, "Choose an Adequate warm-up-window Time"

    • Section 17.2.4.2, "Correlating Output Adapter Component Configuration File Configuration"

13. Configure the component configuration file to enable session-transacted for both inbound JMS adapters and the outbound JMS adapter as Example 17-43 shows:

    Example 17-43 Inbound and Outbound JMS Adapter Component Configuration File

    <?xml version="1.0" encoding="UTF-8"?>
    <wlevs:config 
            xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
            xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
        ...
        <jms-adapter>
            <name>JMSInboundAdapter</name>
            <jndi-provider-url>t3://localhost:7001</jndi-provider-url>
            <destination-jndi-name>./Queue1</destination-jndi-name>
            <user>weblogic</user>
            <password>weblogic</password>
            <work-manager>JettyWorkManager</work-manager>
            <concurrent-consumers>1</concurrent-consumers>
            <session-transacted>true</session-transacted>
        </jms-adapter>
    
        <jms-adapter>
            <name>JMSInboundAdapter2</name>
            <jndi-provider-url>t3://localhost:7001</jndi-provider-url>
            <destination-jndi-name>./Queue1</destination-jndi-name>
            <user>weblogic</user>
            <password>weblogic</password>
            <work-manager>JettyWorkManager</work-manager>
            <concurrent-consumers>1</concurrent-consumers>
            <session-transacted>true</session-transacted>
        </jms-adapter>
        ...
        <jms-adapter>
            <name>JMSOutboundAdapter</name>
            <event-type>JMSEvent</event-type>
            <jndi-provider-url>t3://localhost:7001</jndi-provider-url>
            <destination-jndi-name>Topic1</destination-jndi-name>
            <delivery-mode>nonpersistent</delivery-mode>
            <session-transacted>true</session-transacted>
        </jms-adapter>
        ...
    </wlevs:config>
    

14. Optionally, configure the component configuration file to include the Oracle CEP high availability input adapter and correlating output adapter as Example 17-27 shows.

    Example 17-44 High Availability Input and Output Adapter Component Configuration File

    <?xml version="1.0" encoding="UTF-8"?>
    <wlevs:config 
            xmlns:wlevs="http://www.bea.com/ns/wlevs/config/application"
            xmlns:ha="http://www.oracle.com/ns/cep/config/cluster">
        ...
        <ha:ha-inbound-adapter>
            <name>myHaInputAdapter</name>
        </ha:ha-inbound-adapter>
        ...
        <ha:ha-correlating-adapter>
            <name>myHaBroadcastAdapter</name>
            <fail-over-delay>2000</fail-over-delay>
        </ha:ha-correlating-adapter>
        ...
    </wlevs:config>
    

    For more information, see:

    • Section 17.2.1.2, "High Availability Input Adapter Component Configuration File Configuration"

    • Section 17.2.4.2, "Correlating Output Adapter Component Configuration File Configuration"

15. Optionally, add an ActiveActiveGroupBean to your EPN to improve scalability.

    For more information, see Section 19.2, "Configuring Scalability With the ActiveActiveGroupBean".

16. Deploy your application to the deployment group you created in step 1.

    For more information, see Section 20.4, "Deploying Oracle CEP Applications".

    Oracle CEP automatically selects one of the Oracle CEP servers as the primary.

17.2.1 How to Configure the High Availability Input Adapter

The Oracle CEP high availability broadcast output adapter is implemented by BroadcastInputAdapter.

This section describes how to configure the Oracle CEP high availability input adapter, including:

• Section 17.2.1.1, "High Availability Input Adapter EPN Assembly File Configuration"

• Section 17.2.1.2, "High Availability Input Adapter Component Configuration File Configuration"

For more information, see Section 16.1.3.1, "High Availability Input Adapter".

<wlevs:adapter id="jmsAdapter" provider="jms-inbound"
    <wlevs:listener ref="myHaInputAdapter"/>      
</wlevs:event-bean>

<wlevs:adapter id="myHaInputAdapter" provider="ha-inbound">
    <wlevs:instance-property name="keyProperties" value="id"/>
    <wlevs:instance-property name="timeProperty" value="arrivalTime"/>
    <wlevs:instance-property name="eventType" value="MyEventType"/>
</wlevs:adapter>

<wlevs:channel id="inputChannel" event-type="MyEventType ">
    <wlevs:source ref="myHaInputAdapter"/>
    <wlevs:application-timestamped>
        <wlevs:expression>arrivalTime</wlevs:expression>
    </wlevs:application-timestamped>
</wlevs:channel>

<ha:ha-inbound-adapter>
    <name>myHaInputAdapter</name>
    <heartbeat units="millis">1000</heartbeat>
    <batch-size>10</batch-size>
</ha:ha-inbound-adapter>

17.2.2 How to Configure the Sliding Window Output Adapter

The Oracle CEP high availability sliding window output adapter is implemented by SlidingWindowQueueTrimmingAdapter.

This section describes how to configure the Oracle CEP high availability sliding window output adapter, including:

• Section 17.2.2.1, "Sliding Window Output Adapter EPN Assembly File Configuration"

• Section 17.2.2.2, "Sliding Window Adapter Component Configuration File Configuration"

For more information, see Section 16.1.3.2, "Sliding Window Output Adapter".

<wlevs:adapter id="mySlidingWindowingAdapter" provider ="ha-buffering">
    <wlevs:listener>
        <bean class="com.bea.wlevs.example.cluster.ClusterAdapterBean"/>
    </wlevs:listener>
    <wlevs:instance-property name="windowLength" value="15000"/>
</wlevs:adapter>

<ha:ha-buffered-adapter>
    <name>mySlidingWindowingAdapter</name>
    <window-length>15000</window-length>
    <warm-up-window-length units="minutes">6</warm-up-window-length>
</ha:ha-buffered-adapter>

17.2.3 How to Configure the Broadcast Output Adapter

The Oracle CEP high availability broadcast output adapter is implemented by class GroupBroadcastQueueTrimmingAdapter.

This section describes how to configure the Oracle CEP high availability broadcast output adapter, including:

• Section 17.2.3.1, "Broadcast Output Adapter EPN Assembly File Configuration"

• Section 17.2.3.2, "Broadcast Output Adapter Component Configuration File Configuration"

For more information, see Section 16.1.3.3, "Broadcast Output Adapter".

<wlevs:adapter id="myBroadcastAdapter" provider="ha-broadcast">
    <wlevs:listener ref="actualAdapter"/>
    <wlevs:instance-property name="keyProperties" value="time"/>
    <wlevs:instance-property name="monotonic" value="true"/>
</wlevs:adapter>

<ha:ha-broadcast-adapter>
    <name>myBroadcastAdapter</name>
    <trimming-interval units="events">10</trimming-interval>
    <warm-up-window-length units="minutes">6</warm-up-window-length>
</ha:ha-broadcast-adapter>

17.2.4 How to Configure the Correlating Output Adapter

The Oracle CEP high availability correlating output adapter is implemented by class CorrelatedQueueTrimmingAdapter.

This section describes how to configure the Oracle CEP high availability correlating output output adapter, including:

• Section 17.2.4.1, "Correlating Output Adapter EPN Assembly File Configuration"

• Section 17.2.4.2, "Correlating Output Adapter Component Configuration File Configuration"

For more information, see Section 16.1.3.4, "Correlating Output Adapter".

<wlevs:adapter id="myCorrelatingAdapter" provider="ha-correlating">
    <wlevs:listener>
        <bean class="com.bea.wlevs.example.cluster.ClusterAdapterBean"/>
    </wlevs:listener>
    <wlevs:instance-property name="correlatedSource" ref="clusterCorrOutstream"/>
    <wlevs:instance-property name="failOverDelay" value="2000"/>
</wlevs:adapter>

<ha:ha-correlating-adapter>
    <name>myCorrelatingAdapter</name>
    <window-length>15000</window-length>
    <warm-up-window-length units="minutes">6</warm-up-window-length>
</ha:ha-correlating-adapter>