29 Oracle Complex Event Processing

29.1.1 Deprecated API and Schemas

Table 29-1 lists Java API deprecated in 11g Release 1 (11.1.1) and the replacement API, if any.

Table 29-2 lists Oracle CEP schema deprecated in 11g Release 1 (11.1.1) and the replacement schema, if any.

29.1.2 Adapter Changes

The programming model for adapters has changed as follows:

• Outbound Adapters

• Lifecycle Callback Methods for Adapters

• Runnable Adapters

• Adapter Factories

• Publishing Adapter Providers

• StockTick Event Type Replaced by OracleStockTick

Outbound Adapters

Adapters can now also be outbound; previously they were only inbound.

Lifecycle Callback Methods for Adapters

Spring tags for adapters now include attributes for setting lifecycle callback methods via the EPN assembly file.

Runnable Adapters

For adapters that want to run in a thread, their Java class should now implement com.bea.wlevs.ede.api.RunnableBean.

Adapter Factories

Programmers are no longer required to create an adapter factory when creating adapters. You only need to create an adapter factory if you want to share adapters among applications.

Publishing Adapter Providers

Adapter providers are factories for adapters that are published through the OSGi service registry.

Previously, the only way of advertising adapter providers was to use Spring-DM only, like this:

<osgi:service interface="com.bea.wlevs.ede.api.AdapterFactory" ref="myBean">
    <osgi:service-properties>
        <entry key="type" value="SocketAdapterType"/>
    </osgi:service-properties>
</osgi:service>

However, Spring-DM does not support exporting and importing an OSGi service in the same application so the above approach is deprecated.

Now, you should declare providers with the wlevs:factory tag like this:

<wlevs:factory provider-name="SocketAdapterType" ref="myBean">

This will work whether the adapters are in the same application or not.

Note that if your adapters and providers are collocated (both in the same application) using a provider is optional; you could just instantiate the adapter directly.

Failure to make this change may result in an application that fails to start and eventually times out.

StockTick Event Type Replaced by OracleStockTick

When using the loadgen adapter, note that the StockTick event is now named OracleStockTick.

29.1.3 New and Deprecated Options in the Deployer Tool

The Deployer tool includes the following changes in this release:

• Section 29.1.3.1, "Suspend and Resume Commands"

• Section 29.1.3.2, "Start and Stop Commands are Deprecated"

• Section 29.1.3.3, "Password Argument Deprecated"

For more information, see "Deployer Command-Line Reference" in the Oracle CEP Administrator's Guide.

29.1.4 Changes in Management, Monitoring, and JMX

The management framework of Oracle CEP has been overhauled in this release.

Oracle CEP no longer supports the JRMP protocol. Instead, JMX clients must use the more secure MSA protocol for both local and remote access to the Oracle CEP JMX server. When you connect to the Oracle CEP JMX server that is running on localhost or on a remote host, you must always use the JMX URL service:jmx:msarmi://HOST-NAME:PORT/jndi/jmxconnector so that you are always using the MSA connector (where HOST-NAME is either localhost or the name of the remote host and PORT is the Oracle CEP server JNDI port).

For more information, see:

• "Accessing the Oracle CEP JMX Server" in the Oracle CEP Administrator's Guide

• "Configuring JMX" in the Oracle CEP Administrator's Guide

29.1.5 Using stopwlevs.sh With Multiple Servers on the Same Host

Included per bug 8417480.

Consider a scenario where you start two servers on the same host, for example, with server 1 listening on port 9002 and server 2 listening on port 9022. If you then use stopwlevs.sh in the server 1 domain directory, the server listening on port 9002 is stopped. If you then use stopwlevs.sh in the server 2 domain directory, the stop operation fails due to connection reset error.

Workaround: use the stopwlevs.sh command line argument -url or -listenPort to specify a port other than 9002.

29.1.6 Underestimated Latency For Application-Timestamped Channels

