This section contains information on the following subjects:
Section 2.6, "Installing an Oracle CEP Patch Using Smart Update"
Section 2.8, "Upgrading to Oracle CEP Release 11gR1 (11.1.1)"
Before you install Oracle CEP Release 11gR1 (11.1.1):
Ensure that you are installing on a supported platform.
For more information, see Section 1.6, "Supported Platforms".
Choose the JVM you will use:
If your application requires low latency, optionally install Oracle JRockit Real Time 3.1.2.
Oracle CEP performs optimally when it can access certain features from Oracle JRockit Real Time, in particular the JRockit deterministic garbage collector. Oracle CEP includes its own version of JRockit (in ORACLE_CEP_HOME/jrockit_JAVA-VERSION_RJROCKIT-VERSION), but it does not include the deterministic garbage collector.
Caution:
Be sure you install the version of Oracle JRockit Real Time for Java version 5.0 or 6.0. Oracle JRockit Real Time for Java version 1.4.2 is not compatible with Oracle CEP Release 11gR1 (11.1.1).For more information on Oracle JRockit Real Time, see http://www.oracle.com/technology/products/jrockit/jrrt/index.html.
For other platforms (such as HP or IBM/AIX), ensure that you have the appropriate platform-specific JVM installed.
For more information, see Section 1.6, "Supported Platforms".
Install Apache Ant, a Java-based build tool. For details, see the Apache Ant Project at http://ant.apache.org/.
Decide whether or not you need to upgrade Oracle CEP and Oracle CEP applications to the current release.
For more information, see Section 2.8, "Upgrading to Oracle CEP Release 11gR1 (11.1.1)".
You install Oracle CEP using a standard Oracle installation program.
You can find the installation program appropriate for your platform here: http://www.oracle.com/technology/software/products/middleware/htdocs/111110_fmw.html. For more information on supported platforms, see Section 1.6, "Supported Platforms".
The program can be used in the following modes:
Graphical mode
Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems. See Section 2.3, "Installing Oracle CEP in Graphical Mode."
Caution:
If you want to run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.Console mode
Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system. See Section 2.4, "Installing Oracle CEP in Console Mode."
Silent mode
Silent-mode installation is a non-interactive method of installing your software that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation in either of two ways: as part of a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. See Section 2.5, "Installing Oracle CEP in Silent Mode."
The Oracle CEP graphical installation program is self-explanatory, however, you can follow these steps for more information.
To install Oracle CEP in graphical mode:
Log in to the Windows or UNIX computer on which you want to install Oracle CEP.
Be sure you log in to the computer as the user that will be the main administrator of the Oracle CEP installation.
Download the product distribution file for the platform on which you want to install Oracle CEP.
Launch the installation program in graphical mode using the commands listed in the following table appropriate for your platform.
| Platform | Instructions |
|---|---|
| Windows | Using Windows Explorer, double-click the appropriate installation program file from its download directory. |
| Linux or Solaris | Open a command window, change to the download directory, and enter these commands:
prompt> chmod a+x filename prompt> ./filename In the preceding commands, If you want to create an installation log, use the
prompt> ./filename -log=C:\logs\server_install.log
|
After the installation program has finished loading, you will see the standard Welcome window.
Click Next.
In the Choose Home Directory window, you can specify either an existing ORACLE_CEP_HOME directory or create a new one.
The ORACLE_CEP_HOME directory is the main installation directory for Oracle CEP, such as c:\oracle_cep. You can have one or many ORACLE_CEP_HOME directories on your computer, whichever suits your development and production environments best.
If you decide to install into an existing ORACLE_CEP_HOME directory, the installer program checks if the directory includes the version of JRockit required by this release of Oracle CEP:
If it finds the required JRockit installation, it does not install a new one.
If it does not find an appropriate JRockit installation, then the program installs its own version in the ORACLE_CEP_HOME directory.
Use the Browse button to browse your computer for an existing or new ORACLE_CEP_HOME directory.
Click Next.
In the Choose Install Type window, you can choose whether to install the complete version of Oracle CEP or whether you want to pick the individual components of the product that you want to install.
Caution:
By default, the complete installation does not include the product samples. If you want to install the samples (recommended), choose the Custom option.Click Next.
If you chose Custom in the preceding step:
You will see the Choose Products and Components window. Check the components you want to install, such as the product samples.
In the JDK Selection window, select the JDKs you want to install for use with Oracle CEP. Use the Browse button to find other JDKs installed in different directories.
Click Next.
In the Choose Product Installation Directories window, you can change the default name of the home directory of Oracle CEP, ocep_11.1.
Although you can name this directory anything you want, Oracle recommends that you use the default name for clarity and standardization. For example, the documentation assumes that you install into the ocep_11.1 directory.
Click Next.
If you are installing on Windows, and you logged in as a user with Administrator privileges, then you will see the Choose Shortcut Location window where you can choose where you want the Start Menu folder to appear. The following table describes the options available:
| If you select . . . | The following occurs . . . |
|---|---|
| All Users | Recommended. All users registered on the machine are provided with access to the installed software. Subsequently, if users without Administrator privileges use the Configuration Wizard from this installation to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired. |
| Local user | Other users registered on this machine will not have access to the Start menu entries for this installation. |
If you logged in as a user without Administrator privileges, the Start menu entries are created in your user's local Start menu folder.
Click Next.
The Installation Summary window shows the products and components you are about to install, along with the approximate size in MB. This window is for your information only; to change the components to be installed, use the Previous button to return to the appropriate window.
Click Next.
The installer program installs Oracle CEP. The Installation Complete window indicates that the product was installed successfully.
Click Done to exit the program.
Review the post-installation steps that Section 2.7, "Post-Installation Steps" describes.
Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX or Windows system.
When installing in console-mode, respond to the prompts in each section by entering the number associated with your choice or by pressing Enter to accept the default. To exit the installation process, enter exit (or x, for short) in response to any prompt. To review or change your selection, enter previous (or p, for short) at the prompt. To proceed to the following window, enter next (or n, for short).
Note:
In the following procedure, Windows conventions (such as back-slashes in pathnames) are used, for example,C:\oracle_cep\ocep_11.1. When entering pathnames on a UNIX system, be sure to use UNIX conventions, instead. For example, use forward slashes in pathnames, such as /oracle_cep/ocep_11.1.To install Oracle CEP in console mode:
Log in to the Windows or UNIX computer on which you want to install Oracle CEP.
Be sure you log in to the computer as the user that will be the main administrator of the Oracle CEP installation.
Download the product distribution file for the platform on which you want to install Oracle CEP.
Launch the installation program in console mode using the commands listed in the following table appropriate for your platform.
| Platform | Instructions |
|---|---|
| Windows | Open a command window, change to the download directory, and enter the following command:
prompt> filename -mode=console
In the preceding command, If you want to create an installation log, use the
prompt> filename -mode=console -log=C:\logs\server_install.log
|
| Linux or Solaris | Open a command window, change to the download directory, and enter these commands:
prompt> chmod a+x filename prompt> ./filename -mode=console In the preceding commands, If you want to create an installation log, use the
prompt> ./filename -mode=console -log=C:\logs\server_install.log
|
At the Welcome prompt, type next (or n for short) or press Enter to continue with the installation process.
In the Choose Home Directory window, the list of known home directories (if any) appear, as well as an option to create a new one.
The ORACLE_CEP_HOME directory is the main Oracle CEP installation directory, such as c:\oracle_cep. You can have one or many ORACLE_CEP_HOME directories on your computer, whichever suits your development and production environments best.
If you decide to install into an existing ORACLE_CEP_HOME directory, the installer program checks if the directory includes the version of JRockit required by this release of Oracle CEP:
If it finds the required JRockit installation, it does not install a new one.
If it does not find an appropriate JRockit installation, then the program installs its own version in the ORACLE_CEP_HOME directory.
Type 1 to create a new ORACLE_CEP_HOME directory, or type the number of the existing ORACLE_CEP_HOME directory.
If you chose 1 to create a new ORACLE_CEP_HOME directory, the installation program guides you through the required steps to create the new ORACLE_CEP_HOME.
Be sure to enter the full path of the ORACLE_CEP_HOME directory, for example C:\oracle_cep2.
If you specify a directory that does not exist, the installation program creates it for you.
In the Choose Install Type window, you can choose whether to install the complete version of Oracle CEP or whether you want to pick the individual components of the product that you want to install.
Enter 1 for a complete install or 2 for a custom install.
Caution:
By default, the complete installation does not include the product samples. If you want to install the samples (recommended), choose the Custom option (2).If you chose Custom in the preceding step, you will see the Choose Components to Install window.
Enter the numbers in brackets to toggle the components you want to install, such as the samples.
Enter next (or n) when you have chosen the components.
In the Choose Product Installation Directories, you can change the default name of the home directory of Oracle CEP, ocep_11.1, by entering a new value.
Although you can name this directory anything you want, Oracle recommends that you use the default name for clarity and standardization. For example, the documentation assumes that you install into the ocep_11.1 directory.
Enter next (or n) when you are done.
If you are installing on Windows, and you logged in as a user with Administrator privileges, then you will see the Choose Shortcut Location window where you can choose where you want the Start Menu folder to appear. The following table describes the options available:
| If you select . . . | The following occurs . . . |
|---|---|
| 1 "All Users" | Recommended. All users registered on the machine are provided with access to the installed software. Subsequently, if users without Administrator privileges use the Configuration Wizard from this installation to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired. |
| 2 "Local user" | Other users registered on this machine will not have access to the Start menu entries for this installation. |
If you logged in as a user without Administrator privileges, the Start menu entries are created in your user's local Start menu folder.
Enter the appropriate number.
The installer program installs Oracle CEP. The Installation Complete window indicates that the product was installed successfully.
Type exit to exit the program.
Review the post-installation steps that Section 2.7, "Post-Installation Steps" describes.
Silent-mode installation is a non-interactive method of installing your software that requires the use of an XML properties file for selecting installation options.
To install Oracle CEP in silent mode:
Log in to the Windows or UNIX computer on which you want to install Oracle CEP.
Be sure you log in to the computer as the user that will be the main administrator of the Oracle CEP installation.
Download the product distribution file for the platform on which you want to install Oracle CEP.
Create a silent.xml file that defines the configuration settings normally entered by a user during an interactive installation process.
See Section 2.5.1, "Creating a silent.xml File for Silent-Mode Installation."
Note:
Incorrect entries in thesilent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you launch the installation program.Launch the installation program in silent mode using the commands in the following table appropriate for your platform.
| Platform | Instructions |
|---|---|
| Windows | Open a command window, change to the download directory, and enter the following command:
prompt> filename -mode=silent -silent_xml=path_to_xml_file In the preceding command, If you want to create an installation log, use the prompt> filename -mode=silent -silent_xml=path_to_xml_file -log=C:\logs\server_install.log |
| Linux or Solaris | Open a command window, change to the download directory, and enter these commands:
prompt> chmod a+x filename prompt> ./filename -mode=silent -silent_xml=path_to_xml_file In the preceding commands, If you want to create an installation log, use the prompt> ./filename -mode=silent -silent_xml=path_to_xml_file -log=C:\logs\server_install.log |
An Oracle Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
The installation is complete when the Oracle Installer window disappears.
See Section 2.5.3, "Returning Exit Codes to the Command Window" for getting information about the success or failure of the silent installation.
Review the post-installation steps that Section 2.7, "Post-Installation Steps" describes.
When you install Oracle CEP in silent mode, the installation program uses an XML file (silent.xml) to determine which installation options should be implemented.
To create a silent.xml file for silent-mode installation:
Using your favorite text editor, create an empty file called silent.xml on the computer on which you want to install Oracle CEP in silent mode.
Copy the contents of the sample XML file, shown in Example 2-1, into your own silent.xml file.
Example 2-1 Sample silent.xml File for Silent-Mode Installation
<?xml version="1.0" encoding="UTF-8"?>
<!-- Silent installer option: -mode=silent -silent_xml=C:\oracle\silent.xml -->
<bea-installer>
<input-fields>
<data-value name="BEAHOME" value="C:\oracle_cep" />
<data-value name="USER_INSTALL_DIR" value="C:\oracle_cep\ocep_11.1" />
<data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"/>
<data-value name="COMPONENT_PATHS" value="Oracle Complex Event Processing" />
</input-fields>
</bea-installer>
In the silent.xml file you just created, edit the values for the keywords shown in Table 2-1 to reflect your configuration.
For example, if you want to install into the ORACLE_CEP_HOME directory e:\oracle_cep, update the corresponding <data-value> element as follows
<data-value name="BEAHOME" value="e:\oracle_cep" />
Table 2-1 Values for the silent.xml File
| For this data-value name... | Enter the following value... |
|---|---|
BEAHOME |
The full pathname for the |
USER_INSTALL_DIR |
The full pathname for the directory where you want to install your Oracle CEP software. |
INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER |
Windows only. Specify:
The user performing the installation must have Administrator privileges to install the Start menu shortcuts in the All Users folder. The default value for this parameter, if you do not specify it, is |
COMPONENT_PATHS |
Specify the components and subcomponents of Oracle CEP you want to install on your system. Use the following values:
For additional information about entering these values, see Section 2.5.2, "Guidelines for Component Selection." If you do not include the |
Save the file in the directory of your choice.
Use the following guidelines when you specify values for the COMPONENT_PATHS data-value name:
When you specify a product component to be installed, all subcomponents that are installed by default in a complete installation are also installed. For example, the following entry installs both Oracle CEP and the samples:
<data-value name="COMPONENT_PATHS" value="Oracle Complex Event Processing" />
To install multiple components or subcomponents, separate the components with a bar (|). Do not leave a space before or after the bar.
To specify subcomponents, you must specify a component/subcomponent combination for each entry. For example, to explicitly install Oracle CEP and the samples, enter the following line in the file:
<data-value name="COMPONENT_PATHS" value="Oracle Complex Event Processing/Event Server|Oracle Complex Event Processing/Event Server Samples" />
Note:
Because this release of Oracle CEP includes only the server itself and samples, the preceding example is equivalent to the example in the first bullet.When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation. These exit codes are shown in Table 2-2.
| Code | Description |
|---|---|
|
0 |
Installation completed successfully |
|
-1 |
Installation failed due to a fatal error |
|
-2 |
Installation failed due to an internal XML parsing error |
Example 2-2 provides a sample Windows command file that invokes the installation program in silent mode and echoes the exit codes to the command window from which the script is executed.
Example 2-2 Sample Windows Command File Displaying Silent-Mode Exit Codes
rem Execute the installer in silent mode @echo off ofm_ocep_generic_11.1.1.1.0_32_disk1_1of1.exe -mode=silent -silent_xml=C:\downloads\silent.xml -log=C:\logs\products_silent.log @rem Return an exit code to indicate success or failure of installation set exit_code=%ERRORLEVEL% @echo. @echo Exitcode=%exit_code% @echo. @echo Exit Code Key @echo --------------- @echo 0=Installation completed successfully @echo -1=Installation failed due to a fatal error @echo -2=Installation failed due to an internal XML parsing error @echo.
Using the Oracle Smart Update tool, you can locate, install, and activate maintenance and security updates for Oracle CEP.
For more information, see Oracle Smart Update Installing Patches and Maintenance Packs.
Try out the product examples. For information about the examples and how to run them, see Chapter 3, "Oracle CEP Samples."
Create your own Oracle CEP domain:
See:
"Creating an Oracle CEP Standalone-Server Domain" in the Oracle CEP Administrator's Guide
"Creating an Oracle CEP Multi-Server Domain" in the Oracle CEP Administrator's Guide
Create an Oracle CEP application and deploy it to your new domain.
For a description of the programming model, details about the various components that make up an application, and how they all fit together, see "Overview of Creating Oracle CEP Applications" in the Oracle CEP IDE Developer's Guide for Eclipse.
Upgrading to Oracle CEP Release 11gR1 (11.1.1) is a two-step process: first you must upgrade your applications and then you must upgrade the domain to which the applications are deployed.
Table 2-3 lists the steps you must take for each supported upgrade path:
| From Release | To Release 10.3 | To Release 11gR1 (11.1.1) |
|---|---|---|
|
2.0 |
||
|
10.3 |
Not Applicable. |
For more information, see Section 2.8.5, "Backward Compatibility Issues".
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 /bea/user_projects/domains/mydomain20 directory.
To upgrade a WebLogic Event Server 2.0 domain to Oracle CEP 10.3:
Using the Configuration Wizard, create a temporary Oracle CEP 10.3 domain. Later steps in this procedure require you to use or refer to files in a new Oracle CEP 10.3 domain, and it is best to use a new domain. You can later delete this domain if you want.
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 /oracle_cep/user_projects/domains/mydomain30/defaultserver directory.
See "Creating an Oracle CEP Standalone-Server Domain" in the Oracle CEP Administrator's Guide.
If the WebLogic Event Server 2.0 server is currently running, stop it.
Make a backup copy of your WebLogic Event Server 2.0 domain in case you need to revert back.
Replace the following two files in the WebLogic Event Server 2.0 domain with the equivalent files from the Oracle CEP 10.3 domain.
lib/XACMLAuthorizerInit.ldift
lib/XACMLRoleMapperInit.ldift
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 server directory under the domain directory (/oracle_cep/user_projects/domains/mydomain30/defaultserver in our example).
Using your favorite text editor, open the atnstore.txt file in the WebLogic Event Server 2.0 domain, located in the config sub-directory of the main domain directory, and add the new Oracle 10.3 groups:
group: wlevsDeployers description: group: wlevsApplicationAdmins description: group: wlevsBusinessUsers description: group: wlevsOperators description:
Remove the following files and directories (if they exist) in the WebLogic Event Server 2.0 domain:
FileBasedDefaultCredentialMappermy-realmInit.initialized
FileBasedXACMLAuthorizermy-realmInit.initialized
FileBasedXACMLRoleMappermy-realmInit.initialized
rm
cm
atz
Update the startwlevs.cmd (Windows) or startwlevs.sh (Unix) command scripts in the WebLogic Event Server 2.0 domain to point to the new Oracle 10.3 binaries.
Update the stopwlevs.cmd (Windows) or stopwlevs.sh (Unix) command scripts in the WebLogic Event Server 2.0 domain to point to the new Oracle 10.3 binaries.
Start the server in the 2.0 domain using the Oracle 10.3 binaries.
"Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain" in the Oracle CEP Administrator's Guide.
This upgrade procedure might have changed the security configuration of your 2.0 domain, especially if you created new users and assigned them to groups. If this is the case, use Visualizer to reconfigure the security.
See:
"Security Tasks" in the Oracle CEP Visualizer User's Guide
"Configuring Security for Oracle CEP" in the Oracle CEP Administrator's Guide
This section describes the steps you must take to upgrade an Oracle CEP 10.3 domain so that it runs correctly in Oracle CEP Release 11gR1 (11.1.1). For clarity, it is assumed that the existing Oracle CEP 10.3 domain is located in the /bea/user_projects/domains/mydomain103 directory.
To upgrade an Oracle CEP 10.3 domain to Oracle CEP release 11gR1 (11.1.1):
Using the Configuration Wizard, create a temporary Oracle CEP Release 11gR1 (11.1.1) domain. Later steps in this procedure require you to use or refer to files in a new Oracle CEP Release 11gR1 (11.1.1) domain, and it is best to use a new domain. You can later delete this domain if you want.
For the purposes of this procedure, it is assumed that the new Oracle CEP Release 11gR1 (11.1.1) domain is called mydomain11, it contains a single server called defaultserver, and the server files are located in the /oracle_cep/user_projects/domains/mydomain11/defaultserver directory.
See "Creating an Oracle CEP Standalone-Server Domain" in the Oracle CEP Administrator's Guide.
If the WebLogic Event Server 10.3 server is currently running, stop it.
Make a backup copy of your WebLogic Event Server 10.3 domain in case you need to revert back.
Replace the following two files in the WebLogic Event Server 10.3 domain with the equivalent files from the Oracle CEP Release 11gR1 (11.1.1) domain.
lib/XACMLAuthorizerInit.ldift
lib/XACMLRoleMapperInit.ldift
The WebLogic Event Server 10.3 files are located relative to the domain directory (/bea/user_projects/domains/mydomain30 in our example) and the Oracle CEP Release 11gR1 (11.1.1) files are located relative to the server directory under the domain directory (/oracle_cep/user_projects/domains/mydomain11/defaultserver in our example).
Using your favorite text editor, open the atnstore.txt file in the WebLogic Event Server 10.3 domain, located in the config sub-directory of the main domain directory, and add the new Oracle Release 11gR1 (11.1.1) groups:
group: wlevsDeployers description: group: wlevsApplicationAdmins description: group: wlevsBusinessUsers description: group: wlevsOperators description:
Remove the following files and directories (if they exist) in the WebLogic Event Server 10.3 domain:
FileBasedDefaultCredentialMappermy-realmInit.initialized
FileBasedXACMLAuthorizermy-realmInit.initialized
FileBasedXACMLRoleMappermy-realmInit.initialized
rm
cm
atz
Update the startwlevs.cmd (Windows) or startwlevs.sh (Unix) command scripts in the WebLogic Event Server 10.3 domain to point to the new Oracle Release 11gR1 (11.1.1) binaries.
Update the stopwlevs.cmd (Windows) or stopwlevs.sh (Unix) command scripts in the WebLogic Event Server 10.3 domain to point to the new Oracle Release 11gR1 (11.1.1) binaries.
Start the server in the 10.3 domain using the Oracle Release 11gR1 (11.1.1) binaries.
"Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain" in the Oracle CEP Administrator's Guide.
This upgrade procedure might have changed the security configuration of your 10.3 domain, especially if you created new users and assigned them to groups. If this is the case, use Visualizer to reconfigure the security.
See:
"Security Tasks" in the Oracle CEP Visualizer User's Guide
"Configuring Security for Oracle CEP" in the Oracle CEP Administrator's Guide
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.
To upgrade a WebLogic Event Server 2.0 application to run on Oracle CEP 10.3:
Update the MANIFEST.MF file to import new versions of Spring framework and Oracle CEP packages, as well as new required packages. In particular:
Update the version of all imported Spring framework packages to 2.5.5. For example:
Import-Package:
org.springframework.aop.framework;version="2.5.5",
org.springframework.aop;version="2.5.5",
...
Update the version of any imported Oracle CEP packages to 3.0.0.0. For example:
Import-Package:
com.bea.wlevs.ede;version="3.0.0.0",
com.bea.wlevs.ede.api;version="3.0.0.0",
...
Add the following packages to the Import-Package header if they are not already included:
Import-Package:
com.bea.wlevs.management.configuration.spi;version="3.0.0.0",
com.bea.wlevs.management.spi;version="3.0.0.0",
com.bea.wlevs.monitor;version="3.0.0.0",
com.bea.wlevs.spi;version="3.0.0.0",
com.bea.wlevs.spring.support;version="3.0.0.0",
commonj.work;version="1.4.0.0",
org.springframework.osgi.extensions.annotation;version="1.1.0",
com.bea.wlevs.ede.spi;version="3.0.0.0",
com.bea.wlevs.configuration.internal;version="3.0.0.0",
...
If you use Spring or Spring Dynamic Modules for OSGI (Spring DM) features in your application, it is possible that the declaration of the features in the Spring application context file has changed. If this is the case, you must update these declarations in the EPN assembly file of your Oracle CEP application.
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 upgradeRefer to the appropriate 2.5 XSD Schemas for any changes:
Spring: http://www.springframework.org/schema/beans/spring-beans.xsd
Spring DM: http://www.springframework.org/schema/osgi/spring-osgi.xsd
The following bullets list some of the typical changes you might have to make; the following list is not complete:
When specifying a property to the <osgi:service-property> tag, use the <entry> tag with the key and value attributes, rather than the old <prop> tag.
For example, change the following 2.0 tag from:
<osgi:service-properties>
<prop key="type">SocketAdapterType</prop>
</osgi:service-properties>
To:
<osgi:service-properties>
<entry key="type" value="SocketAdapterType"/>
</osgi:service-properties>
The value or ref attribute 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, change the following 2.0 tag from:
<wlevs:adapter id="fileAdapter" provider="FileAdapterType">
<!-- file: empty value uses default
<wlevs:instance-property name="file" value="" />
<wlevs:listener ref="algoTradingProcessor"/>
</wlevs:adapter>
To:
<wlevs:adapter id="fileAdapter" provider="FileAdapterType">
<wlevs:instance-property name="file" value="test.file" />
<wlevs:listener ref="algoTradingProcessor"/>
</wlevs:adapter>
Recompile the Java code of your 2.0 adapter and business POJO implementations using your IDE. If you get compile-time errors, check the latest 10.3 Javadoc (http://download.oracle.com/docs/cd/E13157_01/wlevs/docs30/javadocs/wlevs/index.html) that describe the new Oracle CEP APIs and make the appropriate source code changes.
If your 2.0 application has an adapter that uses the loadgen provider as Example 2-3 shows, then you must register a StockTick event type in your EPN assembly file as Example 2-4 shows.
After you have made the preceding changes, reassemble the application and deploy it to Oracle CEP 10.3.
See "Assembling and Deploying Oracle CEP Applications" in the Oracle CEP IDE Developer's Guide for Eclipse.
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 an application that you developed in Oracle CEP 10.3 so that it runs on Oracle CEP Release 11gR1 (11.1.1).
To upgrde an Oracle CEP 10.3 application to run on Oracle CEP release 11gR1 (11.1.1):
Update the MANIFEST.MF file to import new versions of Spring framework and Oracle CEP packages, as well as new required packages.
Note that alternatively you can specify unversioned packages which will not require updating and also that you can specify larger versions in order to avoid minor version updates, that is, use "2.5" instead of "2.5.6".
In particular:
Update the version of all imported Spring framework packages to 2.5.6. For example:
Import-Package:
org.springframework.aop.framework;version="2.5.6",
org.springframework.aop;version="2.5.6",
...
Update the version of all imported Spring-DM framework packages to 1.2.0. For example:
Import-Package:
org.springframework.osgi.context="1.2.0",
...
Update the version of any imported Oracle CEP packages to 11.1.1.1_0. For example:
Import-Package:
com.bea.wlevs.ede;version="11.1.1.1_0",
com.bea.wlevs.ede.api;version="11.1.1.1_0",
...
Add the following packages to the Import-Package header if they are not already included (see the sample source for a complete list of headers that may be required):
Import-Package:
com.bea.wlevs.management.spi;version="11.1.1.1_0",
com.bea.wlevs.spring.support;version="11.1.1.1_0",
com.bea.wlevs.ede.spi;version="11.1.1.1_0",
org.springframework.osgi.extensions.annotation;version="1.2.0",
...
If you use Spring or Spring Dynamic Modules for OSGI (Spring DM) features in your application, it is possible that the declaration of the features in the Spring application context file has changed. If this is the case, you must update these declarations in the EPN assembly file of your Oracle CEP application.
Note:
This change is a result of the upgrade of the Spring-DM framework (from 1.1 to 1.2) that occurred between Oracle CEP 10.3 and Oracle CEP 11.1, not as a direct result of the Oracle CEP upgrade.Refer to the appropriate 2.5 XSD Schemas for any changes:
Spring: http://www.springframework.org/schema/beans/spring-beans.xsd
Spring DM: http://www.springframework.org/schema/osgi/spring-osgi.xsd
In particular convert any Spring-DM declared adapter factories to use the <wlevs:factory/> tag instead. For example, if your 10.3 EPN assembly file contains the service that Example X shows, then you must replace this service with the wlevs:factory that Example Y shows.
Example 2-5 Spring-DM Declared Adapter Factory
<osgi:service interface="com.bea.wlevs.ede.api.AdapterFactory">
<osgi:service-properties>
<entry key="type" value="SocketAdapterType"/>
</osgi:service-properties>
<bean class="com.bea.wlevs.example.algotrading.adapter.SocketAdapterFactory" />
</osgi:service>
Recompile the Java code of your 10.3 adapter and business POJO implementations using your IDE. If you get compile-time errors, check the latest Release 11gR1 (11.1.1) Javadoc (see Oracle CEP Java API Reference) that describe the new Oracle CEP APIs and make the appropriate source code changes.
Consider changing deprecated Java API and Oracle CEP schema as the Oracle CEP Release Notes describe.
After you have made the preceding changes, reassemble the application and deploy it to Oracle CEP Release 11gR1 (11.1.1).
See "Assembling and Deploying Oracle CEP Applications" in the Oracle CEP IDE Developer's Guide for Eclipse.
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.
The following are non-backward compatible changes in the management framework:
The following classes have been deprecated and removed from all operation signatures:
com.bea.wlevs.management.ManagementException
com.bea.wlevs.management.ManagementRuntimeException
com.bea.wlevs.management.MbeanOperationsException
The following methods have been removed from all MBeans: isRegistered(), preRegister(), postRegister(), getMBeanInfo().
The monitoring-related methods have been removed from StageMBean and replaced by com.bea.wlevs.monitor.management.MonitorRuntimeMBean.
The com.bea.wlevs.management.boot.BootMBean has been removed.
The com.bea.wlevs.management.configuration.ConfigSessionBean has been removed.
The ObjectName for the AppDeploymentMBean has been changed to include the DomainMBean as a parent.
The class com.bea.wlevs.server.management.mbean.ServerRuntimeMBean has been changed to com.bea.wlevs.management.runtime.ServerRuntimeMBean.
Two additional modules have been added: com.bea.wlevs.management.api_* and com.bea.wlevs.management.spi_*, in addition to the existing com.bea.wlevs.management_*.
The service com.bea.wlevs.spi.ManagementService has been moved from bundle com.bea.wlevs.spi_* to com.bea.wlevs.management.spi_*.