The following sections describe the new and changed features in Oracle CEP 10.3:
Version 10.3 of Oracle CEP includes the following new features:
You can now configure multiple servers in an Oracle CEP domain, and cluster them together to achieve high availability.
Oracle CEP applications can optionally publish or consume events to and from a cache to increase the availability of the events and increase the performance of their applications. A cache is a temporary storage area for events, created exclusively to improve the overall performance of your application; it is not necessary for the application to function correctly.
The event repository feature of Oracle CEP allows you to record events flowing through an event processing network (EPN) and store them so you can later play back the events. The event repository is configured per stage, such as a processor or stream.
Seein the Visualizer Online Help document.
Oracle CEP Visualizer, henceforth called Visualizer for simplicity, is a Web 2.0 application that consumes data from Oracle CEP, displays it in a useful and intuitive way to system administrators and operators, and, for specificied tasks, accepts data that is then passed back to Oracle CEP so as to change it configuration.
An HTTP Publish-Subscribe Server is a mechanism whereby Web clients, such as browser-based clients, subscribe to channels, receive messages as they become available, and publish messages to these channels, all using asynchronous messages over HTTP. Every instance of Oracle CEP includes a pub-sub server that programmers can use to implement HTTP publish-subscribe functionality in their applications.
Oracle CEP provides both inbound and outbound JMS adapters that you can use in your event applications to send and receive messages to and from a JMS queue, respectively, without writing any Java code.
The Configuration Wizard is a new tool for creating Oracle CEP domains.
The event processing language (EPL) has the following new features:
SELECTclauses to be embedded within another
EXISTSkeywords are available when subqueries are used in the
WHEREclause. Previously they were available only in the
FROMclause and without the ability to correlate the inner and outer query.
Oracle CEP provides a variety of mechanisms to protect server resources such as data and event streams, configuration, username and password data, security policy information, remote credentials, and network traffic.
Oracle CEP supports various security providers for authentication, authorization, role mapping, and credential mapping. As initially installed, Oracle CEP is configured to use the file-based providers for both authentication and authorization. You can also configure the system to use an LDAP or DBMS provider.
For details, see.
Version 10.3 of Oracle CEP includes the following changed and deprecated features:
The HelloWorld example has been simplified in the following ways:
The Oracle CEP programming model has changed in the following ways:
So as to support clustering and a multi-server environment, the directory structure of the out-of-the-box and sample domains has changed.
Previously, all domain files were located directly under the domain directory, such as
ORACLE_CEP_HOME refers to the top-level installation directory of Oracle CEP.
In the 10.3 release, the domain directory contains one or more sub-directories that correspond to a single server; this directory contains all the configuration files for that server. For example, the HelloWorld domain contains a single server whose configuration files are located in the following directory:
The new Configuration Wizard for creating domains follows this updated directory structure.
-stop commands of the Deployer tool have been deprecated.
When using the
-install command to install an application, Oracle CEP automatically starts it after all internal initialization tasks have completed. Subsequently, if you stop and start the Oracle CEP server instance, the application is automatically stopped and started, respectively.
The Deployer tool has two new options:
-resume. Users should use
-suspend to suspend a currently running application, and
-resume for it to resume running.
The management framework of Oracle CEP has been overhauled in this version.
For details, see. See Backward Compatibility Issues for changes that are not backward compatible to the previous version of Oracle CEP (WebLogic Event Server 2.0.)
You can now specify logging severity for modules of a server, in addition to the logging severity of the server itself. The severity of the modules overrides that of the server.
For details, see.
Upgrading to Oracle CEP 10.3 is a two-step process: first you must upgrade your applications and then you must upgrade the domain to which the applications are deployed. The following sections describe each step:
This section describes the steps you must take to upgrade an application that you developed in Version 2.0 of WebLogic Event Server so that it runs on Oracle CEP 10.3.
MANIFEST.MFfile to import new versions of Spring framework and Oracle CEP packages, as well as new required packages. In paticular:
2.5.5. For example:
188.8.131.52. For example:
Import-Packageheader if they are not already included:
|Note:||This change is a result of the upgrade of the Spring framework (from 2.0 to 2.5) that occurred between WebLogic Event Server 2.0 and Oracle CEP 10.3, not as a direct result of the Oracle CEP upgrade.|
<osgi:service-property>tag, use the
<entry>tag with the
valueattributes, rather than the old
<prop>tag. For example, update the following 2.0 tag:
<entry key="type" value="SocketAdapterType"/></osgi:service-properties>
refattribute of an instance-property must always be set to an explicit value; it can no longer be an empty string to indicate an implicit use of a default value. For example, update the following 2.0 tag:
<wlevs:adapter id="fileAdapter" provider="FileAdapterType">
<!-- file: empty value uses default
<wlevs:instance-property name="file" value="" /><wlevs:listener ref="algoTradingProcessor"/>
<wlevs:adapter id="fileAdapter" provider="FileAdapterType">
<wlevs:instance-property name="file" value="test.file" /><wlevs:listener ref="algoTradingProcessor"/>
After you have made the preceding changes, reassemble the application and deploy it to Oracle CEP 10.3. See.
If, during deployment, you get an exception that indicates that a package is invisible, add this package to the
Import-Package header of the
MANIFEST.MF file, then reassemble and redeploy the application. Keep adding packages in this manner until the application deploys successfully.
This section describes the steps you must take to upgrade a WebLogic Event Server 2.0 domain so that it runs correctly in Oracle CEP 10.3.
For clarity, it is assumed that the existing WebLogic Event Server 2.0 domain is located in the
For the purposes of this procedure, it is assumed that the new Oracle CEP 10.3 domain is called
mydomain30, it contains a single server called
defaultserver, and the server files are located in the
The WebLogic Event Server 2.0 files are located relative to the domain directory (
/bea/user_projects/domains/mydomain20 in our example) and the Oracle CEP 10.3 files are located relative to the the server directory under the domain directory (
/oracle_cep/user_projects/domains/mydomain30/defaultserver in our example).
atnstore.txtfile in the WebLogic Event Server 2.0 domain, located in the
configsub-directory of the main domain directory, and add the new Oracle 10.3 groups:
startwlevs.sh(Unix) command scripts in the WebLogic Event Server 2.0 domain to point to the new Oracle 10.3 binaries.
stopwlevs.sh(Unix) command scripts in the WebLogic Event Server 2.0 domain to point to the new Oracle 10.3 binaries.
The following are non-backward compatible changes in the management framework:
StageMBeanand replaced by
com.bea.wlevs.management.boot.BootMBeanhas been removed.
com.bea.wlevs.management.configuration.ConfigSessionBeanhas been removed.
AppDeploymentMBeanhas been changed to include the
DomainMBeanas a parent.
com.bea.wlevs.server.management.mbean.ServerRuntimeMBeanhas been changed to
com.bea.wlevs.management.spi_*, in addition to the existing
com.bea.wlevs.spi.ManagementServicehas been moved from bundle