The monitor service may underestimate the latency time of events that are being processed through the CQL processor when application-timestamped channels are being used and is-totally-ordered is not enabled.

29.1.7 JConsole Connection may Throw Benign Null Pointer Exceptions

Included per bug 8515145.

When you connect to Oracle CEP server using JConsole (with or without the wlevsjconsole.sh script), JConsole may throw a java.lang.NullPointerException.

Workaround: click OK in the exception dialog box and proceed. The exception does not affect the JMX connection or Oracle CEP server.

29.1.8 Variable Duration Non-Event Detection is not Supported

Fixed duration non-event pattern detection is supported in 11g Release 1 (11.1.1). When you create a query for fixed duration non-event detection, you may use the DURATION clause with constant value and time unit, such as DURATION 5 SECONDS, or just a constant value such as DURATION 5.

Variable duration non-event pattern detection is not supported in 11g Release 1 (11.1.1). That is, you may not use the DURATION clause with an arbitrary arithmetic expression, such as DURATION c1+4.

Recurring non-event pattern detection is supported in 11g Release 1 (11.1.1) but only for the fixed duration case. That is, you may use a DURATION clause with a MULTIPLES OF clause but only for a duration that is a constant value.

29.1.9 JMSAdapterMBean Methods for New Connection, User, and Password

The following methods have been added to com.bea.wlevs.management.configuration.JMSAdapterMBean:

• getConnectionUser

• getConnectionPassword

• getConnectionEncryptedPassword

The following attributes have been added to the wlevs_application_config.xsd element jms-adapter:

• connection-user

• connection-password

• connection-encrypted-password

When Oracle CEP acquires the JNDI InitialContext, it uses the user and password (or encrypted-password) settings.

When Oracle CEP calls the createConnection method on the javax.jms.ConnectionFactory to create a connection to the JMS destination (JMS queue or topic), it uses the connection-user and connection-password (or connection-encrypted-password) settings, if configured. Otherwise, Oracle CEP uses the user and password (or encrypted-password) settings.

You can use the connection-user and connection-password (or connection-encrypted-password) settings in applications where one security provider is used for JNDI access and a separate security provider is used for JMS access.

29.2.1 Accessing Signal Generation Dashboard With Firefox Version 3.0

