2 Installing Oracle CEP

2.5.1 Creating a silent.xml File for Silent-Mode Installation

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:

1. 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.

2. 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>
   

3. 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 ORACLE_CEP_HOME directory of your choice.
   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: true, or yes, to create the shortcuts in the All Users folder. false, or no, to create the shortcuts in the local users folder. 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 true.
   COMPONENT_PATHS	Specify the components and subcomponents of Oracle CEP you want to install on your system. Use the following values: Oracle Complex Event Processing Oracle Complex Event Processing/Event Server Oracle Complex Event Processing/Event Server Samples For additional information about entering these values, see Section 2.5.2, "Guidelines for Component Selection." If you do not include the COMPONENT_PATHS data-value name in the silent.xml file, the complete Oracle CEP product is installed.
   LOCAL_JVMS	Option to select supported JVM, which is already installed. Note: The presence of either(BEA_BUNDLED_JVMS or LOCAL_JVMS) or both of these tokens negates any default selection and only sets the values assigned for these tokens as user selection. The value of the token can be a pipe (|) separated JavaHomes.
   BEA_BUNDLED_JVMS	Specify the BEA-supplied JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol (|). Do not leave a space before or after the bar. Use this option to install Oracle CEP for use with the Oracle JRockit JDK included in the Oracle CEP installer.

   
   

   Note:

   Silent install does not support the LOCAL_JVMS data-value. To define a local JVM, you must use graphical mode installation as Section 2.3, "Installing Oracle CEP in Graphical Mode" describes.

4. Save the file in the directory of your choice.

2.5.2 Guidelines for Component Selection

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.

2.5.3 Returning Exit Codes to the Command Window

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.

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.

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.

2.7.1 Configuring Oracle CEP for the Sun JDK

If you installed Oracle CEP for use with the Sun JDK, you must make changes to the setDomainEnv and startwlevs scripts in each Oracle CEP domain directory. This section describes:

• Section 2.7.1.1, "How to Configure Oracle CEP for the Sun JDK on Windows"

• Section 2.7.1.2, "How to Configure Oracle CEP for the Sun JDK on Linux"

2.7.2 Configuring Oracle CEP for the IBM JDK

If you installed Oracle CEP for use with the IBM JDK, depending on your operating system and processor architecture, you must make changes to the IBM AIX network options and the setDomainEnv script in each Oracle CEP domain directory. This section describes:

• Section 2.7.2.1, "How to Configure Oracle CEP for the IBM JVM on IBM AIX (64-bit)"

2.8.1 Upgrading a WebLogic Event Server 2.0 Domain to Oracle CEP 10.3

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:

1. 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.

2. If the WebLogic Event Server 2.0 server is currently running, stop it.

3. Make a backup copy of your WebLogic Event Server 2.0 domain in case you need to revert back.

4. 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).

5. 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:
   

6. 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

7. 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.

8. 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.

9. 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.

10. 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

2.8.2 Upgrading an Oracle CEP 10.3 Domain to Oracle CEP 11g Release 1 (11.1.1)

This section describes the steps you must take to upgrade an Oracle CEP 10.3 domain so that it runs correctly in Oracle CEP 11g Release 1 (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):

1. Using the Configuration Wizard, create a temporary Oracle CEP 11g Release 1 (11.1.1) domain. Later steps in this procedure require you to use or refer to files in a new Oracle CEP 11g Release 1 (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 11g Release 1 (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.

2. If the WebLogic Event Server 10.3 server is currently running, stop it.

3. Make a backup copy of your WebLogic Event Server 10.3 domain in case you need to revert back.

4. Replace the following two files in the WebLogic Event Server 10.3 domain with the equivalent files from the Oracle CEP 11g Release 1 (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 11g Release 1 (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).

5. 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 11g Release 1 (11.1.1) groups:

   group: wlevsDeployers
   description:
   group: wlevsApplicationAdmins
   description:
   group: wlevsBusinessUsers
   description:
   group: wlevsOperators
   description:
   

6. 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

7. 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 11g Release 1 (11.1.1) binaries.

8. 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 11g Release 1 (11.1.1) binaries.

9. Start the server in the 10.3 domain using the Oracle 11g Release 1 (11.1.1) binaries.

   "Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain" in the Oracle CEP Administrator's Guide.

10. 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

2.8.3 Upgrading a WebLogic Event Server 2.0 Application to Run on Oracle CEP 10.3

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:

1. 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",
         ...
     

2. 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 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

   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>
     

3. 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.

4. 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.

   Example 2-3 Adapter Using loadgen Provider

   <wlevs:adapter id="fxMarketAmer" provider="loadgen">
       <wlevs:instance-property name="port" value="9011"/>
   </wlevs:adapter>
   

   Example 2-4 Registering a StockTick Event

   <wlevs:event-type-repository>
       <wlevs:event-type type-name="StockTick">
           <wlevs:class>com.bea.wlevs.adapter.defaultprovider.StockTickEvent</wlevs:class>
       </wlevs:event-type>
   </wlevs:event-type-repository>
   

5. 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 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.

2.8.4 Upgrading an Oracle CEP 10.3 Application to Run on Oracle CEP 11g Release 1 (11.1.1)

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 11g Release 1 (11.1.1).

To upgrade an Oracle CEP 10.3 application to run on Oracle CEP release 11gR1 (11.1.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",
         ...
     

2. 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 2-5 shows, then you must replace this service with the wlevs:factory that Example 2-6 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>
   

   Example 2-6 wlevs:factory

   <wlevs:factory provider-name="SocketAdapterType"     class="com.bea.wlevs.example.algotrading.adapter.SocketAdapterFactory"/>
   

3. 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 11g Release 1 (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.

4. After you have made the preceding changes, reassemble the application and deploy it to Oracle CEP 11g Release 1 (11.1.1).

   See "Assembling and Deploying Oracle CEP Applications" in the Oracle CEP 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.

2.8.5 Backward Compatibility Issues

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_*.