When accessing the signal generation example dashboard (at URL http://localhost:9002/signalgeneration/dashboard.html) using the Firefox browser version 3.0 on Windows, you will get an error when you click Start.

Workaround: use Internet Explorer version 7 to access the signal generation example dashboard.

29.2.2 VPN Software and Multicast Traffic

Active VPN software is known to have unpredictable behavior on multicast traffic. Additionally, having both Cisco VPN and Nortel VPN installed breaks multicast traffic.

29.2.3 Starting Oracle CEP Visualizer With Firefox

When using Oracle CEP Visualizer with the Firefox browser (version 3.0, SSL, and JDK 1.6), the first time you access a Oracle CEP Visualizer page it will render slowly, sometimes up to 30 seconds.

29.2.4 Uploading Files Using Oracle CEP Visualizer, Firefox, and SSL

When using Oracle CEP Visualizer, you may get an error if you try to upload a file using the Firefox browser and SSL.

This is a known problem (http://bugs.adobe.com/jira/browse/FP-226) with Adobe Flex that affects Oracle CEP Visualizer.

29.2.5 Foreign Stage Channels Cannot be Connected to an Oracle CQL Processor

If a channel is connected to an Oracle CQL processor, it cannot be a foreign stage.

29.2.6 Exceptions Thrown When Using Oracle CEP Visualizer with FireFox

When using Oracle CEP Visualizer with FireFox:

• Do not set the Jetty scratch directory to a path with a space in it. Doing so will cause FileNotFoundException.

• Ignore EOFException thrown on the server side; these exceptions will not cause client side failure.

29.2.7 Oracle CEP IDE for Eclipse and FireFox 3 Libraries are Incompatible

Included per bug 8514556.

The Oracle CEP IDE for Eclipse uses Eclipse 3.3, which is incompatible with required FireFox 3 libraries on Linux. In this case, Eclipse will crash on startup with a JVM core dump and error message like this:

# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00bc80ac, pid=18044, tid=3086637584
#
# Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode, sharing
linux-x86)
# Problematic frame:
# C  [libc.so.6+0x710ac]  memcpy+0x1c
#
# An error report file with more information is saved as:
# /usr/local/bt/workspace/testruntime/eclipse/hs_err_pid18044.log 

Workaround: perform the following procedure.

1. Change to the root user on your Linux machine.

2. Prevent Eclipse from loading the libc.so library noted in the core dump error message:

   mv libc.so libc.so.orig
   

   Note:

   This will disable FireFox 3 on this machine. To use FireFox 3, you must change the name of this library back to libc.so.

3. Follow the instructions outlined in the Eclipse Linux crash support Wiki page:

   http://wiki.eclipse.org/IRC_FAQ#I_just_installed_Eclipse_on_Linux.2C_but_it_does_not_start._What_is_the_problem.3F

   In particular, ensure that the JVM you are using with Eclipse is:

   • explicitly pointed to in the eclipse.ini file, and

   • JDK 1.6 or higher

29.2.8 Configuring Oracle CEP Native Clustering Using IPv6 on Linux

Included per bug 8548822.

When using Oracle CEP native clustering on Linux with IPv6, you may see an error like the one shown in Example 29-1 after restarting a member of a cluster.

<Error> <evs4j> <BEA-2049005> <The cluster member 3 is considered to have failed>

Workaround: perform the following procedure:

1. Using the editor of your choice, open the startwlevs.sh script for the affected Oracle CEP sever.

   The startwlevs.sh server start script is located in the server directory under the main domain directory. For example, the default server directory of the HelloWorld domain is located in ORACLE_CEP_HOME/ocep_11.1/samples/domains/helloworld_domain/defaultserver, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep.

2. Edit the startwlevs.sh script to add the -Djava.net.preferIPv4Stack=true property to the java command line:

   "$JAVA_HOME/bin/java" $JVM_ARGS $DEBUG_ARGS -Djava.net.preferIPv4Stack=true 
   -Dwlevs.home="$USER_INSTALL_DIR" -Dbea.home="$BEA_HOME" 
   -jar "${USER_INSTALL_DIR}/bin/wlevs.jar" $ARGS
   

3. Save and close the startwlevs.sh script.

4. Start the affected Oracle CEP server using the modified startwlevs.sh script.

29.2.9 Multi-Byte Characters are not Supported by loadgen

The loadgen utility supports only ASCII characters. It does not support multi-byte character sets.

29.2.10 Oracle CEP Server Cannot Start if Keystore and Private Key Passwords are Different

The passwords for the keystore and the alias for the SSL private key must be the same. If they are not, the Oracle CEP Server will not start.

29.2.11 Configuring Oracle CEP Server to use the Sun JVM

Typically, when you install Oracle CEP server, you configure Oracle CEP server to use the bundled JRockit SDK 1.6.0_05. Alternatively, you can configure Oracle CEP server to use a supported Sun Microsystems JDK.

How to configure Oracle CEP Server for use with the Sun JVM:

1. Install the appropriate Sun JDK.

   For more information, see:

   • http://www.oracle.com/technology/software/products/ias/files/oracle%20fusion%20middleware%2011gr1%20%2811%201%201%201%200%29%20certification%20matrix.xls

   • http://java.sun.com/javase/downloads/index.jsp.

2. Using the editor of your choice, open the setDomainEnv.sh or setDomainEnv.cmd script for the affected Oracle CEP sever.

   This script is located in the server directory under the main domain directory. For example, the default server directory of the HelloWorld domain is located in ORACLE_CEP_HOME/ocep_11.1/samples/domains/helloworld_domain/defaultserver, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep.

3. Edit this script to set the JAVA_HOME variable to your JDK 1.6.0_11 installation:

   JAVA_HOME=/scratch/jdk/jdk_1.6.0_11
   

4. Save and close the script.

5. Using the editor of your choice, open the startwlevs.sh or startwlevs.cmd script for the affected Oracle CEP sever.

   This server start script is located in the server directory under the main domain directory. For example, the default server directory of the HelloWorld domain is located in ORACLE_CEP_HOME/ocep_11.1/samples/domains/helloworld_domain/defaultserver, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep.

6. Edit this script to add the following properties to the JVM_ARGS variable:

   ...
   JVM_ARGS=-XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass -Xms512m
   ...
   

7. Save and close the script.

8. Start the affected Oracle CEP server using the modified startwlevs.sh or startwlevs.cmd script.

29.2.12 Eclipse 3.3 Fails to Start Up on Red Hat Linux 5.3

Eclipse 3.3 fails to start on Red Hat Linux 5.3.

To work around this issue, add the following to the eclipse.ini file:

 -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner-1.9

This is not an issue in Eclipse 3.4 and higher.

29.2.13 Oracle CEP Applications as Web Service Provider Requires JDK 1.6.0_14 or Higher

To configure an Oracle CEP application as a Web service provider, you must use JDK 1.6.0_14 or above.

29.2.14 Configuration Wizard Fails to Create Domain on Alternate Mount Points

Included per bug 9473264 .

If you install Oracle CEP on one mount point, such as /opt, and you run the ORACLE_CEP_HOME/ocep_11.1/common/bin/config.sh to create a domain and you specify some other mount point, such as /dev (where /dev and /opt represent two different hard disks), when you enter the name of the new domain and the full pathname of its domain location, the configuration wizard will fail to create the domain with a ConfigGeneratorException.

In this release, you may only create domains on the same mount point as the one on which you installed Oracle CEP.

29.2.15 Suspending and Resuming the Oracle CEP Server is not Supported by Oracle High Availability

Included per bug 9526609.

In this release, you may not suspend or resume an Oracle CEP server with an Oracle high availability-enabled application. That is, you may not use the commands:

kill -s STOP CEP_SERVER_PID
kill -s CONT CEP_SERVER_PID 

Where CEP_SERVER_PID is the process ID of the Oracle CEP server.

29.2.16 Simultaneous Secondary Failure May Result in Deadlock Using Oracle High Availability

Included per bug 9787466.

In the rare case that two secondary servers fail simultaneously, there is a possibility that Oracle Coherence will encounter a deadlock and Oracle high availability failover will not succeed.

Workaround:

1. Shutdown all the servers in the Oracle high-availability deployment group.

   This will also shutdown Oracle Coherence.

2. Restart all the servers in the Oracle high-availability deployment group.

   This will also restart Oracle Coherence.

29.2.17 Set Production Oracle CEP Servers to Log Levels Higher Than NOTICE Only

In a production system, ensure that the log level is set to NOTICE or higher (that is NOTICE, WARNING, ERROR, CRITICAL, ALERT, or EMERGENCY) for both security and performance reasons.

For more information, see "Using Log Severity Levels" in the Oracle CEP Administrator's Guide.

29.2.18 Change Default User Name and Password After Installation

As part of the installation process, the installer creates a default domain named ocep_domain under ORACLE_CEP_HOME/user_projects/domains. Oracle recommends that you to change the default user name and password for this domain after installation is completed.

For more information, see "How to Change the Password of a User" in the Oracle CEP Visualizer User's Guide.

29.2.19 Oracle CEP Visualizer com.bea.wlevs.visualizer.help Bundle Startup Fails

When you first start up the Oracle CEP server, under some conditions, deployment of the Oracle CEP Visualizer com.bea.wlevs.visualizer.help bundle may timeout and fail with a server log error like:

Critical error in OHW configuration. Config URL: null 

Workaround:

1. Stop the Oracle CEP server.

2. Delete the ORACLE_CEP_HOME/user_projects/domains/ocep_domain/SERVER_NAME/Jetty directory and its contents.

3. Start the Oracle CEP server.

29.2.20 Oracle CQL Sample Built With build.xml File Fails to Deploy

If you build the Oracle CQL sample using the ORACLE_CEP_HOME\ocep_11.1\samples\source\applications\cql\build.xml file and try to deploy the ORACLE_CEP_HOME\ocep_11.1\samples\source\applications\cql\dist\com.bea.wlevs.example.cql_11.1.1.1_0.jar file, the deployment will fail.

Workaround: edit the ORACLE_CEP_HOME\ocep_11.1\samples\source\applications\cql\build.xml file and in target copyfiles, change the includes attribute on line 61 to read includes="**/*" as Example 29-2 shows:

...
    <target name="copyfiles">
        <mkdir dir="${output.dir}/META-INF/spring" />
        <copy todir="${output.dir}/META-INF/spring">
            <fileset dir="META-INF/spring" includes="*" />
        </copy>
        <mkdir dir="${output.dir}/META-INF/wlevs" />
        <copy todir="${output.dir}/META-INF/wlevs">
            <fileset dir="META-INF/wlevs/" includes="**/*" />
        </copy>
    </target>
...

29.2.21 Cannot Start Server With Security Disabled in a User-Configured Domain

Included per bug 9604646.

If you use the configuration wizard to create your own domain (such as ORACLE_CEP_HOME/my_projects/my_domains/mydomain/myserver), you cannot start the Oracle CEP server with security disabled by adding -disablesecurity to the server startup command line.

Workaround: to start the server with security disabled, edit the startwlevs.sh file to add the -disablesecurity argument as Example 29-3 shows:

"$JAVA_HOME/bin/java" $JVM_ARGS $DEBUG_ARGS -Dwlevs.home="$USER_INSTALL_DIR" -Dbea.home="$BEA_HOME"  -jar "${USER_INSTALL_DIR}/bin/wlevs.jar" -disablesecurity $ARGS

For more information, see "Creating an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode" in the Oracle CEP Administrator's Guide.

29.2.22 Do Not Terminate the Full Pathname of a New Domain With a Slash

Included per bug 9649029.

When using the Configuration Wizard to create a new domain, when prompted for the full pathname to the new domain, do not terminate the pathname with a Linux file separator character (/).

For example, enter this:

/cep/user_projects/domains

Do not enter this:

/cep/user_projects/domains/

29.2.23 Enabling and Disabling Configuration History Management

Included per bug 9828236.

By default, Oracle CEP provides resource and application configuration history management.

Optionally, you can disable this feature by editing the ORACLE-CEP-HOME/user_projects/domains/ocep_domain/SERVER/startwlevs.sh file :

"$JAVA_HOME/bin/java" $JVM_ARGS $DEBUG_ARGS -Dwlevs.home="$USER_INSTALL_DIR" -Dbea.home="$BEA_HOME"  -jar "${USER_INSTALL_DIR}/bin/wlevs.jar" $ARGS

If you disable this feature, Oracle CEP cannot propagate rules amongst the Oracle CEP servers in a multi-server domain. In this case, to propagate rule changes, you must manually update the rules in all the servers of a multi-server domain.

If you disable this feature and then wish to re-enable it, you must do so as follows:

1. Undeploy your Oracle CEP application.

2. Shutdown the Oracle CEP server.

3. Edit the startwlevs.sh file to either remove the -Dcom.oracle.ocep.config.version.enabled system property or set it to true.

4. Start the Oracle CEP server.

5. Deploy your Oracle CEP application.

Failure to do so may cause rule propagation to fail in a multi-server domain and may prevent the Oracle CEP Visualizer from maintaining a consistent view of the Oracle CEP servers in a multi-server domain.

29.2.24 Manually Refresh Oracle CEP Visualizer Panels After Upgrade or Adding Oracle CQL Queries

Before upgrading an Oracle CEP application, be sure to close all open panels. Failure to do so may leave some panels in a disabled state.

When using the Oracle CEP Visualizer to add or remove Oracle CQL queries or views in an Oracle CEP application that is deployed in a multi-server domain, before you can see the change in the Oracle CEP Visualizer Oracle CQL Rules Tab, you must click either of the View or Query radio buttons and then click the All Rules radio button.

29.2.25 Simultaneous Updates From Multiple Servers in a Cluster are not Supported

In a multi-server domain, you may not issue updates from more than one Oracle CEP server at a time.

For example, you cannot modify Oracle CQL rules on one server at the same time as modifying Oracle CQL rules on another server.

This applies to any configuration management operation such as rules, high-availability adatper changes, and so on.

29.3.1 Oracle CQL Example Uses orderData.prop not data-aggre.prop

In section "To test the missing event query" in the Oracle CEP Getting Started, step 3 should read:

1. ...

2. ...

3. Run the load generator using the orderData.prop properties file:

   1. On Windows:

      prompt> runloadgen.cmd orderData.prop
      

   2. On UNIX:

      prompt> runloadgen.sh orderData.prop
      

29.3.2 Event Record and Playback Example Uses Default Berkeley Database

The first paragraph in "Event Record and Playback Example" in the Oracle CEP Getting Started should read as follows:

"The record and playback example shows how to configure a component to record events to an event store and then configure another component in the network to playback events from the store. The example uses the Oracle CEP-provided default Berkeley database to store the events. The example also shows how to configure a publishing HTTP pub-sub adapter as a node in the event processing network."

Example 3-11 "recplay Application Configuration File config.xml: adapter Element" in the Oracle CEP Getting Started should read as follows:

<adapter>
      <name>simpleEventSource</name>
      <record-parameters>
        <dataset-name>recplay_sample</dataset-name>
        <event-type-list>
            <event-type>SimpleEvent</event-type>
        </event-type-list>
        <batch-size>1</batch-size>
        <batch-time-out>10</batch-time-out>
      </record-parameters>
</adapter>

The following paragraph and Example 3-12 "recplay Oracle CEP Server Configuration File config.xml: data-source and rdbms-event-store-provider Elements" in the Oracle CEP Getting Started should be omitted:

"The Provider Name contains the value of the rdbms-event-store-provider child element name which corresponds to the data-source child element name as Example 3-12 shows."

The provider-name element is optional: by omitting this element, Oracle CEP uses the default Berkeley Database configuration that Oracle CEP provides. Oracle recommends that you use this default Berkeley Database configuration.

29.3.3 Deployment to a Group is Supported Only in a Multi-Server Domain

You may only deploy to a group if the target Oracle CEP server is part of a multi-server domain (that is, if clustering is enabled). You may not deploy to a group if the target Oracle CEP server is part of a standalone-server domain (that is, if clustering is disabled). For more information, see "Overview of Oracle CEP Multi-Server Domain Administration" in the Oracle CEP Administrator's Guide.

The following documentation should note this group deployment restriction:

• Table B-3, "Deployment Commands" in the Oracle CEP Administrator's Guide.

• "To deploy an Oracle CEP application using the Deployer utility" in the Oracle CEP Developer's Guide for Eclipse, step 5.

• "Deploying an Application in a Standalone-Server Domain" in the Oracle CEP Visualizer User's Guide.

• "Deploying an Application in a Multi-Server Domain" in the Oracle CEP Visualizer User's Guide.

29.3.4 Oracle CEP Java Types [C and [B Should be char[] and byte[]

Example 9-9 "EPN Assembly File event-type element for a Table" in the Oracle CEP Developer's Guide for Eclipse should read:

<wlevs:event-type-repository>
    ...
    <wlevs:event-type type-name="StockEvent">
        <wlevs:properties>
            <wlevs:property name="symbol" type="char[]" length="16" />
            <wlevs:property name="exchange" type="char[]" length="16" />
        </wlevs:properties>
    </wlevs:event-type>
    ...
</wlevs:event-type-repository>

In Table 9-2 "EPN Assembly File event-type Element Property Attributes" in the Oracle CEP Developer's Guide for Eclipse, the row for attribute type should read:

"The Oracle CEP Java type from Table 10–3 that corresponds to the column's SQL data type.In Example 10–4, the type value for column symbol is char[]."

In Table 9-3 "SQL Column Types and Oracle CEP Type Equivalents" in the Oracle CEP Developer's Guide for Eclipse:

• All occurrences of [C should read char[]

• All occurrences of [B should read byte[]

29.3.5 Oracle CEP Support for IPv4 and IPv6

The Oracle CEP Administrator's Guide does not indicate that Oracle CEP does not support IPv6. It should read as follows:

29.3.6 Configuring an EventPartitioner on a Channel

In "Event Partitioner Channel" in the Oracle CEP Developer's Guide for Eclipse, paragraphs two and three should read as follows:

"When you configure a channel to use the default EventPartitioner, you specify the name of an event property by which the channel partitions events. The default EventPartitioner calculates a hash key using the event property value's Object.hashCode() as input to an internal hash function. The hashkey % number-of-listeners is used to calculate which listener will receive the event. This algorithm is based on the same algorithm used by HashMap to calculate in which bucket to place a new item. In practice, this means events with the same event property value are sent to the same listener.

When using an event partitioner channel, if you want to perform load balancing, then each listener must be identical.

Otherwise, listeners need not be identical."

In "How to Configure Scalability With an Event Partitioner Channel" in the Oracle CEP Developer's Guide for Eclipse, Step 4 should read as follows:

"Edit the EPN assembly file to add a partitionByEventProperty instance property to the channel element.

The value of this instance-property is the name of the event property by which the channel partitions events.

In this example, the channel partitions events by event property symbol."

And Example 19-2, "Channel eventPartioner Instance Property" should read as follows:

...
    <wlevs:channel id="EventPartitionerChannel" event-type="PriceEvent">
        <wlevs:instance-property name="partitionByEventProperty" value="symbol" />
        <wlevs:listener ref="processor1" />
        <wlevs:listener ref="processor2" />
        <wlevs:listener ref="processor3" />
        <wlevs:source ref="inbound" />
    </wlevs:channel>
...

29.3.7 Event Processing Network Editor Screen Captures Show Unsupported Event Types Tab

In screen captures of the Event Processing Network (EPN) editor, an Event Types tab is shown. This tab is not supported in this release and does not appear in the actual Oracle CEP IDE for Eclipse.

29.3.8 Oracle Spatial Data Cartridge Namespace Configuration

In "How to Configure Oracle Spatial Data Cartridge Application Context" in the Oracle CEP Developer's Guide for Eclipse, the step after step 2 should read as follows:

"Edit the EPN file to add the required namespace and schema location entries as the following example shows:

<?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:spatial="http://www.oracle.com/ns/ocep/spatial/"
       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_1_1_3.xsd"
  http://www.oracle.com/ns/ocep/spatial
  http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd">

"

In "Oracle Spatial Data Cartridge Application Context" in the Oracle CEP CQL Language Reference, paragraph one should read as foolws:

"You can define an application context for an instance of an Oracle Spatial data cartridge and propagate this application context at runtime. This allows you to associate specific Oracle Spatial application defaults (such as an SDO_SRID) with a particular Oracle Spatial data cartridge instance.

Before you can define an Oracle Spatial data cartridge application context, edit your Oracle CEP application EPN assembly file to add the required namespace and schema location entries as the following example shows:

<?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:spatial="http://www.oracle.com/ns/ocep/spatial/"
       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_1_1_3.xsd"
  http://www.oracle.com/ns/ocep/spatial
  http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd">

"