Contents

List of Examples

List of Figures

List of Tables

Title and Copyright Information

Preface

Audience

Documentation Accessibility

Related Documents

Conventions

Part I Overview

1 Overview of Oracle CEP Server Administration

1.1 Understanding Oracle CEP Servers and Domains

1.2 Understanding Oracle CEP Server Lifecycle

1.2.1 User Action: Start Oracle CEP Server

1.2.2 User Action: Stop Oracle CEP Server

1.3 Understanding Oracle CEP Server Configuration

1.3.1 Oracle CEP Server Configuration Files

1.3.2 Configuring an Oracle CEP Server by Manually Editing the config.xml File

1.3.3 Configuration History Management

1.3.4 Configuring the Oracle CEP Server bootclasspath

1.3.4.1 How to Configure the Oracle CEP Server bootclasspath

1.4 Understanding Oracle CEP Server Administration Tools

1.4.1 Configuration Wizard

1.4.2 Oracle CEP Visualizer

1.4.3 wlevs.Admin Command-Line Utility

1.4.4 Deployer Command-Line Utility

1.4.5 Security Command-Line Utilities

1.4.6 JMX

1.5 Understanding Oracle CEP Server Administration Tasks

1.5.1 Creating Oracle CEP Servers and Domains

1.5.2 Updating Oracle CEP Servers and Domains

1.5.3 Configuring Oracle CEP Servers

1.5.4 Starting and Stopping Oracle CEP Servers

1.5.5 Deploying Applications to Oracle CEP Servers

1.5.6 Managing Oracle CEP Applications, Servers, and Domains

Part II Standalone-Server Domains

2 Introduction to Standalone-Server Domains

2.1 Overview of Oracle CEP Standalone-Server Domain Administration

2.2 Scalability and Oracle CEP Standalone-Server Domain

2.3 Next Steps

3 Administrating Oracle CEP Standalone-Server Domains

3.1 Creating an Oracle CEP Standalone-Server Domain

3.1.1 Creating an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode

3.2 Updating an Oracle CEP Standalone-Server Domain

3.2.1 How to Update an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode

3.3 Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain

3.3.1 How to Start an Oracle CEP Standalone-Server Using the startwlevs Script

3.3.2 How to Stop an Oracle CEP Standalone-Server Using the stopwlevs Script

4 Deploying Applications to Standalone-Server Domains

4.1 Deploying an Application to an Oracle CEP Standalone-Server Domain

4.1.1 How to Deploy an Application to an Oracle CEP Standalone-Server Using the Oracle CEP Visualizer

4.1.2 How to Deploy an Application to an Oracle CEP Singleton Server Group Using the Deployer Utility

Part III Multi-Server Domains

5 Introduction to Multi-Server Domains

5.1 Overview of Oracle CEP Multi-Server Domain Administration

5.1.1 Oracle Coherence Clustering

5.1.2 Oracle CEP Native Clustering

5.2 Groups

5.2.1 Singleton Server Deployment Group

5.2.2 Domain Deployment Group

5.2.3 Custom Deployment Groups

5.3 Multi-Server Notifications and Messaging

5.4 Multi-Server Domain Directory Structure

5.5 Order of cluster Element Child Elements

5.6 High Availability and Multi-Server Domains

5.7 Scalability and Multi-Server Domains

5.8 Next Steps

6 Administrating Multi-Server Domains With Oracle Coherence

6.1 Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence

6.1.1 How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence

6.1.2 How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence

6.1.3 Configuring the Oracle Coherence Cluster

6.1.3.1 The tangosol-coherence-override.xml File

6.2 Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence

6.2.1 How to Update an Oracle CEP Multi-Server Domain Using the Configuration Wizard in Graphical Mode

6.3 Securing the Messages Sent Between Servers in a Multi-Server Domain

6.3.1 How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence

6.4 Using the Multi-Server Domain APIs to Manage Group Membership Changes

6.5 Starting and Stopping an Oracle CEP Server in a Multi-Server Domain

7 Administrating Multi-Server Domains With Oracle CEP Native Clustering

7.1 Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering

7.1.1 How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle CEP Native Clustering

7.1.2 How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle CEP Native Clustering

7.2 Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering

7.2.1 How to Update an Oracle CEP Multi-Server Domain Using the Configuration Wizard in Graphical Mode

7.3 Securing the Messages Sent Between Servers in a Multi-Server Domain

7.3.1 How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering

7.4 Using the Multi-Server Domain APIs to Manage Group Membership Changes

7.5 Starting and Stopping an Oracle CEP Server in a Multi-Server Domain

8 Deploying Applications to Multi-Server Domains

8.1 Overview of Deploying an Application to an Oracle CEP Multi-Server Domain

8.2 Deploying to an Oracle CEP Server Using the Oracle CEP Visualizer

8.3 Deploying to an Oracle CEP Server Singleton Group Using the Deployer Utility

8.4 Deploying to an Oracle CEP Server Domain Group Using the Deployer Utility

8.5 Deploying to an Oracle CEP Server Custom Group Using the Deployer Utility

8.6 Troubleshooting Multi-Server Domain Deployment

8.6.1 Oracle CEP Server Stops Application After Deployment

Part IV Configuring Services

9 Configuring Network I/O for Oracle CEP

9.1 Overview of Network I/O in Oracle CEP

9.1.1 Network I/O Providers

9.1.2 IPv4 and IPv6 Support

9.2 Configuring Network I/O Server (netio)

9.2.1 How to Configure Network I/O Server

9.3 Configuring Network I/O Client (netio-client)

9.3.1 How to Configure Network IO Client

10 Configuring Security for Oracle CEP

10.1 Overview of Security in Oracle CEP

10.1.1 Java SE Security

10.1.2 Security Providers

10.1.3 Users, Groups, and Roles

10.1.4 SSL

10.1.5 FIPS

10.1.6 Enabling and Disabling Security

10.1.7 Security Utilities

10.1.8 Specifying User Credentials When Using the Command-Line Utilities

10.1.9 Security in Oracle CEP Examples and Domains

10.2 Configuring Java SE Security for Oracle CEP Server

10.3 Configuring a Security Provider

10.3.1 Configuring Authentication Using the LDAP Provider and Authorization Using the DBMS Provider

10.3.2 Configuring Both Authentication and Authorization Using the DBMS Provider

10.4 Configuring Password Strength

10.5 Configuring SSL to Secure Network Traffic

10.5.1 How to Configure SSL Manually

10.5.2 How to Create a Key-Store Manually

10.5.3 How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer

10.6 Configuring FIPS for Oracle CEP Server

10.7 Configuring HTTPS-Only Connections for Oracle CEP Server

10.8 Configuring Security for Oracle CEP Server Services

10.8.1 Configuring Jetty Security

10.8.2 Configuring JMX Security

10.8.3 Configuring JDBC Security

10.8.4 Configuring HTTP Publish-Subscribe Server Channel Security

10.9 Configuring Cross-Domain Security for Oracle CEP Visualizer

10.10 Configuring the Oracle CEP Security Auditor

10.11 Disabling Security

11 Configuring Jetty for Oracle CEP

11.1 Overview of Jetty Support in Oracle Complex Event Processing

11.1.1 Servlets

11.1.2 Network I/O Integration

11.1.3 Thread Pool Integration

11.1.4 Jetty Work Managers

11.1.4.1 Understanding How Oracle CEP Uses Thread Pools

11.1.4.2 Understanding Work Manager Configuration

11.2 Configuring a Jetty Server Instance

11.2.1 jetty Configuration Object

11.2.2 netio Configuration Object

11.2.3 work-manager Configuration Object

11.2.4 jetty-web-app Configuration Object

11.2.5 Developing Servlets for Jetty

11.2.6 Web Application Deployment

11.3 Example Jetty Configuration

12 Configuring JMX for Oracle CEP

12.1 Overview of JMX Support in Oracle CEP

12.1.1 Understanding JMX Configuration

12.1.2 Understanding JMX Management

12.1.2.1 Accessing the Oracle CEP JMX Server

12.1.2.2 Accessing Configuration MBeans

12.1.2.3 Accessing Oracle CEP Runtime MBeans

12.1.3 Understanding Oracle CEP MBeans

12.1.3.1 Oracle CEP Configuration MBeans

12.1.3.2 Oracle CEP Runtime MBeans

12.1.3.3 Oracle CEP MBean Hierarchy

12.2 Configuring JMX

12.2.1 jmx Configuration Object

12.2.2 rmi Configuration Object

12.2.3 jndi-context Configuration Object

12.2.4 exported-jndi-context Configuration Object

12.2.5 Example of Configuring JMX

12.3 Managing With JMX

12.3.1 How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client

12.3.2 How to Programmatically Connect to the Oracle CEP JMX Server From an Oracle CEP Client

12.3.3 How to Programmatically Configure an Oracle CEP Component Using JMX APIs

12.3.4 How to Programmatically Monitor the Throughput and Latency of an Oracle CEP Component Using JMX APIs

12.3.5 How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Enabled

12.3.6 How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled

13 Configuring JDBC for Oracle CEP

13.1 Overview of Database Access from an Oracle CEP Application

13.1.1 Oracle JDBC Driver

13.1.2 Type 4 JDBC Driver for SQL Server from DataDirect

13.1.3 Supported Databases

13.1.3.1 Databases Supported by the Oracle JDBC Driver

13.1.3.2 Databases Supported by the Type 4 JDBC Driver for SQL Server from DataDirect

13.2 Description of Oracle CEP Data Sources

13.2.1 Default Data Source Configuration

13.2.2 Custom Data Source Configuration

13.2.3 Getting the Native JDBC Connection

13.3 Configuring Access to a Database Using the Oracle JDBC Driver

13.4 Configuring Access to a Database Using the Type 4 JDBC Drivers from Data Direct

13.5 Configuring Access to a Different Database Driver or Driver Version

13.5.1 How to Access a Database Driver Using an Application Library Built With bundler.sh

13.5.2 How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse

13.5.3 How to Access a Database Driver Using bootclasspath

14 Configuring HTTP Publish-Subscribe for Oracle CEP

14.1 Overview of HTTP Publish-Subscribe

14.1.1 How the HTTP Pub-Sub Server Works

14.1.2 HTTP Pub-Sub Server Support in Oracle CEP

14.2 Creating a New HTTP Publish-Subscribe Server

14.3 Configuring an Existing HTTP Publish-Subscribe Server

14.4 Example HTTP Publish-Subscribe Server Configuration

15 Configuring Logging and Debugging for Oracle CEP

15.1 Overview of Logging and Debugging Configuration

15.1.1 Commons Apache Logging Framework

15.1.1.1 Setting the Log Factory

15.1.1.2 Using Log Severity Levels

15.1.1.3 Log Files

15.1.1.4 Log Message Format

15.1.2 OSGi Framework Logger

15.1.3 Log4j Logger

15.1.3.1 Loggers

15.1.3.2 Appenders

15.1.3.3 Layouts

15.2 Configuring the Oracle CEP Logging Service

15.2.1 logging-service

15.2.2 log-file

15.2.3 log-stdout

15.2.4 Configuring Severity for an Individual Module

15.3 Configuring Log4j Logging

15.3.1 Configuring log4j Properties

15.3.2 Configuring Application Manifest

15.3.3 Enabling Log4j Logging

15.3.4 Debugging Log4j Logging

15.4 Using the Apache Commons Logging API

15.5 Configuring Oracle CEP Debugging Options

15.5.1 How to Configure Oracle CEP Debugging Options Using System Properties

15.5.2 How to Configure Oracle CEP Debugging Options Using a Configuration File

Part V References

A wlevs.Admin Command-Line Reference

A.1 Overview of the wlevs.Admin Utility

A.2 Configuring the wlevs.Admin Utility Environment

A.3 Running the wlevs.Admin Utility Remotely

A.4 Running wlevs.Admin Utility in SSL Mode

A.5 Syntax for Invoking the wlevs.Admin Utility

A.5.1 Example Environment

A.5.2 Exit Codes Returned by wlevs.Admin

A.6 Connection Arguments

A.7 User Credentials Arguments

A.8 Common Arguments

A.9 Command for Getting Usage Help

A.9.1 HELP

A.9.1.1 Syntax

A.9.1.2 Example

A.10 Commands for Managing the Server Life Cycle

A.10.1 SHUTDOWN

A.10.1.1 Syntax

A.10.1.2 Example

A.11 Commands for Managing the Oracle CQL Rules of an Application

A.11.1 GETRULE

A.11.1.1 Syntax

A.11.1.2 Example

A.11.2 ADDRULE

A.11.2.1 Syntax

A.11.2.2 Example

A.11.3 DELETERULE

A.11.3.1 Syntax

A.11.3.2 Example

A.11.4 REPLACERULE

A.11.4.1 Syntax

A.11.4.2 Example

A.11.5 STARTRULE

A.11.5.1 Syntax

A.11.5.2 Example

A.11.6 STOPRULE

A.11.6.1 Syntax

A.11.6.2 Example

A.11.7 UPLOAD

A.11.7.1 Syntax

A.11.7.2 Example

A.11.8 DOWNLOAD

A.11.8.1 Syntax

A.11.8.2 Example

A.12 Commands for Managing the EPL Rules of an Application

A.12.1 ADDRULE

A.12.1.1 Syntax

A.12.1.2 Example

A.12.2 DELETERULE

A.12.2.1 Syntax

A.12.2.2 Example

A.12.3 REPLACERULE

A.12.3.1 Syntax

A.12.3.2 Example

A.12.4 GETRULE

A.12.4.1 Syntax

A.12.4.2 Example

A.12.5 ADDPARAMS

A.12.5.1 Syntax

A.12.5.2 Example

A.12.6 DELETEPARAMS

A.12.6.1 Syntax

A.12.6.2 Example

A.12.7 GETPARAMS

A.12.7.1 Syntax

A.12.7.2 Example

A.12.8 UPLOAD

A.12.8.1 Syntax

A.12.8.2 Example

A.12.9 DOWNLOAD

A.12.9.1 Syntax

A.12.9.2 Example

A.13 Commands for Managing Oracle CEP MBeans

A.13.1 Specifying MBean Types

A.13.2 MBean Management Commands

A.13.3 GET

A.13.3.1 Syntax

A.13.3.2 Example

A.13.4 INVOKE

A.13.4.1 Syntax

A.13.4.2 Example

A.13.5 QUERY

A.13.5.1 Syntax

A.13.5.2 Example

A.13.5.3 Querying for Application and Processor Names

A.13.6 SET

A.13.6.1 Syntax

A.13.6.2 Example

A.14 Commands for Controlling Event Record and Playback

A.14.1 STARTRECORD

A.14.1.1 Syntax

A.14.1.2 Example

A.14.2 STOPRECORD

A.14.2.1 Syntax

A.14.2.2 Example

A.14.3 CONFIGURERECORD

A.14.3.1 Syntax

A.14.3.2 Example

A.14.4 SCHEDULERECORD

A.14.4.1 Syntax

A.14.4.2 Example

A.14.5 LISTRECORD

A.14.5.1 Syntax

A.14.5.2 Example

A.14.6 STARTPLAYBACK

A.14.6.1 Syntax

A.14.6.2 Example

A.14.7 STOPPLAYBACK

A.14.7.1 Syntax

A.14.7.2 Example

A.14.8 CONFIGUREPLAYBACK

A.14.8.1 Syntax

A.14.8.2 Example

A.14.9 SCHEDULEPLAYBACK

A.14.9.1 Syntax

A.14.9.2 Example

A.14.10 LISTPLAYBACK

A.14.10.1 Syntax

A.14.10.2 Example

A.15 Commands for Monitoring Throughput and Latency

A.15.1 MONITORAVGLATENCY

A.15.1.1 Syntax

A.15.1.2 Example

A.15.2 MONITORAVGLATENCYTHRESHOLD

A.15.2.1 Syntax

A.15.2.2 Example

A.15.3 MONITORMAXLATENCY

A.15.3.1 Syntax

A.15.3.2 Example

A.15.4 MONITORAVGTHROUGHPUT

A.15.4.1 Syntax

A.15.4.2 Example

A.16 Commands for Managing Configuration History

A.16.1 CONFIGHISTORY

A.16.1.1 Syntax

A.16.1.2 Example

A.16.2 DELETECONFIGCHANGEHISTORY

A.16.2.1 Syntax

A.16.2.2 Example

A.16.3 LISTCHANGERECORDS

A.16.3.1 Syntax

A.16.3.2 Example

A.16.4 LISTRESOURCEREVISIONS

A.16.4.1 Syntax

A.16.4.2 Example

A.16.5 UNDOCONFIGCHANGE

A.16.5.1 Syntax

A.16.5.2 Example

B Deployer Command-Line Reference

B.1 Overview of Using the Deployer Command-Line Utility

B.2 Configuring the Deployer Utility Environment

B.3 Running the Deployer Utility Remotely

B.4 Syntax for Invoking the Deployer Utility

B.4.1 Connection Arguments

B.4.2 User Credential Arguments

B.4.3 Deployment Commands

B.5 Examples of Using the Deployer Utility

C Security Utilities Command-Line Reference

C.1 The cssconfig Command-Line Utility

C.1.1 cssconfig Syntax

C.2 The encryptMSAConfig Command-Line Utility

C.2.1 encryptMSAConfig Syntax

C.3 The GrabCert Command-Line Utility

C.3.1 GrabCert Syntax

C.3.2 Examples of Using GrabCert

C.4 The passgen Command-Line Utility

C.4.1 passgen Syntax

C.4.2 Examples of Using passgen

C.4.2.1 Using passgen interactively

C.4.2.2 Providing a Password on the Command Line

C.5 The secgen Command-Line Utility

C.5.1 Generating a File-Based Provider Configuration File

C.5.2 Generating a Key File

C.5.3 Using the secgen Properties File

C.5.4 Examples of Using secgen

C.5.5 Limitations of secgen

Index

List of Examples

1-1 Sample Oracle CEP Server config.xml File

6-1 myServer1 config.xml File

6-2 myServer2 config.xml File

6-3 Server Configuration File config.xml for myServer1

6-4 Server Configuration File config.xml for myServer2

6-5 Server Configuration File config.xml for myServer3

6-6 The cluster Element security Child Element

6-7 The security-config.xml File encryption-service Element

7-1 myServer1 config.xml File

7-2 myServer2 config.xml File

7-3 Server Configuration File config.xml for myServer1

7-4 Server Configuration File config.xml for myServer2

7-5 Server Configuration File config.xml for myServer3

7-6 The cluster Element security Child Element

7-7 The security-config.xml File encryption-service Element

9-1 Oracle CEP netio Element With provider-type Defined

9-2 Oracle CEP netio Element

9-3 Oracle CEP netio Element With name Element

9-4 Oracle CEP netio Element With port Element

9-5 Oracle CEP netio Element With port Element

9-6 Oracle CEP netio-client Element

9-7 Oracle CEP netio-client Element With name Element

9-8 Oracle CEP netio-client Element With port Element

10-1 LDAP/DBMS Properties File

10-2 DBMS Property File

10-3 Default password-validator Element in the security.xml File

10-4 Default ssl Element

10-5 Default netio Element

10-6 Default jetty Element

10-7 Default ssl Element

10-8 Editing java.security to Add jsafejcefips JAR as a JCE Provider

10-9 Making JsafeJCE the Default Provider

10-10 Editing server.config to Enable Fips

10-11 Typical config.xml File With Both HTTP and HTTPS Access

10-12 Typical config.xml File With HTTP Access Removed

10-13 Oracle CEP config.xml File data-source Element After Encryption

10-14 Oracle CEP config.xml File data-source Element After Encryption

10-15 Default sec:auditor Element

11-1 Example Jetty Configuration

12-1 JMX Configuration

12-2 Establishing a Connection to the Oracle CEP JMX Server

12-3 Establishing a Connection to the Oracle CEP JMX Server

12-4 Querying MBeans

12-5 Acquiring an Instance of a MonitorRuntimeMBean

12-6 Acquiring an Instance of ProbeRuntimeMBean

12-7 Unregistering the MBean

13-1 Custom Data Source Configuration in Oracle CEP Server config.xml

13-2 bundler.sh Command Line Options

13-3 Using the Bundler Utility

13-4 Bundle JAR Contents

13-5 Service Registration Log Messages

13-6 driver-params Child Element

13-7 MyActivator Class Implementation

13-8 Un-JAR the Database Driver

13-9 Adding Export-Package to the Manifest Editor

13-10 Adding a Bundle-Activator Element to the Manifest Editor

13-11 Adding a DynamicImport-Package Element to the Manifest Editor

13-12 driver-params Child Element

15-1 Oracle CEP Server config.xml File With Logging Configuration

15-2 entry Child Element of the logger-severity-properties Element

15-3 Example log4j.properties File

15-4 Commons Code Example

15-5 Creating a debug-properties Element for the Debug Flag

15-6 Enabling Debug Logging

List of Figures

1-1 Oracle CEP Server Lifecycle State Diagram

5-1 Multi-Server Domain Directory Structure

12-1 Oracle CEP MBean Tree

12-2 Oracle CEP MBean Object Model

12-3 Jconsole Initial Login Attempt

12-4 JConsole New Connection Dialog

12-5 JConsole Browser

12-6 JConsole Browser

13-1 Oracle CEP Data Source

13-2 Oracle CEP IDE for Eclipse lib Directory

13-3 New Java Class Dialog

13-4 Manifest Editor: Overview Tab

13-5 Manifest Editor: Runtime Tab

13-6 JAR Selection Dialog

13-7 Manifest Editor: Dependencies Tab

13-8 Package Selection Dialog

13-9 Manifest Editor

14-1 HTTP Publish-Subscribe Server in Oracle CEP

List of Tables

9-1 Oracle CEP Network I/O Providers

10-1 Default Oracle CEP Task Roles and Groups

10-2 Child Elements of <password-validator>

10-3 Oracle CEP Security Auditor Severity Levels

11-1 Configuration Parameters for the jetty Element

11-2 Configuration Parameters for the netio Element

11-3 Configuration Parameters for the work-manager Element

11-4 Configuration Parameters for the jetty-web-app Element

12-1 Oracle CEP MBean Object Name Key Properties

12-2 Component Declaration Example With Corresponding MBean Object Names

12-3 Configuration Parameters for the jmx Element

12-4 Configuration Parameters for the rmi Element

12-5 Configuration Parameters for the jndi-context Element

12-6 Configuration Parameters for the exported-jndi-context Element

12-7 JConsole New Connection Attributes

13-1 bundler.sh Command Line Options

13-2 Factory Class and Service Interface

13-3 driver-params Child Element Properties

13-4 New Java Class Parameters

13-5 driver-params Child Element Properties

15-1 Log Message Severity

15-2 Configuration Parameters for logging-service

15-3 Configuration Parameters for log-file

15-4 Configuration Parameters for log-stdout

15-5 Logging Component Name Constants

15-6 Debug Flags

A-1 Connection Arguments

A-2 User Credentials Arguments

A-3 Common Arguments

A-4 Overview of Commands for Managing the Server Life Cycle

A-5 SHUTDOWN Arguments

A-6 Overview of Commands for Managing Application Oracle CQL Rules

A-7 GETRULE Arguments

A-8 ADDRULE Arguments

A-9 DELETERULE Arguments

A-10 REPLACERULE Arguments

A-11 STARTRULE Arguments

A-12 STOPRULE Arguments

A-13 UPLOAD Arguments

A-14 DOWNLOAD Arguments

A-15 Overview of Commands for Managing Application EPL Rules

A-16 ADDRULE Arguments

A-17 DELETERULE Arguments

A-18 REPLACERULE Arguments

A-19 GETRULE Arguments

A-20 ADDPARAMS Arguments

A-21 DELETEPARAMS Arguments

A-22 GETPARAMS Arguments

A-23 UPLOAD Arguments

A-24 DOWNLOAD Arguments

A-25 MBean Management Command Overview

A-26 GET Arguments

A-27 INVOKE Arguments

A-28 QUERY Arguments

A-29 SET Arguments

A-30 Overview of Commands for Controlling Event Record and Playback

A-31 STARTRECORD Arguments

A-32 STOPRECORD Arguments

A-33 CONFIGURERECORD Arguments

A-34 SCHEDULERECORD Arguments

A-35 LISTRECORD Arguments

A-36 STARTPLAYBACK Arguments

A-37 STOPPLAYBACK Arguments

A-38 CONFIGUREPLAYBACK Arguments

A-39 SCHEDULEPLAYBACK Arguments

A-40 LISTPLAYBACK Arguments

A-41 Overview of Commands for Monitoring Throughput and Latency

A-42 MONITORAVGLATENCY Arguments

A-43 MONITORAVGLATENCYTHRESHOLD Arguments

A-44 MONITORMAXLATENCY Arguments

A-45 MONITORAVGLATENCY Arguments

A-46 Overview of Commands for Managing Configuration History

A-47 DELETECONFIGCHANGEHISTORY Arguments

A-48 GETRULE Arguments

A-49 GETRULE Arguments

A-50 GETRULE Arguments

B-1 Connection Arguments

B-2 User Credential Arguments

B-3 Deployment Commands

C-1 GrabCert Arguments

C-2 passgen Arguments

C-3 secgen Arguments for a File-Based Provider Configuration File

C-4 secgen Arguments for a Key File

Oracle® Fusion Middleware

Administrator's Guide for Oracle Complex Event Processing

11g Release 1 (11.1.1.6.0)

E14300-06

November 2011

Documentation for administrators that describes how to manage Oracle Complex Event Processing (Oracle CEP) applications and clusters, including deploying and administering, as well as configuring use of Oracle Coherence, Jetty, JMX, JDBC, and security tools.

Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing 11g Release 1 (11.1.1.6.0)

E14300-06

Copyright © 2007, 2011, Oracle and/or its affiliates. All rights reserved.

Primary Author: Steve Traut, Peter Purich

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This document describes how to configure and manage the Oracle CEP server.

Oracle CEP (formally known as the WebLogic Event Server) is a Java server for the development of high-performance event driven applications. It is a lightweight Java application container based on Equinox OSGi, with shared services, including the Oracle CEP Service Engine, which provides a rich, declarative environment based on Oracle Continuous Query Language (Oracle CQL) - a query language based on SQL with added constructs that support streaming data - to improve the efficiency and effectiveness of managing business operations. Oracle CEP supports ultra-high throughput and microsecond latency using JRockit Real Time and provides Oracle CEP Visualizer and Oracle CEP IDE for Eclipse developer tooling for a complete real time end-to-end Java Event-Driven Architecture (EDA) development platform.

Audience

This document is intended for all users of Oracle CEP.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following:

Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing

Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing

Oracle Fusion Middleware CQL Language Reference for Oracle Complex Event Processing

Oracle Fusion Middleware EPL Language Reference for Oracle Complex Event Processing

Oracle Database SQL Language Reference at http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/toc.htm

SQL99 Specifications (ISO/IEC 9075-1:1999, ISO/IEC 9075-2:1999, ISO/IEC 9075-3:1999, and ISO/IEC 9075-4:1999)

Oracle CEP Forum: http://forums.oracle.com/forums/forum.jspa?forumID=820

Oracle CEP Samples: http://www.oracle.com/technologies/soa/complex-event-processing.html

Oracle Event Driven Architecture Suite sample code: http://www.oracle.com/technology/sample_code/products/event-driven-architecture

Conventions

The following text conventions are used in this document:

Convention | Meaning
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Part I

Overview

Part I contains the following chapters:

Chapter 1, "Overview of Oracle CEP Server Administration"

1 Overview of Oracle CEP Server Administration

This chapter provides an overview of administering Oracle Complex Event Processing (Oracle CEP), introducing Oracle CEP servers and domains and server lifecycle, as well as server configuration, administration tools and tasks.

Section 1.1, "Understanding Oracle CEP Servers and Domains"

Section 1.2, "Understanding Oracle CEP Server Lifecycle"

Section 1.3, "Understanding Oracle CEP Server Configuration"

Section 1.4, "Understanding Oracle CEP Server Administration Tools"

Section 1.5, "Understanding Oracle CEP Server Administration Tasks"

1.1 Understanding Oracle CEP Servers and Domains

An Oracle CEP server consists of logically related resources and services to which you deploy Oracle CEP applications. Services include:

Network Input/Output (I/O)—server and client Internet Protocol (IP) port access, IPv4 and IPv6 support, and a variety of blocking and non-blocking network I/O providers.

Security—security services such as SSL, password stores, and authentication and authorization providers.

Jetty—HTTP server.

Java Management Extensions (JMX)—to provide programmatic access to Oracle CEP server and application behavior.

JDBC datasources—to access relational databases to store events for event record and playback, to access a table as an event source for Oracle CQL queries, and to join a table in EPL queries.

HTTP publish-subscribe server—to push event messages to subscribed clients such as the Oracle CEP Visualizer and your own Web 2.0 applications.

logging—to support monitoring and troubleshooting server and application operation.

All the files that apply to a server are contained in a single server directory. The main configuration file for the server is called config.xml—this is where you configure the server's services and specify to which domain the server belongs. For more information, see Section 1.3.1, "Oracle CEP Server Configuration Files".

An Oracle CEP domain is the management unit of a set of one or more servers. There are two types of domain:

Standalone-server domain—A domain that contains a single server. This is the type of domain created by default by the Configuration Wizard and is the starting point for a multi-server domain.

For more information, see Chapter 3, "Administrating Oracle CEP Standalone-Server Domains".

Multi-server domain—A domain that contains two or more servers that share the same multicast address and port and share a security provider. Multi-server domains enable high availability for Oracle CEP applications. When you deploy an application to a multi-server domain, the application is replicated to each server in the domain.

The servers in a multi-server domain can be located on the same computer or on separate computers; what ties the servers together in a multi-server domain is that they have the same multicast address and port and belong to the same domain, all of which are configured in the server's config.xml file.

For more information, see:

Chapter 6, "Administrating Multi-Server Domains With Oracle Coherence"

Chapter 7, "Administrating Multi-Server Domains With Oracle CEP Native Clustering"

1.2 Understanding Oracle CEP Server Lifecycle

Figure 1-1 shows a state diagram for the Oracle CEP server lifecycle. In this diagram, the state names (STARTING, RUNNING, and SHUTTING_DOWN) correspond to the ServerRuntimeMBean method getState() return values. These states are specific to Oracle CEP; they are not OSGi bundle states.

Figure 1-1 Oracle CEP Server Lifecycle State Diagram

Note:

For information on Oracle CEP application lifecycle, see "Oracle CEP Application Lifecycle" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

This section describes the lifecycle of an application deployed to Oracle CEP and the sequence of com.bea.wlevs.ede.api API callbacks. The lifecycle description is broken down into actions that a user performs, including:

Section 1.2.1, "User Action: Start Oracle CEP Server"

Section 1.2.2, "User Action: Stop Oracle CEP Server"

This information explains how Oracle CEP manages an application's lifecycle so that you can better use the lifecycle APIs in your application. For a description of these APIs (such as RunnableBean and SuspendableBean), see:

"Oracle CEP APIs" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing

1.2.1 User Action: Start Oracle CEP Server

After you start the Oracle CEP server, it performs the following actions:

Starts core engine bundles.

Starts Oracle CEP bundles.

Registers MBeans.

Oracle CEP server state is now STARTING.

Starts application bundles.

Oracle CEP server state is now RUNNING.

1.2.2 User Action: Stop Oracle CEP Server

After you shutdown the Oracle CEP server, it performs the following actions:

Oracle CEP server state is SHUTTING_DOWN.

Unregister ServerRuntimeMBean.

Oracle CEP server ceases to have a state.

Shuts down Oracle CEP bundles.

Shuts down application bundles.

Shuts down core engine bundles.

1.3 Understanding Oracle CEP Server Configuration

Oracle CEP server configuration falls into two categories:

configuring a server

configuring the applications you deploy to a server

For each configuration category, you can perform the configuration task:

Statically: by editing an XML file manually.

Using this approach, you must restart the server or redeploy the application after making a change.

Dynamically: by manipulating management beans (MBeans) using Oracle CEP Visualizer, wlevs.Admin command-line utility, or programmatically using JMX,

Using this approach, you do not have to restart the server or redeploy the application after making a change

You configure the server statically by:

Stopping the Oracle CEP server.

Editing the Oracle CEP server config.xml file located in the server's domain directory

Starting the Oracle CEP server.

There are some server configuration tasks that you can only perform statically, such as configuring Jetty.

There are some server configuration tasks that you can perform dynamically using management beans (MBeans). In this case you do not have to manually stop and start the server for the changes to take effect.

You can dynamically configure Oracle CEP servers and applications using Oracle CEP Visualizer, wlevs.Admin command line utility, or your own Java code using Oracle CEP standards-based interfaces that are fully compliant with JMX APIs (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/).

Typically, you statically configure an application when you initially create it, as described in Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse. In particular, you configure the event processing network (EPN) of the application by creating the EPN assembly file, and configure individual components of the application (adapters, channels, and processors) by creating their configuration files.

After you deploy an application, you can dynamically change its configuration, as well as the configuration of its individual components, by manipulating the MBeans that the Oracle CEP server automatically creates for the application and its components. A typical task is to dynamically configure the Oracle CQL rules for the processors of a deployed application. You do this using Oracle CEP Visualizer, wlevs.Admin command-line utility, or JMX.

This section describes:

Section 1.3.1, "Oracle CEP Server Configuration Files"

Section 1.3.2, "Configuring an Oracle CEP Server by Manually Editing the config.xml File"

Section 1.3.3, "Configuration History Management"

Section 1.3.4, "Configuring the Oracle CEP Server bootclasspath"

For more information, see:

Section 1.5.3, "Configuring Oracle CEP Servers"

Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Appendix A, "wlevs.Admin Command-Line Reference"

Chapter 12, "Configuring JMX for Oracle CEP"

1.3.1 Oracle CEP Server Configuration Files

By default, the Configuration Wizard creates domains in the ORACLE_CEP_HOME/user_projects/domains directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory such as d:\oracle_cep.

For example, d:\oracle_cep\user_projects\domains\my_domain, where my_domain is the a domain directory. Each Oracle CEP server you create in this domain will have a subdirectory in my_domain such as c:\oracle_cep\user_projects\domains\my_domain\server1.

The following list describes the important files and directories of a server in a domain, relative to the server directory (such as c:\oracle_cep\user_projects\domains\my_domain\server1):

deployments.xml—XML file that contains the list of applications, packaged as OSGi bundles, that are currently deployed to the Oracle CEP instance of this domain. You never update this file manually to deploy applications, but rather, use the deployer tool.

startwlevs.cmd—Command file used to start an instance of Oracle CEP. The UNIX equivalent is called startwlevs.sh.

stopwlevs.cmd—Command file used to stop an instance of Oracle CEP. The UNIX equivalent is called stopwlevs.sh.

config/config.xml—XML file that describes the services that have been configured for the Oracle CEP instance. Services include logging, debugging, Jetty Web Service, and JDBC data sources.

For more information, see Section 1.3.2, "Configuring an Oracle CEP Server by Manually Editing the config.xml File".

config/security*—Files that configure security for the domain.

config/atnstore.txt—File that lists the configured users and groups for this domain.

1.3.2 Configuring an Oracle CEP Server by Manually Editing the config.xml File

The most efficient, least error-prone way to configure an Oracle CEP server is to use one or more of the Oracle CEP administration tools as Section 1.4, "Understanding Oracle CEP Server Administration Tools" describes.

Optionally, you can perform Oracle CEP server configuration by manually editing the Oracle CEP server config.xml file. For more information on the location of the Oracle CEP server config.xml file, see Section 1.3.1, "Oracle CEP Server Configuration Files".

Caution:

If you update the config.xml file manually to change the configuration of an Oracle CEP server, you must restart the server for the change to take effect.

You can configure the following server objects and features using the config.xml file (the referenced sections describe the exact elements you must add or update):

How the servers in a multi-server domain are configured together. This includes the multicast address and port, the groups, and so on.

See:

Chapter 3, "Administrating Oracle CEP Standalone-Server Domains"

Chapter 6, "Administrating Multi-Server Domains With Oracle Coherence"

Chapter 7, "Administrating Multi-Server Domains With Oracle CEP Native Clustering"

Network I/O.

See Chapter 9, "Configuring Network I/O for Oracle CEP."

Security.

See Chapter 10, "Configuring Security for Oracle CEP."

Jetty, an open-source, standards-based, full-featured Java Web Server.

See Chapter 11, "Configuring Jetty for Oracle CEP."

JMX, required to use the Oracle CEP Visualizer, wlevs.Admin utility, and Deployer utility

See Chapter 12, "Configuring JMX for Oracle CEP."

JDBC data source, used to connect to a relational database.

See Chapter 13, "Configuring JDBC for Oracle CEP."

HTTP publish-subscribe server.

See Chapter 14, "Configuring HTTP Publish-Subscribe for Oracle CEP."

Logging and debugging properties of the server. By default, the log level is set to NOTICE.

See Chapter 15, "Configuring Logging and Debugging for Oracle CEP."

Example 1-1 shows a sample config.xml, from the ORACLE_CEP_HOME/user_projects/domains/ocep_domain/defaultserver template domain, shows how to configure some of these services.

Example 1-1 Sample Oracle CEP Server config.xml File

<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2007 sp2 (http://www.altova.com)-->
<n1:config
  xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd"
  xmlns:n1="http://www.bea.com/ns/wlevs/config/server"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <netio>
      <name>NetIO</name>
      <port>9002</port>
   </netio>
   <netio>
      <name>sslNetIo</name>
      <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
      <port>9003</port>
   </netio>
   <work-manager>
      <name>JettyWorkManager</name>
      <min-threads-constraint>5</min-threads-constraint>
      <max-threads-constraint>10</max-threads-constraint>
   </work-manager>
   <jetty>
      <name>JettyServer</name>
      <network-io-name>NetIO</network-io-name>
      <work-manager-name>JettyWorkManager</work-manager-name>
      <secure-network-io-name>sslNetIo</secure-network-io-name>
   </jetty>
   <rmi>
      <name>RMI</name>
      <http-service-name>JettyServer</http-service-name>
   </rmi>
   <jndi-context>
      <name>JNDI</name>
   </jndi-context>
   <exported-jndi-context>
      <name>exportedJndi</name>
      <rmi-service-name>RMI</rmi-service-name>
   </exported-jndi-context>
   <jmx>
      <rmi-service-name>RMI</rmi-service-name>
      <jndi-service-name>JNDI</jndi-service-name>
   </jmx>
   <ssl>
      <name>sslConfig</name>
      <key-store>./ssl/evsidentity.jks</key-store>
      <key-store-pass>
         <password>{Salted-3DES}j4XEtuXmmvEl4M/NInwq0A==</password>
      </key-store-pass>
      <key-store-alias>evsidentity</key-store-alias>
      <key-manager-algorithm>SunX509</key-manager-algorithm>
      <ssl-protocol>TLS</ssl-protocol>
      <enforce-fips>false</enforce-fips>
      <need-client-auth>false</need-client-auth>
   </ssl>
   <http-pubsub>
      <name>pubsub</name>
      <path>/pubsub</path>
      <pub-sub-bean>
         <server-config>
            <name>/pubsub</name>
            <supported-transport>
               <types>
                  <element>long-polling</element>
               </types>
            </supported-transport>
            <publish-without-connect-allowed>true</publish-without-connect-allowed>
         </server-config>
         <channels>
            <element>
               <channel-pattern>/evsmonitor</channel-pattern>
            </element>
            <element>
               <channel-pattern>/evsalert</channel-pattern>
            </element>
            <element>
               <channel-pattern>/evsdomainchange</channel-pattern>
            </element>
         </channels>
      </pub-sub-bean>
   </http-pubsub>
   <cluster>
      <server-name>productionServer</server-name>
   </cluster>
   <domain>
      <name>ocep_domain</name>
   </domain>

1.3.3 Configuration History Management

When you deploy an application to the Oracle CEP server, the Oracle CEP server creates a configuration history for the application. Any configuration changes you make to the application are recorded in this history. You can view and roll-back (undo) these changes using the Oracle CEP Visualizer or wlevs.Admin tool.

For more information, see:

"Configuration History Management" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Appendix A, "Commands for Managing Configuration History"

1.3.4 Configuring the Oracle CEP Server bootclasspath

In general, you configure all Oracle CEP server options using the Oracle CEP server configuration file, you configure all Oracle CEP application options using Oracle CEP assembly and component configuration files, and you satisfy all Oracle CEP application run-time dependencies by importing the relevant private artifacts into an Oracle CEP project or deploying a shared application library that contains the relevant shared artifacts that applications import indirectly.

If necessary, you can configure the Oracle CEP bootclasspath with artifacts, such as native code libraries, that the Oracle CEP server makes available before both application libraries and Oracle CEP applications are deployed.

You can use this technique to satisfy application or application library dependencies that you cannot satisfy using simple application imports or application libraries.

For more information, see "Application Dependencies" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

1.3.4.1 How to Configure the Oracle CEP Server bootclasspath

Optionally, you can use the bootclasspath to make native code libraries available to application libraries that depend on them.

To configure the Oracle CEP bootclasspath:

Update the server start script in the server directory of your domain directory so that Oracle CEP finds the appropriate native library JAR file when it boots up.

The name of the server start script is startwlevs.cmd (Windows) or startwlevs.sh (UNIX), and the script is located in the server directory of your domain directory. The out-of-the-box sample domains are located in ORACLE_CEP_HOME/ocep_11.1/samples/domains, and the user domains are located in ORACLE_CEP_HOME/user_projects/domains, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory, such as d:\oracle_cep.

Update the start script by adding the -Xbootclasspath/a option to the Java command that executes the wlevs_3.0.jar file. Set the -Xbootclasspath/a option to the full path name of the native library you are going to use.

For example, if you want to use the native library mynativelib located in Oracle CEP server directory %USER_INSTALL_DIR%\bin, update the java command in the start script as follows -- the updated section shown in bold (the example is broken here for readability; in practice you should have the full command on one line):

%JAVA_HOME%\bin\java -Dwlevs.home=%USER_INSTALL_DIR% -Dbea.home=%BEA_HOME%
-Xbootclasspath/a:%USER_INSTALL_DIR%\bin\mynativelib.jar
-jar "%USER_INSTALL_DIR%\bin\wlevs_3.0.jar"
-disablesecurity %1 %2 %3 %4 %5 %6

In the example, %USER_INSTALL_DIR% points to ORACLE_CEP_HOME\ocep_11.1.

If Oracle CEP is running, restart it so it reads the new java option and data source information.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

1.4 Understanding Oracle CEP Server Administration Tools

This section describes the various Oracle CEP server administration tools that you can use to administer Oracle CEP servers, domains, and applications.

You can administer Oracle CEP servers, domains, and applications using any of the following:

Section 1.4.1, "Configuration Wizard"

Section 1.4.2, "Oracle CEP Visualizer"

Section 1.4.3, "wlevs.Admin Command-Line Utility"

Section 1.4.4, "Deployer Command-Line Utility"

Section 1.4.5, "Security Command-Line Utilities"

Section 1.4.6, "JMX"

For more information, see:

Section 1.3, "Understanding Oracle CEP Server Configuration"

Section 1.5, "Understanding Oracle CEP Server Administration Tasks"

1.4.1 Configuration Wizard

The Configuration Wizard is a Java application that you can invoke graphically to create and update Oracle CEP servers and domains.

For more information, see:

Chapter 3, "Administrating Oracle CEP Standalone-Server Domains"

Chapter 6, "Administrating Multi-Server Domains With Oracle Coherence"

Chapter 7, "Administrating Multi-Server Domains With Oracle CEP Native Clustering"

1.4.2 Oracle CEP Visualizer

The Oracle CEP Visualizer is the Oracle CEP graphical administration console.

It 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 specified tasks, accepts data that is then passed back to Oracle CEP to change its configuration.

Using Oracle CEP Visualizer, you can perform a wide variety of Oracle CEP server, domain, and application administration tasks for existing Oracle CEP standalone server domains and Oracle CEP multi-server domains.

For more information, see "Overview of Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

1.4.3 wlevs.Admin Command-Line Utility

The wlevs.Admin command-line utility is a Java application that you can invoke locally or remotely to perform a wide variety of Oracle CEP server, domain, and application administration tasks.

For more information, see Appendix A, "wlevs.Admin Command-Line Reference".

1.4.4 Deployer Command-Line Utility

The Deployer command-line utility is a Java application that you can invoke locally or remotely to perform application deployment and application administration tasks.

For more information, see Appendix B, "Deployer Command-Line Reference".

1.4.5 Security Command-Line Utilities

Oracle CEP provides a variety of command-line utilities that simplify security administration.

For more information, see Appendix C, "Security Utilities Command-Line Reference".

1.4.6 JMX

Using standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification, you can perform a wide variety of Oracle CEP server, domain, and application administration tasks programatically using JMX and Oracle CEP MBeans.

For more information, see:

Chapter 12, "Configuring JMX for Oracle CEP"

Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing

1.5 Understanding Oracle CEP Server Administration Tasks

This section describes some of the important Oracle CEP server administration tasks, including:

Section 1.5.1, "Creating Oracle CEP Servers and Domains"

Section 1.5.2, "Updating Oracle CEP Servers and Domains"

Section 1.5.3, "Configuring Oracle CEP Servers"

Section 1.5.4, "Starting and Stopping Oracle CEP Servers"

Section 1.5.5, "Deploying Applications to Oracle CEP Servers"

Section 1.5.6, "Managing Oracle CEP Applications, Servers, and Domains"

1.5.1 Creating Oracle CEP Servers and Domains

The most important administration task is to create Oracle CEP servers and domains.

For more information, see:

Chapter 3, "Creating an Oracle CEP Standalone-Server Domain"

Chapter 6, "Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Chapter 7, "Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering"

1.5.2 Updating Oracle CEP Servers and Domains

Once you create an Oracle CEP server and domain, you can update it to change its configuration or group membership.

For more information, see:

Chapter 3, "Updating an Oracle CEP Standalone-Server Domain"

Chapter 6, "Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Chapter 7, "Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering"

1.5.3 Configuring Oracle CEP Servers

Once you create an Oracle CEP server and domain, you must configure the various services they provide.

For more information, see:

Chapter 9, "Configuring Network I/O for Oracle CEP"

Chapter 10, "Configuring Security for Oracle CEP"

Chapter 11, "Configuring Jetty for Oracle CEP"

Section 12.2, "Configuring JMX"

Chapter 13, "Configuring JDBC for Oracle CEP"

Chapter 14, "Configuring HTTP Publish-Subscribe for Oracle CEP"

Chapter 15, "Configuring Logging and Debugging for Oracle CEP"

1.5.4 Starting and Stopping Oracle CEP Servers

After you have created an Oracle CEP domain along with at least a single server, you start a server instance so you can then deploy applications and begin running them. During upgrades and after some configuration changes, you must stop and start the Oracle CEP server.

For more information, see:

Section 3.3, "Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain"

Oracle Coherence: Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain"

Oracle CEP Native Clustering: Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain"

Note:

on Windows, do not stop the Oracle CEP server by clicking the Close button in the command prompt in which you started it. Always stop the Oracle CEP server using the stopwlevs.cmd script or Ctrl-C.

1.5.5 Deploying Applications to Oracle CEP Servers

Once you have created and configured an Oracle CEP server and domain, you can deploy Oracle CEP applications to them.

For more information, see:

Section 4.1, "Deploying an Application to an Oracle CEP Standalone-Server Domain"

Section 8.1, "Overview of Deploying an Application to an Oracle CEP Multi-Server Domain"

"Overview of Creating Oracle CEP Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

1.5.6 Managing Oracle CEP Applications, Servers, and Domains

Once you have deployed applications to an Oracle CEP server and domain, you must manage the application to perform tasks such as monitor its performance and perform upgrades.

For more information, see:

Section 1.4, "Understanding Oracle CEP Server Administration Tools"

Section 12.3, "Managing With JMX"

Part II

Standalone-Server Domains

Part II contains the following chapters:

Chapter 2, "Introduction to Standalone-Server Domains"

Chapter 3, "Administrating Oracle CEP Standalone-Server Domains"

Chapter 4, "Deploying Applications to Standalone-Server Domains"

2 Introduction to Standalone-Server Domains

This chapter introduces standalone domains for Oracle Complex Event Processing (Oracle CEP), or domains that contain a single instance that can be the starting point for clusters.

Section 2.1, "Overview of Oracle CEP Standalone-Server Domain Administration"

Section 2.2, "Scalability and Oracle CEP Standalone-Server Domain"

Section 2.3, "Next Steps"

2.1 Overview of Oracle CEP Standalone-Server Domain Administration

An Oracle CEP standalone-server domain is a domain that contains a single Oracle CEP server. This is the type of domain created by default by the Configuration Wizard and is the starting point for a multi-server domain.

For more information, see:

Section 1.1, "Understanding Oracle CEP Servers and Domains"

Section 1.3, "Understanding Oracle CEP Server Configuration"

2.2 Scalability and Oracle CEP Standalone-Server Domain

Using a standalone-server domain, you can take advantage of some of the Oracle CEP scalability quality of service options.

To maximize scalability, consider a multi-server domain.

For more information, see:

"Understanding Scalability" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

Chapter 5, "Introduction to Multi-Server Domains"

2.3 Next Steps

After creating your own Oracle CEP standalone-server domain, consider the administration tasks that Section 1.5, "Understanding Oracle CEP Server Administration Tasks" describes.

For example, you can:

Create additional servers in the domain and configure the domain to be multi-server.

See Chapter 5, "Introduction to Multi-Server Domains."

Optionally configure the server.

See Section 1.3, "Understanding Oracle CEP Server Configuration."

Create an Oracle CEP application.

See Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse for a description of the programming model, details about the various components that make up an application, how they all fit together, and typical steps to create a new application.

Deploy your new, or existing, Oracle CEP application to the domain.

For more information, see:

Section 4.1, "Deploying an Application to an Oracle CEP Standalone-Server Domain"

"Assembling and Deploying Oracle CEP Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

Manage your applications, servers, and domains:

Using the Oracle CEP Visualizer.

See Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Using the wlevs.Admin command line tool.

See Appendix A, "wlevs.Admin Command-Line Reference".

Using JMX and MBeans.

See Section 12.3, "Managing With JMX".

3 Administrating Oracle CEP Standalone-Server Domains

This chapter describes how create and update an Oracle Complex Event Processing (Oracle CEP) standalone-server domain with the configuration wizard, as well as how to start and stop the server.

Section 3.1, "Creating an Oracle CEP Standalone-Server Domain"

Section 3.2, "Updating an Oracle CEP Standalone-Server Domain"

Section 3.3, "Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain"

3.1 Creating an Oracle CEP Standalone-Server Domain

After you install Oracle CEP, use the Configuration Wizard to create a new domain to deploy your applications. The Configuration Wizard creates, by default, the domains in the ORACLE_CEP_HOME/user_projects/domains directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory such as d:/oracle_cep. You can, however, create a domain in any directory you want.

The Configuration Wizard creates a single default server in the domain; all the server-related file are located in a subdirectory of the domain directory named the same as the server (such a c:\oracle_cep\user_projects\domains\my_domain\defaultserver). Additionally, the Configuration Wizard allows you to:

Configure the server's administration user and password.

Configure the default server to use a database or database driver that is different from the default. In this case, you need to customize the JDBC settings to point to the appropriate database.

Configure the server's listen port.

Configure the password for the identity keystore and private keystore.

You can use the Configuration Wizard in the following modes:

Graphical mode—Graphical-mode configuration is an interactive, GUI-based method for creating and configuring a domain. It can be run on both Windows and UNIX systems. See Section 3.1.1, "Creating an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode."

3.1.1 Creating an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode

The following procedure shows how to invoke and use the Configuration Wizard in graphical mode by executing the relevant command script for both Windows or Unix.

Note:

On Windows, you can also invoke the Configuration Wizard using the Start menu:

Start > All Programs > Oracle Complex Event Processing 11gR1 > Tools > Configuration Wizard

Note:

If you intend to add servers from this new domain to the Eclipse IDE, be sure to see "How to Create a Local Oracle CEP Server and Server Runtime" in Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse for information on completing domain creation.

To create an Oracle CEP standalone-server domain using the Configuration Wizard in graphical mode:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the ORACLE_CEP_HOME/ocep_11.1/common/bin directory, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep:

prompt> cd /oracle_cep/ocep_11.1/common/bin

Invoke the config.cmd (Windows) or config.sh (UNIX) command to invoke the wizard:

prompt> config.sh

After the Configuration Wizard has finished loading, you will see a standard Oracle Welcome window.

Note:

The Oracle CEP Configuration Wizard is self-explanatory; however, if you want more information about using the tool, continue reading this procedure.

Click Next.

In the Choose Create or Update Domain window, choose Create a New Oracle CEP Domain.

Click Next.

Enter the name of the administrator user for the default server of the domain.

Click Next.

Enter basic configuration information about the default server in the domain. In particular:

Enter the name of the default server. This name will also be used as the name of the directory that contains the default server files.

The listen port for Oracle CEP itself. Default is 9002.

The secure listen port. Default is 9003.

Click Next.

Enter and confirm the password for the Oracle CEP domain identity keystore.

By default, the password for the certificate private key will be the same as the password for the identity keystore.

Note:

The Oracle CEP Server will not start unless the password for certificate private key is the same as the password for the identity keystore. Do not clear Use Keystore Password and do not enter a private key password.

Click Next.

Decide whether or not to update the JDBC datasource configuration:

The Configuration Wizard bases the creation of a new domain on the Oracle CEP domain template; by default, this template does not configure any JDBC datasource for a domain. This means that, unless you change the default domain template used by the Configuration Wizard, if you choose No at this step, no JDBC data source is configured. If you want to configure a JDBC data source, choose Yes at this step to proceed to the page in which you can enter the data source information.

To create a JDBC datasource:

Select Yes.

Click Next.

Enter the new JDBC datasource values in Configure Database Properties window.

In the top section, enter the name of the datasource. Then select the database type (Oracle or Microsoft SQL Server) and corresponding drivers; you can also browse to new drivers using the Browse/Append button.

In the lower section, enter the details about the database to which this data source connects, such as its name, the name of the computer that hosts the database server, the port, and the name and password of the user that connects to the database. The JDBC connection URL is automatically generated for you based on this information.

Click Next.

To not create a JDBC datasource:

Select No.

Click Next.

In the Configure Server window, enter the name of the new domain and the full pathname of its domain location.

The configuration wizard creates the domain using its domain name in the domain location directory.

Note:

Oracle recommends you always use the default domain location to create your domains:

On UNIX, the default domain is: ORACLE_CEP_HOME/user_projects/domains.

On Windows, the default domain is: ORACLE_CEP_HOME\user_projects\domains.

Click Create.

If the creation of the domain succeeded, you will see a message similar to the following in the Creating Domain window:

Domain created successfully!
Domain location: C:\oracle_cep\user_projects\domains\ocep_domain

Click Done.

If you intend to add servers from this new domain to the Eclipse IDE, be sure to see "How to Create a Local Oracle CEP Server and Server Runtime" in Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse for information on completing domain creation.

3.2 Updating an Oracle CEP Standalone-Server Domain

Use the Configuration Wizard to update an existing server in a domain.

The Configuration Wizard creates, by default, the domains in the ORACLE_CEP_HOME/user_projects/domains directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory such as d:/oracle_cep. You can, however, create a domain in any directory you want.

The Configuration Wizard creates a single default server in the domain; all the server-related file are located in a subdirectory of the domain directory named the same as the server (such as c:\oracle_cep\user_projects\domains\my_domain\defaultserver).

You can update only the following configuration options of an existing standalone-server in your domain:

The listen port.

The configuration of the JDBC datasource.

You can use the Configuration Wizard in the following modes:

Graphical mode—Graphical-mode is an interactive, GUI-based method for updating a domain. It can be run on both Windows and UNIX systems. See Section 3.2.1, "How to Update an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode."

3.2.1 How to Update an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode

The following procedure shows how to invoke and use the Configuration Wizard in graphical mode by executing the relevant command script for both Windows or Unix.

Note:

On Windows, you can also invoke the Configuration Wizard using the Start menu:

Start > All Programs > Oracle Complex Event Processing 11gR1 > Tools > Configuration Wizard

For clarity, it is assumed in this section that you want to update a server called productionServer whose server-related files are located in the C:\oracle_cep\user_projects\domains\mydomain\productionServer directory.

To update an Oracle CEP standalone-server domain using the Configuration Wizard in graphical mode:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the ORACLE_CEP_HOME/ocep_11.1/common/bin directory, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep:

prompt> cd /oracle_cep/ocep_11.1/common/bin

Invoke the config.cmd (Windows) or config.sh (UNIX) command to invoke the wizard:

prompt> config.sh

After the Configuration Wizard has finished loading, you will see a standard Oracle Welcome window.

Note:

The Oracle CEP Configuration Wizard is self-explanatory; however, if you want more information about using the tool, continue reading this procedure.

Click Next.

In the Choose Create or Update Domain window, select Update an existing Oracle CEP domain.

Click Next.

In the text box, enter the full pathname of the server directory that contains the files for the server you want to update.

In this example, the value is C:\oracle_cep\user_projects\domains\mydomain\productionServer.

Click Next.

Update the listen ports for the server.

Note:

To prevent any conflicts when all servers are running at the same time, be sure that you do not enter the same values used by other servers in the domain.

Click Next.

Decide whether or not to update the JDBC datasource configuration:

To update the JDBC datasource configuration:

Select Yes.

Click Next.

Enter the new JDBC datasource values.

To leave the JDBC datasource configuration unchanged:

Select No.

Click Next.

Click Update to update the server.

3.3 Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain

You can start and stop an Oracle CEP standalone-server using any of the Oracle CEP Visualizer, Oracle CEP IDE for Eclipse, or command line scripts.

This section describes:

Section 3.3.1, "How to Start an Oracle CEP Standalone-Server Using the startwlevs Script"

Section 3.3.2, "How to Stop an Oracle CEP Standalone-Server Using the stopwlevs Script"

3.3.1 How to Start an Oracle CEP Standalone-Server Using the startwlevs Script

Each Oracle CEP server directory contains a command script that starts a server instance; by default, the script is called startwlevs.cmd (Windows) or startwlevs.sh (UNIX).

To start an Oracle CEP standalone-server using the startwlevs script:

Ensure that the JAVA_HOME variable in the server start script points to the correct Oracle JRockit JDK. If it does not, edit the script.

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

If using the Oracle JRockit JDK installed with Oracle CEP, the JAVA_HOME variable should be set as follows:

For UNIX:

JAVA_HOME=ORACLE_CEP_HOME/jrockit_160_20

For Windows:

set JAVA_HOME=ORACLE_CEP_HOME\jrockit_160_20

where ORACLE_CEP_HOME refers to the installation directory of Oracle CEP 10.3, such as /oracle_cep (UNIX) or c:\oracle_cep (Windows).

If using the Oracle JRockit JDK installed with Oracle JRockit Real Time, the JAVA_HOME variable should be set as follows:

For UNIX:

JAVA_HOME=ORACLE_RT_HOME/JROCKIT_RT_HOME

For Windows:

set JAVA_HOME=ORACLE_RT_HOME\JROCKIT_RT_HOME

where ORACLE_RT_HOME refers to the installation directory of Oracle JRockit Real Time, such as /jrockit (UNIX) or c:\jrockit (Windows), and JROCKIT_RT_HOME refers to JRockit Real Time directory.

Open a command window and change to the server directory of the domain directory. For example, to start the HelloWorld sample server:

prompt> cd C:\oracle_cep\ocep_11.1\samples\domains\helloworld_domain\defaultserver

Execute the startwlevs.cmd (Windows) or startwlevs.sh (UNIX) script:

prompt> startwlevs.cmd

If you are using the Oracle JRockit JDK included in Oracle JRockit Real Time, enable the deterministic garbage collector by passing the -dgc parameter to the command:

prompt> startwlevs.cmd -dgc

Note:

On HP-UX, to avoid an OutOfMemoryError, you may need to increase the MaxPermSize to 256 in startwlevs.sh. For example: -XX:MaxPermSize=256m.

3.3.2 How to Stop an Oracle CEP Standalone-Server Using the stopwlevs Script

Each Oracle CEP server directory contains a command script that stops a server instance; by default, the script is called stopwlevs.cmd (Windows) or stopwlevs.sh (UNIX).

Note:

The following procedure does not stop an Oracle CEP stand-alone server running in SSL mode. To stop an Oracle CEP stand-alone server running in SSL mode, run the wlevs.Admin utility, as described in Section A.4, "Running wlevs.Admin Utility in SSL Mode."

To stop an Oracle CEP standalone-server using the stopwlevs script:

Open a command window and change to the server directory. For example, to stop the running HelloWorld sample server:

prompt> cd C:\oracle_cep\ocep_11.1\samples\domains\helloworld_domain\defaultserver

Execute the stopwlevs.cmd (Windows) or stopwlevs.sh (UNIX) script.

Use the -url argument to pass the URL that establishes a JMX connection to the server you want to stop. This URL takes the form service:jmx:msarmi://host:port//jndi/jmxconnector, where host refers to the computer hosting the server and port refers to the server's JNDI port, configured in config.xml file. For example:

prompt> stopwlevs.sh -url service:jmx:msarmi://ariel:9002/jndi/jmxconnector

In the example, the host is ariel and the JMX port is 9002. The 9002 port is the netio port defined in the Oracle CEP server config.xml configuration file. MSA security uses it for JMX connectivity.

See Section A.6, "Connection Arguments" for additional details about the -url argument.

Note:

on Windows, do not stop the Oracle CEP server by clicking the Close button in the command prompt in which you started it. Always stop the Oracle CEP server using the stopwlevs.cmd script or Ctrl-C.

4 Deploying Applications to Standalone-Server Domains

This chapter describes how to deploy an application to a standalone-server Oracle Complex Event Processing (Oracle CEP) domain, including how to do so with Oracle CEP Visualizer and with the deployer utility.

Section 4.1, "Deploying an Application to an Oracle CEP Standalone-Server Domain"

4.1 Deploying an Application to an Oracle CEP Standalone-Server Domain

When you deploy an application to a standalone-server domain, you typically deploy to the singleton server group using either the Oracle CEP Visualizer or Deployer utility.

For more information, see:

Section 5.2, "Groups"

Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Appendix B, "Deployer Command-Line Reference"

4.1.1 How to Deploy an Application to an Oracle CEP Standalone-Server Using the Oracle CEP Visualizer

The simplest way to deploy an Oracle CEP application to a standalone-server domain is to use the Oracle CEP Visualizer.

For more information, see "Deploying an Application" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

4.1.2 How to Deploy an Application to an Oracle CEP Singleton Server Group Using the Deployer Utility

If you do not specify a group when you deploy an application, Oracle CEP deploys the application to the singleton server group that includes only the specific server to which you deploy the application. This is the standard case in single-server domains.

The following example shows how to deploy to a singleton group; note that the command does not specify a -group option:

prompt> java -jar wlevsdeploy.jar -url http://ariel:9002/wlevsdeployer -install myapp_1.0.jar

In the example, the myapp_1.0.jar application will be deployed to the singleton server group that contains a single server: the one running on host ariel and listening to port 9002.

Part III

Multi-Server Domains

Part III contains the following chapters:

Chapter 5, "Introduction to Multi-Server Domains"

Chapter 6, "Administrating Multi-Server Domains With Oracle Coherence"

Chapter 7, "Administrating Multi-Server Domains With Oracle CEP Native Clustering"

Chapter 8, "Deploying Applications to Multi-Server Domains"

5 Introduction to Multi-Server Domains

This chapter introduces Oracle Complex Event Processing (Oracle CEP) multi-server domains, also known as clusters, based on Oracle Coherence or Oracle CEP native technology. It also provides overviews of multi-server messaging, high availability, and scalability.

Section 5.1, "Overview of Oracle CEP Multi-Server Domain Administration"

Section 5.2, "Groups"

Section 5.3, "Multi-Server Notifications and Messaging"

Section 5.4, "Multi-Server Domain Directory Structure"

Section 5.5, "Order of cluster Element Child Elements"

Section 5.6, "High Availability and Multi-Server Domains"

Section 5.7, "Scalability and Multi-Server Domains"

Section 5.8, "Next Steps"

5.1 Overview of Oracle CEP Multi-Server Domain Administration

An Oracle CEP multi-server domain (or cluster) is a domain to which you can add one or more servers that become logically connected for the purposes of management, and physically connected using a shared User Datagram Protocol (UDP) multicast address and port. All servers in an Oracle CEP multi-server domain are aware of all other servers in the domain and any one server can be used as an access point for making changes to the deployments in the domain.

Management of the multi-server infrastructure is done at the domain level. Thus server failure, start, or restart is detected by every member of the multi-server domain. Each member of the multi-server domain has a consistent, agreed notion of domain membership enforced by the multi-server infrastructure.

To properly configure servers in a multi-server domain, you must configure them with the same multicast address and port and the same domain name. It is an error to configure servers using the same multicast address and port and port but different domain names.

Applications deployed to the default group in a multi-server domain are deployed homogeneously to all servers of that domain, therefore all servers must have the appropriate configuration resources required by the application.

Oracle CEP supports the following clustering systems:

Section 5.1.1, "Oracle Coherence Clustering"

Section 5.1.2, "Oracle CEP Native Clustering"

The rest of this chapter describes:

Section 5.2, "Groups"

Section 5.3, "Multi-Server Notifications and Messaging"

Section 5.4, "Multi-Server Domain Directory Structure"

Section 5.5, "Order of cluster Element Child Elements"

Section 5.6, "High Availability and Multi-Server Domains"

Section 5.7, "Scalability and Multi-Server Domains"

Section 5.8, "Next Steps"

For more information, see:

Section 1.1, "Understanding Oracle CEP Servers and Domains"

Section 1.3, "Understanding Oracle CEP Server Configuration"

5.1.1 Oracle Coherence Clustering

Oracle Coherence: provides replicated and distributed (partitioned) data management services on top of a reliable, highly scalable peer-to-peer clustering protocol. Oracle Coherence has no single points of failure; it automatically and transparently fails over and redistributes its clustered data management services when a server becomes inoperative or is disconnected from the network. When a new server is added, or when a failed server is restarted, it automatically joins the cluster and Oracle Coherence fails back services to it, transparently redistributing the cluster load.

Note:

Before you can use Oracle CEP with Oracle Coherence, you must obtain a valid Oracle Coherence license such as a license for Coherence Enterprise Edition, Coherence Grid Edition, or Oracle WebLogic Application Grid. For more information on Oracle Coherence, see http://www.oracle.com/technology/products/coherence/index.html.

Using Oracle Coherence, you can take advantage of Oracle CEP high availability quality of service options.

For more information, see:

Section 6.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Section 5.6, "High Availability and Multi-Server Domains"

5.1.2 Oracle CEP Native Clustering

Oracle CEP native clustering: provides a native clustering implementation based on TOTEM.

Using Oracle CEP native clustering, you cannot take advantage of Oracle CEP high availability quality of service options.

For more information, see Section 7.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering".

5.2 Groups

In order to support the deployment to, and management of, the multi-server domain at a finer grained-level than the domain, Oracle CEP introduces the concept of groups. A group is a set of one or more servers with a unique name within the domain. In an Oracle CEP domain, an arbitrary number of groups may exist with a configurable group membership. A server may be a member of more than one group, although typically this information is transparent to the user.

When you deploy an application to a multi-server domain, you deploy it to a particular group. Applications deployed to any group must have a unique name across the domain.

Applications deployed to a group in a multi-server domain are deployed homogeneously to all servers of that group, therefore all servers must have the appropriate configuration resources required by the application.

An application that is deployed to a server can be uninstalled from another server under the same domain.

The following pre-defined deployment groups always exist:

Section 5.2.1, "Singleton Server Deployment Group"

Section 5.2.2, "Domain Deployment Group"

Alternatively, you can create a custom deployment group (see Section 5.2.3, "Custom Deployment Groups").

Note:

If you are planning to deploy an Oracle CEP high availability application, and you require scalability, you may also need to create an Oracle CEP high availability notification group. For more information, see "Deployment Group and Notification Group" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

5.2.1 Singleton Server Deployment Group

This group consists of only the local server. This means that the membership of this group depends on the server from which it is accessed. This group can be used to pin deployments to a single server.

For more information, see Section 6.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence".

5.2.2 Domain Deployment Group

This group contains all live members of the domain. Its membership is automatically managed and cannot be changed by the user.

The domain name is determined by the Oracle CEP server config.xml file domain element. For example, the domain is named mydomain if your config.xml file is like this:

<domain>
    <name>mydomain</name>
</domain>

The default name is WLEventServerDomain.

For more information, see Section 6.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence".

5.2.3 Custom Deployment Groups

There are cases where the application logic cannot simply be replicated across a homogenous set of servers in a multi-server domain. Examples of these types of applications are those that must determine the best price provided by different pricing engines, or applications that send an alert when a position crosses a threshold. In these cases, the application is not idempotent; it must calculate only once or send a single event. In other cases, the application has a singleton nature, such as a monitoring application, the HTTP pub-sub server, and so on.

As a more complex example, consider a domain that has two applications: the strategies application uses several strategies for calculating different prices for some derivative and then feeds its results to a selector application. The selector application then selects the best price amongst the different options provided by the strategies' application results. The strategies application can be replicated to achieve fault-tolerance. However, the selector application must be able to keep state so as to determine the best price; for this reason, the selector application cannot be replicated in a hot/hot fashion.

If a domain must support servers that are not completely homogeneous, you configure this by creating custom groups.

Applications deployed to a custom group in a multi-server domain are deployed homogeneously to all servers of that group, therefore all servers must have the appropriate configuration resources required by the application.

For more information, see Section 6.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence".

5.3 Multi-Server Notifications and Messaging

In order to provide high availability (HA)-like capabilities to adapter and event bean implementations, Oracle CEP provides a number of notification and messaging APIs at both the group- and server-level. Using these APIs, you can configure a server to receive notification when its group or domain membership changes, either because an administrator deliberately changed it or due to a server failure. Similarly you can use these APIs to send messages to both individual groups and to the domain.

When you configure your application to use Oracle CEP high availability options, the primary Oracle CEP server uses Oracle Coherence to communicate with its secondary servers to keep them up to date with the primary server's event processing progress.

You can configure Oracle CEP servers in a multi-server domain to communicate securely.

For more information, see:

Section 6.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence"

Section 7.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering"

"Understanding High Availability" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

5.4 Multi-Server Domain Directory Structure

Servers in an Oracle CEP domain store their files in a single directory. By convention, the directories of the servers in a multi-server domain are sub-directories of the domain directory. Additionally, the name of the servers and domain correspond to the name of the server directories and domain directory, respectively. This is by convention only, and not required, although Oracle recommends you set up your domains this way for simplicity and consistency. If the servers of the multi-server domain are located on different computers, you can replicate the directory structure on both computers, also for simplicity and consistency.

Figure 5-1 shows a multi-server domain directory with three servers.

Figure 5-1 Multi-Server Domain Directory Structure

The myServer1 configuration file snippet shows how the domain directory and domain object are configured with the same name, as well as the server directory and server name. The domain directory is located in the ORACLE_CEP_HOME/user_projects/domains directory, which is the default location for Oracle CEP domains.

5.5 Order of cluster Element Child Elements

The order of cluster element child elements in the config.xml file is important; if you include elements in the incorrect order you may encounter an error. The following list describes the order in which you should list the child elements:

server-name

server-host-name: Specifies the host address/IP used for point-to-point HTTP multi-server communication. Default value is localhost.

This element is mandatory if one or more Oracle CEP servers in your multi-server domain are on different hosts and you plan to manage the multi-server domain using the Oracle CEP Visualizer. It is also mandatory if a server is deployed on a host machine that has multiple IP addresses configured (whether in a multi-server or standalone-server environment).

multicast-address: The multicast communication address. For Coherence well-known addressing (WKA) a unicast address can be used.

multicast-port: Optional. Specifies the port used for multicast traffic. Default value is 9001.

identity: Mandatory only for Oracle CEP native clustering; not used for Oracle Coherence.

enabled

security

groups

operation-timeout: Optional. Specifies, in milliseconds, the timeout for point-to-point HTTP multi-server requests. Default value is 30000.

For a complete description of the Oracle CEP server config.xml file cluster element, see "cluster" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

5.6 High Availability and Multi-Server Domains

If you use Oracle Coherence clustering for your multi-server domain, you can take advantage of Oracle CEP high availability quality of service options. These options are not supported using Oracle CEP native clustering.

For more information, see "Understanding High Availability" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

5.7 Scalability and Multi-Server Domains

Using either Oracle Coherence or Oracle CEP native clustering, you can take advantage of Oracle CEP scalability quality of service options.

For more information, see "Understanding Scalability" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

5.8 Next Steps

After creating your own Oracle CEP multi-server domain, consider the administration tasks that Section 1.5, "Understanding Oracle CEP Server Administration Tasks" describes.

For example, you can:

Optionally configure the server.

See Section 1.3, "Understanding Oracle CEP Server Configuration."

Create an Oracle CEP application.

See Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse for a description of the programming model, details about the various components that make up an application, how they all fit together, and typical steps to create a new application.

Deploy your new, or existing, Oracle CEP application to the domain.

For more information, see:

Section 8.1, "Overview of Deploying an Application to an Oracle CEP Multi-Server Domain"

"Assembling and Deploying Oracle CEP Applications" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

Manage your applications, servers, and domains:

Using the Oracle CEP Visualizer.

See Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Using the wlevs.Admin command line tool.

See Appendix A, "wlevs.Admin Command-Line Reference".

Using JMX and MBeans.

See Section 12.3, "Managing With JMX".

6 Administrating Multi-Server Domains With Oracle Coherence

This chapter describes how to administer Oracle Complex Event Processing (Oracle CEP) multi-server domains that are based on Oracle Coherence. It describes how to create and update multi-server domains, as well as how to secure messages, manage membership changes, and start and stop servers.

Section 6.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Section 6.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Section 6.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

Section 6.4, "Using the Multi-Server Domain APIs to Manage Group Membership Changes"

Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain"

6.1 Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence

This section describes how to create and configure a multi-server domain from two or more Oracle CEP servers using Oracle Coherence, including:

Section 6.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence"

Section 6.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence"

Section 6.1.3, "Configuring the Oracle Coherence Cluster"

Note:

To properly configure servers in a multi-server domain, you must configure them with the same multicast address and port and the same domain name. It is an error to configure servers using the same multicast address and port and port but different domain names.

6.1.1 How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence

This procedure describes how to create a multi-server domain that uses only the two predefined groups: the singleton group and domain group. In a domain that uses default groups, all servers must be completely homogenous.

If a domain must support servers that are not completely homogeneous, you configure this by creating custom groups. See Section 6.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence".

Note:

If you are planning to deploy an Oracle CEP high availability application, and you require scalability, you may also need to create an Oracle CEP high availability notification group. For more information, see "Deployment Group and Notification Group" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Note:

In this section it is assumed that you have already created a domain that contains a single server and that you want to add additional servers to the domain to make it a multi-server domain. See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains" for details on creating a domain.

To create an Oracle CEP multi-server domain with default groups using Coherence:

Create a domain that contains a single, initial server.

See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains".

Add one or more servers to the domain using the Configuration Wizard.

Note:

Even though the Configuration Wizard does not support adding new servers to a multi-server domain, one can use the Configuration Wizard to generate a new stand-alone server, and then manually update its configuration to join a multi-server domain.

See Section 6.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence."

Configure all the servers in the multi-server domain by manually editing their config.xml files and adding a cluster element with specific information.

To configure the servers in a multi-server domain using default groups, update the config.xml file for each member server by adding a cluster child element of the root config element as Example 6-1 shows.

Include the following child elements of cluster:

server-name: The server-name child element of cluster specifies a unique name for the server. Oracle CEP Visualizer uses the value of this element when it displays the server in its console.

Default: the Oracle Coherence member name if that is set or WLEvServer-MEMBERID.

server-host-name: Specifies the host address/IP used for point-to-point HTTP multi-server communication. Default value is localhost.

This element is mandatory if one or more Oracle CEP servers in your multi-server domain are on different hosts and you plan to manage the multi-server domain using the Oracle CEP Visualizer. It is also mandatory if a server is deployed on a host machine that has multiple IP addresses configured (whether in a multi-server or standalone-server environment).

multicast-address: The multicast-address element is required unless all servers of the multi-server domain are hosted on the same computer; in that case you can omit the multicast-address element and Oracle CEP automatically assigns a multicast address to the multi-server domain based on the computer's IP address.

If, however, the servers are hosted on different computers, then you must provide an appropriate domain-local address. Oracle recommends you use an address of the form 239.255.X.X, which is what the auto-assigned multicast address is based on.

All the Oracle CEP servers using this multicast-address must be on the same subnet.

Using Oracle Coherence, you can specify a unicast address here and Oracle Coherence will use WKA (Well Known Addressing).

enabled: By default the clustering of the servers in a multi-server domain is enabled for Oracle Coherence, so the element <enabled>true</enabled> is optional.

In Example 6-1, the server is part of a domain called myDomain.

Example 6-1 myServer1 config.xml File

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <enabled>true</enabled>
  </cluster>
...
</config>

For each server of the multi-server domain, the multicast-address elements must contain the same value. The server-name element, however, must be different for each server in the multi-server domain. Example 6-2 shows the config.xml file of a second server, called myServer2, in the myDomain multi-server domain.

Example 6-2 myServer2 config.xml File

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer2</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <enabled>true</enabled>
  </cluster>
...
</config>

See Section 5.5, "Order of cluster Element Child Elements" for a description of additional multi-server-related configuration elements and the required order of child elements.

Optionally, override the default Oracle Coherence clustering configuration, if necessary.

See Section 6.1.3, "Configuring the Oracle Coherence Cluster".

Optionally, secure the messages that are shared between the servers in a domain by configuring encryption and digital signatures.

See Section 6.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence".

To avoid a single point of failure, consider enabling Oracle CEP Visualizer on a small subset of n machines in the domain.

See "How to Start Oracle CEP Visualizer in a Multi-Server Domain" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Note:

Enabling Oracle CEP Visualizer on a given Oracle CEP Server may impact the performance of the server depending on the Oracle CEP Visualizer workload.

Start all servers in your multi-server domain.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

6.1.2 How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence

This procedure describes how to create a multi-server domain using Oracle Coherence that uses custom groups to accommodate servers which are not completely homogenous.

If all the servers in your domain are completely homogeneous, you do not need to create custom groups. Instead, you can use the predefined, default groups: the singleton group and domain group. See Section 6.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle Coherence".

Note:

If you are planning to deploy an Oracle CEP high availability application, and you require scalability, you may also need to create an Oracle CEP high availability notification group. For more information, see "Deployment Group and Notification Group" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Note:

In this section it is assumed that you have already created a domain that contains a single server and that you want to add additional servers to the domain to make it a multi-server domain. See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains" for details on creating a domain.

In this procedure, assume you have created three servers: myServer1, myServer2, and myServer3. You want myServer1 to be a member of the selector group and myServer2 and myServer3 to be members of the strategy group.

To create an Oracle CEP multi-server domain with custom groups using Oracle Coherence:

Create a domain that contains a single, initial server.

See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains".

Add one or more servers to the domain using the Configuration Wizard.

Note:

Even though the Configuration Wizard does not support adding new servers to a multi-server domain, one can use the Configuration Wizard to generate a new stand-alone server, and then manually update its configuration to join a multi-server domain.

See Section 6.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence."

Configure all the servers in the multi-server domain by manually editing their config.xml files and adding a cluster element with specific information.

To configure the servers in a multi-server domain using custom groups, update the config.xml file for each member server by adding (if one does not already exist) a groups child element of cluster and specifying the name of the group as the value of the groups element.

Note:

When adding cluster element child elements, observe the correct element order as Section 5.5, "Order of cluster Element Child Elements" describes.

The groups element can include more than one group name in the case that the server is a member of more than one group; separate multiple group names using commas.

The groups element is optional; if a server configuration does not include one, then the server is a member of the default groups (domain and singleton). For more information about the domain and singleton groups, see Section 5.2, "Groups".

Example 6-3, Example 6-4, and Example 6-5 show the relevant snippets of the config.xml file for each server.

Example 6-3 Server Configuration File config.xml for myServer1

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <enabled>true</enabled>
      <groups>selector</groups>
  </cluster>
...
</config>

Example 6-4 Server Configuration File config.xml for myServer2

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer2</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <enabled>true</enabled>
      <groups>strategy</groups>
  </cluster>
...
</config>

Example 6-5 Server Configuration File config.xml for myServer3

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer3</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <enabled>true</enabled>
      <groups>strategy</groups>
  </cluster>
...
</config>

Optionally, override the default Oracle Coherence clustering configuration, if necessary.

See Section 6.1.3, "Configuring the Oracle Coherence Cluster".

Optionally, secure the messages that are shared between the servers in a domain by configuring encryption and digital signatures.

See Section 6.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence".

To avoid a single point of failure, consider enabling Oracle CEP Visualizer on a small subset of n machines in the domain.

See "How to Start Oracle CEP Visualizer in a Multi-Server Domain" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Note:

Enabling Oracle CEP Visualizer on a given Oracle CEP Server may impact the performance of the server depending on the Oracle CEP Visualizer workload.

Start all servers in your multi-server domain.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

6.1.3 Configuring the Oracle Coherence Cluster

Oracle CEP leverages the native configuration provided by Oracle Coherence. You do this by packaging the following Oracle Coherence configuration file, with the indicated names, in the application bundle that uses the Oracle Coherence cache:

tangosol-coherence-override.xml—Oracle Coherence cluster configuration. See Section 6.1.3.1, "The tangosol-coherence-override.xml File" for information about this file as well as an example.

When assembling your application, consider the following:

tangosol-coherence-override.xml is a global per-server file (referred to as "operational configuration" in the Oracle Coherence documentation); put this file in the Oracle CEP server config directory.

When you declare that a caching system uses the Oracle Coherence provider, be sure that all of the caches of this caching system also map to an Oracle Coherence configuration and not an Oracle CEP local configuration, or Oracle CEP throws an exception.

6.1.3.1 The tangosol-coherence-override.xml File

The tangosol-coherence-override.xml file configures Oracle Coherence clustering.

The following sample shows a simple configuration. See the explanation after the sample for information about the sections in bold.

<?xml version='1.0'?>
<coherence xml-override="/tangosol-coherence-override.xml">
  <cluster-config>
    <member-identity>
      <cluster-name>com.bea.wlevs.example.provider</cluster-name>
    </member-identity>
...
</coherence>

This configuration file is fairly standard. The main thing to note is that you should specify a cluster-name element to prevent Oracle Coherence from attempting to join existing Oracle Coherence clusters when Oracle CEP starts up; this can cause problems and sometimes even prevent Oracle CEP from starting.

For detailed information about the tangosol-coherence-override.xml file, see "Operational Override File (tangosol-coherence-override.xml)" in the Oracle Coherence Developer's Guide.

6.2 Updating an Oracle CEP Multi-Server Domain Using Oracle Coherence

Use the Configuration Wizard to add a new server to an existing standalone server domain so as to later convert it into a multi-server domain. The procedure is similar to creating a new domain, so be sure you read Section 3.1, "Creating an Oracle CEP Standalone-Server Domain" before continuing with this section.

6.2.1 How to Update an Oracle CEP Multi-Server Domain Using the Configuration Wizard in Graphical Mode

The following procedure shows how to invoke and use the Configuration Wizard in graphical mode by executing the relevant command script for both Windows or Unix.

Note:

On Windows, you can also invoke the Configuration Wizard using the Start menu:

Start > All Programs > Oracle Complex Event Processing 11gR1 > Tools > Configuration Wizard

For clarity, it is assumed that:

You have already created a new domain and its domain directory is C:\oracle_cep\user_projects\domains\mydomain.

The domain includes a single server called defaultserver and the server files are located in the C:\oracle_cep\user_projects\domains\myDomain\myServer1 directory.

You want to create a new server in the existing mydomain domain called myServer2.

To update an Oracle CEP multi-server domain using the Configuration Wizard in graphical mode:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the ORACLE_CEP_HOME/ocep_11.1/common/bin directory, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep:

prompt> cd /oracle_cep/ocep_11.1/common/bin

Invoke the config.cmd (Windows) or config.sh (UNIX) command to invoke the wizard:

prompt> ./config.sh

After the Configuration Wizard has finished loading, you will see a standard Oracle Welcome window.

Note:

The Oracle CEP Configuration Wizard is self-explanatory; however, if you want more information about using the tool, continue reading this procedure.

Click Next.

In the Choose Create or Update Domain window, choose Create a New Oracle CEP Domain.

Click Next.

Enter the name and password of the administrator user for the new server you are adding to the domain.'

Click Next.

Enter basic configuration information about the new server in the domain. If the new server is located on the same computer as any other servers in the domain, be sure the following information is different from that of the other servers to prevent conflicts when starting all servers. In particular:

Enter the name of the new server. This name will also be used as the name of the directory that contains the new server's files. Following our example, this value is myServer1.

The listen port for Oracle CEP itself.

Click Next.

Enter and confirm the password for the Oracle CEP identity keystore. By default, the password for the certificate private key will be the same as the identity keystore; if you want it to be different, clear Use Keystore Password and enter the private key password.

Click Next.

In the Configuration Options window, choose:

Yes if you want to change the default JDBC data source configuration,

No to accept the defaults.

Note:

When you deploy an application to a group in the domain, Oracle CEP replicates the application to each server that is a member of the group. This means that if your application uses a datasource, and you have configured the datasource differently for each server in the domain, then the storage and retrieval of data to and from this data source will differ depending on the server on which the application is running.

Click Next.

If you chose to change the default JDBC data source configuration, enter the information in the Configure Database Properties window.

In the top section, enter the name of the datasource. Then select the database type (Oracle or Microsoft SQL Server) and corresponding drivers; you can also browse to new drivers using the Browse/Append button.

In the lower section, enter the details about the database to which this data source connects, such as its name, the name of the computer that hosts the database server, the port, and the name and password of the user that connects to the database. The JDBC connection URL is automatically generated for you based on this information.

Click Next.

In the Configure Server window, enter the name of the existing domain and the full pathname of its location. Following our example, you would enter myDomain for the domain name and C:\oracle_cep\user_projects\domains for the domain location.

Click Create.

If the creation of the new server succeeded, you will see a message similar to the following in the Creating Domain window:

Domain created successfully!
Domain location: /oracle_cep/user_projects/domains/myDomain

Click Done.

6.3 Securing the Messages Sent Between Servers in a Multi-Server Domain

The servers in a multi-server domain update their state by exchanging multi-server-related messages. It is important that these messages be at least checked for integrity. A private key can be used to achieve integrity. This key must be shared by all servers in the domain.

This section describes:

Section 6.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence"

6.3.1 How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle Coherence

You can secure the messages sent between servers in a multi-server domain using the Oracle Coherence clustering implementation.

To secure the messages sent between servers in a multi-server domain using Oracle Coherence:

Stop all servers in your multi-server domain, if they are currently running.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Edit the config.xml file of each server in the multi-server domain by adding the security child element to the cluster element, as Example 6-6 shows.

Example 6-6 The cluster Element security Child Element

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>1</identity>
      <enabled>coherence</enabled>
      <security>encrypt</security>
  </cluster>
...
</config>

The config.xml file is located in the DOMAIN_DIR/servername/config directory of each server, where DOMAIN_DIR refers to the domain directory and servername refers to the name of your server, such as d:\oracle_cep_home\user_projects\domains\mydomain\myserver1\config.

You must specify one of the following values for the security child element:

none—Default value. Specifies that no security is configured for the multi-server domain.

encrypt—Specifies that multi-server messages should be encrypted.

Observe the correct order of child elements in the cluster element. See Section 5.5, "Order of cluster Element Child Elements".

Edit the DOMAIN_DIR/servername/config/security-config.xml file of each server in the multi-server domain by adding the encryption-service child element of the config root element, as Example 6-7 shows.

Example 6-7 The security-config.xml File encryption-service Element

<config>
  <encryption-service>
     <signature-enabled>true</signature-enabled>
  </encryption-service>
  <css-realm>
   ...
</config>

Ensure that the DOMAIN_DIR/servername/.aesinternal.dat file for each server in the multi-server domain is exactly the same by copying the file from one server to the other servers.

This file is automatically created by the Configuration Wizard when you first created the server; Oracle CEP uses this file for encrypting messages.

For example, assume all the servers in your domain are located in the d:\oracle_cep\user_projects\domains\mydomain directory, and that the domain has three servers: server1, server2, and server3. To ensure they all have the same .aesinternal.dat file, copy the one from server1 to the other servers:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\server1
prompt> cp .aesinternal.dat ..\server2
prompt> cp .aesinternal.dat ..\server3

Start one of the servers in your domain.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Because of the encryption-service element that you added to the security-config.xml file in step 3, Oracle CEP automatically creates the .msasig.dat file in the main server directory. Oracle CEP uses this file for digitally signing messages.

Stop the server you just started.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Copy the .msasig.dat file you created in step 5 to the other servers.

For example:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\server1
prompt> cp .msasig.dat ..\server2
prompt> cp .msasig.dat ..\server3

Perform the following steps on each server in the cluster:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the DOMAIN_DIR/servername directory, where DOMAIN_DIR refers to the domain directory and servername refers to the name of your server, such as d:\oracle_cep_home\user_projects\domains\mydomain\myserver1.

prompt> cd d:\oracle_cep_home\user_projects\domains\mydomain\myserver1

Create a keystore coherence-identity.jks containing the boot user using the JDK keytool utility and the following command line (broken here for readability; in practice the full command should be on one line):

prompt> keytool -genkey -v -keystore config/coherence-identity.jks
-storepass PASSWORD -alias BOOT-USER -keypass BOOT-USER-PASSWORD
-dname CN=BOOT-USER

Where:

PASSWORD is the password used to secure the keystore.

BOOT-USER is the user name you used to log into the Oracle CEP server host.

BOOT-USER-PASSWORD is the password you used when you logged into the Oracle CEP server host.

Create a permissions.xml file.

Edit the permissions.xml file to add the following permission for the boot user:

<permissions>
    <grant>
        <principal>
            <class>javax.security.auth.x500.X500Principal</class>
            <name>CN=BOOT-USER</name>
        </principal>

        <permission>
            <target>*</target>
            <action>all</action>
        </permission>
    </grant>
</permissions>

Where BOOT-USER is the user name you used to log into the Oracle CEP server host.

Save and close the permissions.xml file.

Create a login.config file.

Edit the login.config file to add the following:

Coherence {
    com.tangosol.security.KeystoreLogin required
        keyStorePath=".${/}config${/}coherence-identity.jks";
};

Save and close the login.config file.

Update the server startup script for your platform, startwlevs.cmd (Windows) or startwlevs.sh (UNIX), by adding the following property to the java command that actually starts the server:

-Djava.security.auth.login.config=./login.config

For example (in practice, the full command should be on one line):

"%JAVA_HOME%\bin\java" %DGC% %DEBUG%
-Djava.security.auth.login.config=./login.config
-Dwlevs.home="%USER_INSTALL_DIR%" -Dbea.hoe="%BEA_HOME%"
-jar "%USER_INSTALL_DIR%\bin\wlevs.jar" %1 %2 %3 %4 %5 %6

If you plan to use Oracle CEP Visualizer with the servers in this domain, see Section 10.5.3, "How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer".

Start all servers in your multi-server domain.

See Section 6.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

6.4 Using the Multi-Server Domain APIs to Manage Group Membership Changes

In an active-active system, applications are deployed homogeneously across several servers and are actively executing.

There are cases, however, when these homogeneously-deployed applications need to elect a primary one as the coordinator or leader. In this case, events that result from the coordinator application are kept and passed on to the next component in the EPN; the results of secondary servers are dropped. However, if the coordinator fails, then one of the secondary servers must be elected as the new coordinator.

To enable this in an application, the adapter or event bean, generally in the role of an event sink, must implement the com.bea.wlevs.ede.api.cluster.GroupMembershipListener interface which allows the event sinks to listen for multi-server domain group membership changes. At runtime, Oracle CEP automatically invokes the onMembershipChange callback method whenever membership changes occur.

The signature of the callback method is as follows:

onMembershipChange(Server localIdentity, Configuration groupConfiguration);

In the implementation of the onMembershipChange callback method, the event sink uses the Server object (localIdentity) to verify if it is the leader. This can be done be comparing localIdentity with the result of Configuration.getCoordinator() run on the second parameter, groupConfiguration. This parameter also allows a server to know what the current members of the group are by executing Configuration.getMembers().

Note:

There is a new API for notification groups. For more information, see "Deployment Group and Notification Group" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

In order to only keep events if it is a coordinator, the event sink must get a new Server identity every time membership in the group changes. Group membership changes occur if, for example, another server within the group fails and is no longer the coordinator.

A similar interface com.bea.wlevs.ede.api.cluster.DomainMembershipListener exists for listening to membership changes to the domain as a whole, rather than just changes to the group.

Note that in a hot-hot configuration, there is a non-zero delay in failure notification. If you are using the notification APIs to implement clustering, you will lose and not process events that occur in the window between the server failure and the notification being delivered to the new master server.

For more information, see Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing.

6.5 Starting and Stopping an Oracle CEP Server in a Multi-Server Domain

To start the servers in a multi-server domain, start each server separately by running its start script. This is the same way you start a server in a standalone server domain. See Section 3.3, "Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain" for details.

If you have not configured custom groups for the multi-server domain, then all servers are members of just the pre-defined domain group, which contains all the servers in the multi-server domain, and a singleton group, one for each member server. This means, for example, if there are three servers in the multi-server domain then there are three singleton groups.

If, however, you have configured custom groups for the multi-server domain, then the servers are members of the groups for which they have been configured, as well as the pre-defined groups.

Note:

on Windows, do not stop the Oracle CEP server by clicking the Close button in the command prompt in which you started it. Always stop the Oracle CEP server using the stopwlevs.cmd script or Ctrl-C.

7 Administrating Multi-Server Domains With Oracle CEP Native Clustering

This chapter describes how to administer Oracle Complex Event Processing (Oracle CEP) multi-server domains that are based on Oracle CEP native clustering. It describes how to create and update these domains, secure messages within them, manage group members, and start and stop servers.

Section 7.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering"

Section 7.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering"

Section 7.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

Section 7.4, "Using the Multi-Server Domain APIs to Manage Group Membership Changes"

Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain"

7.1 Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering

This section describes how to create and configure a multi-server domain from two or more Oracle CEP servers using Oracle CEP native clustering. This section includes the following:

Section 7.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle CEP Native Clustering,"

Section 7.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle CEP Native Clustering,"

Note:

To properly configure servers in a multi-server domain, you must configure them with the same multicast address and port and the same domain name. It is an error to configure servers using the same multicast address and port and port but different domain names.

7.1.1 How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle CEP Native Clustering

This procedure describes how to create a multi-server domain that uses only the two predefined groups: the singleton group and domain group. In a domain that uses default groups, all servers must be completely homogenous.

If a domain must support servers that are not completely homogeneous, you configure this by creating custom groups. See Section 7.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle CEP Native Clustering".

For more information about default and custom groups, see Section 5.2, "Groups".

Note:

In this section it is assumed that you have already created a domain that contains a single server and that you want to add additional servers to the domain to make it a multi-server domain. See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains" for details on creating a domain.

To create an Oracle CEP multi-server domain with default groups using Oracle CEP Native Clustering:

Create a domain that contains a single, initial server.

See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains".

Add one or more servers to the domain using the Configuration Wizard.

Note:

Even though the Configuration WIzard does not support adding new servers to a multi-server domain, one can use the Configuration Wizard to generate a new stand-alone server, and then manually update its configuration to join a multi-server domain.

See Section 7.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering."

Configure all the servers in the multi-server domain by manually editing their config.xml files and adding a cluster element with specific information.

To configure the servers in a multi-server domain using default groups, update the config.xml file for each member server by adding a cluster child element of the root config element as Example 7-1 shows.

Include the following child elements of cluster:

server-name: The server-name child element of cluster specifies a unique name for the server. Oracle CEP Visualizer uses the value of this element when it displays the server in its console. The default value if the element is not set is Server-identity where identity is the value of the identity element.

server-host-name: Specifies the host address/IP used for point-to-point HTTP multi-server communication. Default value is localhost.

This element is mandatory if one or more Oracle CEP servers in your multi-server domain are on different hosts and you plan to manage the multi-server domain using the Oracle CEP Visualizer. It is also mandatory if a server is deployed on a host machine that has multiple IP addresses configured (whether in a multi-server or standalone-server environment).

multicast-address: The multicast-address element is required unless all servers of the multi-server domain are hosted on the same computer; in that case you can omit the multicast-address element and Oracle CEP automatically assigns a multicast address to the multi-server domain based on the computer's IP address.

If, however, the servers are hosted on different computers, then you must provide an appropriate domain-local address. Oracle recommends you use an address of the form 239.255.X.X, which is what the auto-assigned multicast address is based on.

All the Oracle CEP servers using this multicast-address must be on the same subnet.

identity: The identity element identifies the server's identity and must be an integer between 1 and INT_MAX. Oracle CEP numerically compares the server identities during multi-server operations; the server with the lowest identity becomes the domain coordinator. Be sure that each server in the multi-server domain has a different identity; if servers have the same identity, the results of multi-server operations are unpredictable.

enabled: By default the clustering of the servers in a multi-server domain is enabled for Oracle Coherence, so to enable Oracle CEP native clustering use <enabled>evs4j</enabled>.

Note:

When adding cluster element child elements, observe the correct element order as Section 5.5, "Order of cluster Element Child Elements" describes.

Example 7-1 myServer1 config.xml File

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>1</identity>
      <enabled>evs4j</enabled>
  </cluster>
...
</config>

In Example 7-2, the server is part of a domain called myDomain.

For each server of the multi-server domain, the multicast-address elements must contain the same value. The identity and server-name elements, however, must be different for each server in the multi-server domain.

Example 7-2 shows the config.xml file of a second server, called myServer2, in the myDomain multi-server domain; note that this server's identity is 2.

Example 7-2 myServer2 config.xml File

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer2</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>2</identity>
      <enabled>evs4j</enabled>
  </cluster>
...
</config>

See Section 5.5, "Order of cluster Element Child Elements" for a description of additional multi-server-related configuration elements and the required order of child elements.

Optionally, secure the messages that are shared between the servers in a domain by configuring encryption and digital signatures.

See Section 7.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering".

To avoid a single point of failure, consider enabling Oracle CEP Visualizer on a small subset of n machines in the domain.

See "How to Start Oracle CEP Visualizer in a Multi-Server Domain" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Note:

Enabling Oracle CEP Visualizer on a given Oracle CEP Server may impact the performance of the server depending on the Oracle CEP Visualizer workload.

Start all servers in your multi-server domain.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

7.1.2 How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle CEP Native Clustering

This procedure describes how to create a multi-server domain that uses custom groups to accommodate servers which are not completely homogenous.

If all the servers in your domain are completely homogeneous, you do not need to create custom groups. Instead, you can use the predefined groups: the singleton group and domain group. See Section 7.1.1, "How to Create an Oracle CEP Multi-Server Domain With Default Groups Using Oracle CEP Native Clustering".

For more information about default and custom groups, see Section 5.2, "Groups".

Note:

In this section it is assumed that you have already created a domain that contains a single server and that you want to add additional servers to the domain to make it a multi-server domain. See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains" for details on creating a domain.

In this procedure, assume you have created three servers: myServer1, myServer2, and myServer3. You want myServer1 to be a member of the selector group and myServer2 and myServer3 to be members of the strategy group.

To create an Oracle CEP multi-server domain with custom groups using Oracle CEP Native Clustering:

Create a domain that contains a single, initial server.

See Chapter 3, "Administrating Oracle CEP Standalone-Server Domains".

Add one or more servers to the domain using the Configuration Wizard.

Note:

Even though the Configuration WIzard does not support adding new servers to a multi-server domain, one can use the Configuration Wizard to generate a new stand-alone server, and then manually update its configuration to join a multi-server domain.

See Section 7.2, "Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering."

Configure all the servers in the multi-server domain by manually editing their config.xml files and adding a cluster element with specific information.

To configure the servers in a multi-server domain using custom groups, update the config.xml file for each member server by adding (if one does not already exist) a groups child element of cluster and specifying the name of the group as the value of the groups element.

Note:

When adding cluster element child elements, observe the correct element order as Section 5.5, "Order of cluster Element Child Elements" describes.

The groups element can include more than one group name in the case that the server is a member of more than one group; separate multiple group names using commas.

The groups element is optional; if a server configuration does not include one, then the server is a member of the default groups (domain and singleton). For more information about the domain and singleton groups, see Section 5.2, "Groups".

Example 7-3, Example 7-4, and Example 7-5 show the relevant snippets of the config.xml file for each server.

Example 7-3 Server Configuration File config.xml for myServer1

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>1</identity>
      <enabled>evs4j</enabled>
      <groups>selector</groups>
  </cluster>
...
</config>

Example 7-4 Server Configuration File config.xml for myServer2

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer2</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>2</identity>
      <enabled>evs4j</enabled>
      <groups>strategy</groups>
  </cluster>
...
</config>

Example 7-5 Server Configuration File config.xml for myServer3

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer3</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>3</identity>
      <enabled>evs4j</enabled>
      <groups>strategy</groups>
  </cluster>
...
</config>

Optionally, secure the messages that are shared between the servers in a domain by configuring encryption and digital signatures.

See Section 7.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering".

To avoid a single point of failure, consider enabling Oracle CEP Visualizer on a small subset of n machines in the domain.

See "How to Start Oracle CEP Visualizer in a Multi-Server Domain" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

Note:

Enabling Oracle CEP Visualizer on a given Oracle CEP Server may impact the performance of the server depending on the Oracle CEP Visualizer workload.

Start all servers in your multi-server domain.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

7.2 Updating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering

Use the Configuration Wizard to add a new server to an existing standalone server domain so as to later convert it into a multi-server domain. The procedure is similar to creating a new domain, so be sure you read Section 3.1, "Creating an Oracle CEP Standalone-Server Domain" before continuing with this section.

7.2.1 How to Update an Oracle CEP Multi-Server Domain Using the Configuration Wizard in Graphical Mode

The following procedure shows how to invoke and use the Configuration Wizard in graphical mode by executing the relevant command script for both Windows or Unix.

Note:

On Windows, you can also invoke the Configuration Wizard using the Start menu:

Start > All Programs > Oracle Complex Event Processing 10gR3 > Tools > Configuration Wizard

For clarity, it is assumed that:

You have already created a new domain and its domain directory is C:\oracle_cep\user_projects\domains\myDomain.

The domain includes a single server called myServer1 and the server files are located in the C:\oracle_cep\user_projects\domains\myDomain\myServer1 directory.

You want to create a new server in the existing myDomain domain called myServer2.

To update an Oracle CEP multi-server domain using the Configuration Wizard in graphical mode:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the ORACLE_CEP_HOME/ocep_11.1/common/bin directory, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep:

prompt> cd /oracle_cep/ocep_11.1/common/bin

Invoke the config.cmd (Windows) or config.sh (UNIX) command to invoke the wizard:

prompt> config.sh

After the Configuration Wizard has finished loading, you will see a standard Oracle Welcome window.

Note:

The Oracle CEP Configuration Wizard is self-explanatory; however, if you want more information about using the tool, continue reading this procedure.

Click Next.

In the Choose Create or Update Domain window, choose Create a New Oracle CEP Domain.

Click Next.

Enter the name and password of the administrator user for the new server you are adding to the domain.'

Click Next.

Enter basic configuration information about the new server in the domain.

Note:

If the new server is located on the same computer as any other servers in the domain, be sure the following information is different from that of the other servers to prevent conflicts when starting all servers

In particular:

Enter the name of the new server.

This name will also be used as the name of the directory that contains the new server's files. Following our example, this value is myServer2.

The listen port for the Oracle CEP server.

Click Next.

Enter and confirm the password for the Oracle CEP identity keystore.

By default, the password for the certificate private key will be the same as the identity keystore; if you want it to be different, clear Use Keystore Password and enter the private key password.

Click Next.

In the Configuration Options window, choose:

Yes if you want to change the default JDBC data source configuration,

No to accept the defaults.

Note:

When you deploy an application to a group in the domain, Oracle CEP replicates the application to each server that is a member of the group. This means that if your application uses a datasource, and you have configured the datasource differently for each server in the domain, then the storage and retrieval of data to and from this data source will differ depending on the server on which the application is running.

Click Next.

If you chose to change the default JDBC data source configuration, enter the information in the Configure Database Properties window.

In the top section, enter the name of the datasource. Then select the database type (Oracle or Microsoft SQL Server) and corresponding drivers; you can also browse to new drivers using the Browse/Append button.

In the lower section, enter the details about the database to which this data source connects, such as its name, the name of the computer that hosts the database server, the port, and the name and password of the user that connects to the database. The JDBC connection URL is automatically generated for you based on this information.

Click Next.

In the Configure Server window, enter the name of the existing domain and the full pathname of its location.

Following our example, you would enter myDomain for the domain name and C:\oracle_cep\user_projects\domains for the domain location.

Click Create.

If the creation of the new server succeeded, you will see a message similar to the following in the Creating Domain window:

Domain created successfully!
Domain location: C:\oracle_cep\user_projects\domains\myDomain

Click Done.

7.3 Securing the Messages Sent Between Servers in a Multi-Server Domain

The servers in a multi-server domain update their state by exchanging multi-server-related messages. It is important that these messages be at least checked for integrity. A private key can be used to achieve integrity. This key must be shared by all servers in the domain.

This section describes:

Section 7.3.1, "How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering"

7.3.1 How to Secure the Messages Sent Between Servers in a Multi-Server Domain Using Oracle CEP Native Clustering

You can secure the messages sent between servers in a multi-server domain using Oracle CEP native clustering.

To secure the messages sent between servers in an Oracle CEP multi-server domain using Oracle CEP Native Clustering:

Stop all servers in your multi-server domain, if they are currently running.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Edit the config.xml file of each server in the multi-server domain by adding the security child element to the cluster element, as Example 7-6 shows.

Example 7-6 The cluster Element security Child Element

<config>
  <domain>
        <name>myDomain</name>
  </domain>
  <cluster>
      <server-name>myServer1</server-name>
      <multicast-address>239.255.0.1</multicast-address>
      <identity>1</identity>
      <enabled>coherence</enabled>
      <security>encrypt</security>
  </cluster>
...
</config>

The config.xml file is located in the DOMAIN_DIR/servername/config directory of each server, where DOMAIN_DIR refers to the domain directory and servername refers to the name of your server, such as d:\oracle_cep_home\user_projects\domains\mydomain\myserver1\config.

You must specify one of the following values for the security child element:

none—Default value. Specifies that no security is configured for the multi-server domain.

encrypt—Specifies that multi-server messages should be encrypted.

Observe the correct order of child elements in the cluster element. See Section 5.5, "Order of cluster Element Child Elements".

Edit the DOMAIN_DIR/servername/config/security-config.xml file of each server in the multi-server domain by adding the encryption-service child element of the config root element, as Example 7-7 shows.

Example 7-7 The security-config.xml File encryption-service Element

<config>
  <encryption-service>
     <signature-enabled>true</signature-enabled>
  </encryption-service>
  <css-realm>
   ...
</config>

Ensure that the DOMAIN_DIR/servername/.aesinternal.dat file for each server in the multi-server domain is exactly the same by copying the file from one server to the other servers.

This file is automatically created by the Configuration Wizard when you first created the server; Oracle CEP uses this file for encrypting messages.

For example, assume all the servers in your domain are located in the d:\oracle_cep\user_projects\domains\mydomain directory, and that the domain has three servers: server1, server2, and server3. To ensure they all have the same .aesinternal.dat file, copy the one from server1 to the other servers:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\server1
prompt> cp .aesinternal.dat ..\server2
prompt> cp .aesinternal.dat ..\server3

Start one of the servers in your domain.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Because of the encryption-service element that you added to the security-config.xml file in step 3, Oracle CEP automatically creates the .msasig.dat file in the main server directory. Oracle CEP uses this file for digitally signing messages.

Stop the server you just started.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

Copy the .msasig.dat file you created in step 5 to the other servers.

For example:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\server1
prompt> cp .msasig.dat ..\server2
prompt> cp .msasig.dat ..\server3

If you plan to use Oracle CEP Visualizer with the servers in this domain, see Section 10.5.3, "How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer".

Start all servers in your multi-server domain.

See Section 7.5, "Starting and Stopping an Oracle CEP Server in a Multi-Server Domain".

7.4 Using the Multi-Server Domain APIs to Manage Group Membership Changes

In an active-active system, applications are deployed homogeneously across several servers and are actively executing.

There are cases, however, when these homogeneously-deployed applications need to elect a primary one as the coordinator or leader. In this case, events that result from the coordinator application are kept and passed on to the next component in the EPN; the results of secondary servers are dropped. However, if the coordinator fails, then one of the secondary servers must be elected as the new coordinator.

To enable this in an application, the adapter or event bean, generally in the role of an event sink, must implement the com.bea.wlevs.ede.api.cluster.GroupMembershipListener interface which allows the event sinks to listen for multi-server domain group membership changes. At runtime, Oracle CEP automatically invokes the onMembershipChange callback method whenever membership changes occur.

The signature of the callback method is as follows:

onMembershipChange(Server localIdentity, Configuration groupConfiguration);

In the implementation of the onMembershipChange callback method, the event sink uses the Server object (localIdentity) to verify if it is the leader. This can be done be comparing localIdentity with the result of Configuration.getCoordinator() run on the second parameter, groupConfiguration. This parameter also allows a server to know what the current members of the group are by executing Configuration.getMembers().

In order to only keep events if it is a coordinator, the event sink must get a new Server identity every time membership in the group changes. Group membership changes occur if, for example, another server within the group fails and is no longer the coordinator.

A similar interface com.bea.wlevs.ede.api.cluster.DomainMembershipListener exists for listening to membership changes to the domain as a whole, rather than just changes to the group.

Note that in a hot-hot configuration, there is a non-zero delay in failure notification. If you are using the notification APIs to implement clustering, you will lose and not process events that occur in the window between the server failure and the notification being delivered to the new master server.

For more information, see Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing.

7.5 Starting and Stopping an Oracle CEP Server in a Multi-Server Domain

To start the servers in a multi-server domain, start each server separately by running its start script. This is the same way you start a server in a standalone server domain. See Section 3.3, "Starting and Stopping an Oracle CEP Server in a Standalone-Server Domain" for details.

If you have not configured custom groups for the multi-server domain, then all servers are members of just the pre-defined domain group, which contains all the servers in the multi-server domain, and a singleton group, one for each member server. This means, for example, if there are three servers in the multi-server domain then there are three singleton groups.

If, however, you have configured custom groups for the multi-server domain, then the servers are members of the groups for which they have been configured, as well as the pre-defined groups.

8 Deploying Applications to Multi-Server Domains

This chapter describes how to deploy applications to Oracle Complex Event Processing (Oracle CEP) multi-server domains using Oracle CEP Visualizer or the deployer utility, as well as how to troubleshoot deployment.

Section 8.1, "Overview of Deploying an Application to an Oracle CEP Multi-Server Domain"

Section 8.2, "Deploying to an Oracle CEP Server Using the Oracle CEP Visualizer"

Section 8.3, "Deploying to an Oracle CEP Server Singleton Group Using the Deployer Utility"

Section 8.4, "Deploying to an Oracle CEP Server Domain Group Using the Deployer Utility"

Section 8.5, "Deploying to an Oracle CEP Server Custom Group Using the Deployer Utility"

Section 8.6, "Troubleshooting Multi-Server Domain Deployment"

8.1 Overview of Deploying an Application to an Oracle CEP Multi-Server Domain

When you deploy an application to a multi-server domain, you typically specify a target group, and Oracle CEP then deploys the application to the set of running servers in that group. Oracle CEP dynamically maintains group membership based on running servers. This means that if new servers in the group are started, Oracle CEP automatically propagates the appropriate set of deployments to the new server.

Take, for example, the simple multi-server domain configured in the section Section 6.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence." Assume that only myServer1 had been started, and then an application is deployed to the domain group, which includes myServer1 and myServer2. At that point, because only myServer1 of the multi-server domain has been started, the application will be deployed only to myServer1. When myServer2 is subsequently started, Oracle CEP automatically replicates and propagates the deployment of the application to myServer2 without the user having the explicitly deploy it.

Deployment propagation occurs based on application version. When you deploy a new version of an application, the new version is propagated to all servers accordingly.

If different configuration is required on different servers for an application then currently it is best to achieve this by using system properties.

This section describes how to perform the following tasks:

Section 8.2, "Deploying to an Oracle CEP Server Using the Oracle CEP Visualizer"

Section 8.3, "Deploying to an Oracle CEP Server Singleton Group Using the Deployer Utility"

Section 8.4, "Deploying to an Oracle CEP Server Domain Group Using the Deployer Utility"

Section 8.5, "Deploying to an Oracle CEP Server Custom Group Using the Deployer Utility"

Section 8.6, "Troubleshooting Multi-Server Domain Deployment"

For more information, see:

Section 5.2, "Groups"

Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Appendix B, "Deployer Command-Line Reference"

8.2 Deploying to an Oracle CEP Server Using the Oracle CEP Visualizer

The simplest way to deploy an Oracle CEP application to a multi-server domain is to use the Oracle CEP Visualizer.

For more information, see "Deploying an Application" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

8.3 Deploying to an Oracle CEP Server Singleton Group Using the Deployer Utility

If you do not specify a group when you deploy an application, Oracle CEP deploys the application to the singleton server group that includes only the specific server to which you deploy the application. This is the standard case in single-server domains, but is also applicable to multi-server domains.

Note:

When you upgrade a 2.0 domain to execute in a multi-server domain, any deployed applications are deployed to the singleton server group.

The following example shows how to deploy to a singleton group; note that the command does not specify a -group option (in practice, the full command should be on one line):

prompt> java -jar wlevsdeploy.jar -url http://ariel:9002/wlevsdeployer
-install myapp_1.0.jar

In the example, the myapp_1.0.jar application will be deployed to the singleton server group that contains a single server: the one running on host ariel and listening to port 9002. If the domain is multi-server and other servers are members of the domain group, the application will not be deployed to these servers.

For more information about groups, see Section 5.2, "Groups".

8.4 Deploying to an Oracle CEP Server Domain Group Using the Deployer Utility

The domain group is a live group that always exists and contains all servers in a domain. In another words, all servers are always a member of the domain group. However, you must still explicitly deploy applications to the domain group. The main reason for this is for simplicity and consistency in usage.

When you explicitly deploy an application to the domain group, Oracle CEP guarantees that all servers of this homogenous environment have this deployment.

To deploy to the domain group, use the -group all option. The following example shows how to deploy to a domain group:

prompt> java -jar wlevsdeploy.jar -url http://ariel:9002/wlevsdeployer -install myapp_1.0.jar -group all

In the example, the myapp_1.0.jar application will be deployed to all servers of the domain group on host ariel listening to port 9002.

For more information about groups, see Section 5.2, "Groups".

8.5 Deploying to an Oracle CEP Server Custom Group Using the Deployer Utility

To deploy to a custom group, use the -group groupname option of the deploy command.

In the following examples, assume the multi-server domain has been configured as described in Section 6.1.2, "How to Create an Oracle CEP Multi-Server Domain With Custom Groups Using Oracle Coherence."

The following example shows how to deploy an application called strategies_1.0.jar to the strategygroup (in practice, the full command should be on one line):

prompt> java -jar wlevsdeploy.jar -url http://ariel:9002/wlevsdeployer
-install strategies_1.0.jar -group strategygroup

Based on the multi-server domain configuration, the preceding command deploys the application to myServer2 and myServer3, the members of the group strategygroup.

The following example shows how to deploy an application called selector_1.0.jar to the selectorgroup (in practice, the full command should be on one line):

prompt> java -jar wlevsdeploy.jar -url http://ariel:9002/wlevsdeployer
-install selector_1.0.jar -group selectorgroup

Based on the multi-server domain configuration, the preceding command deploys the application only to myServer1, which is the sole member of group selectorgroup.

Note that both commands are executed to the same server (the one on host ariel listening to port 9002). However, you can specify any of the servers in the domain in the deploy command, even if the server is not part of the group to which you want to deploy the application.

For more information about groups, see Section 5.2, "Groups".

8.6 Troubleshooting Multi-Server Domain Deployment

This section describes common problems that you may encounter when deploying applications to an Oracle CEP multi-server domain, including:

Section 8.6.1, "Oracle CEP Server Stops Application After Deployment"

8.6.1 Oracle CEP Server Stops Application After Deployment

Problem: After you deploy an application to an Oracle CEP multi-server domain, Oracle CEP stops the application after about 30 seconds.

Solution: Be sure you do not have more than one VPN software package installed on the same computer hosting your multi-server domain.

Part IV

Configuring Services

Part IV contains the following chapters:

Chapter 9, "Configuring Network I/O for Oracle CEP"

Chapter 10, "Configuring Security for Oracle CEP"

Chapter 11, "Configuring Jetty for Oracle CEP"

Chapter 12, "Configuring JMX for Oracle CEP"

Chapter 13, "Configuring JDBC for Oracle CEP"

Chapter 14, "Configuring HTTP Publish-Subscribe for Oracle CEP"

Chapter 15, "Configuring Logging and Debugging for Oracle CEP"

The script content on this page is for navigation purposes only and does not alter the content in any way.

9 Configuring Network I/O for Oracle CEP

This chapter describes how to configure network I/O in Oracle Complex Event Processing (Oracle CEP), including how to configure either a network I/O server or client.

Section 9.1, "Overview of Network I/O in Oracle CEP"

Section 9.2, "Configuring Network I/O Server (netio)"

Section 9.3, "Configuring Network I/O Client (netio-client)"

9.1 Overview of Network I/O in Oracle CEP

Oracle CEP supports network Input/Output (I/O) over Transmission Control Protocol/Internet Protocol (TCP/IP) using a variety of providers in both server and client mode.

You may define a network I/O service for both Secure Socket Layer (SSL) and non-SSL network access.

Oracle CEP supports both IPv4 and IPv6.

The following Oracle CEP services depend on network I/O configuration:

jetty: depends on network I/O server (netio) configuration.

weblogic-rmi-client: depends on network I/O client (netio-client) configuration.

For more information, see:

Section 9.1.1, "Network I/O Providers"

Section 9.1.2, "IPv4 and IPv6 Support"

Section 9.2, "Configuring Network I/O Server (netio)"

Section 9.3, "Configuring Network I/O Client (netio-client)"

Chapter 10, "Configuring Security for Oracle CEP"

Chapter 11, "Configuring Jetty for Oracle CEP"

9.1.1 Network I/O Providers

Table 9-1 lists the network I/O providers that Oracle CEP supports.

Table 9-1 Oracle CEP Network I/O Providers

provider-type
SSL?
Description

non-blocking

No

A non-blocking provider provides fully non-blocking I/O for reads and writes. That means that each call to read or write on the Connection interface will return immediately without blocking. If the underlying connection is not ready, then the read or write call will simply return zero. At that point, the calling code must use one of the notification mechanisms in the NetIO API to wait until the connection is ready to read or write. Non-Blocking providers may also support a non-blocking connect call, which means that a thread need not block if it takes a long time to establish (or fail to establish) a connection to a remote server.

Provider class: com.bea.core.netio.provider.noblock.NIOEngine.

semi-blocking

No

A semi-blocking provider provides non-blocking I/O for the read call, but each write call blocks until the data has been handed to the TCP/IP stack. Some platforms provide mechanisms that make it possible to implement a write-blocking provider that is faster than a fully non-blocking provider, but still allows for high scalability.

Provider class:

Linux with JRockit: com.bea.core.netio.provider.jrockit.JRockitEngine

Windows: com.bea.core.netio.provider.nativeasync.NativeAsyncEngine

blocking

No

A blocking provider blocks on each read and write call until it is complete. If there is no data ready to read, then read will block until there is. This type of provider is much less scalable because there must be a thread waiting for each network connection that might have data. Oracle recommends that this type of provider should not typically be used.

Provider class: com.bea.core.netio.provider.block.BlockingEngine.

native

No

The NativeAsyncEngine will be tried. If it is not supported, then an error will be raised.

NIOFoot 1 

Yes

The NIOEngine will always be used.

Footnote 1 Default provider-type.

Example 9-1 shows how to specify a provider in the Oracle CEP server config.xml file netio element using the provider-type child element.

Example 9-1 Oracle CEP netio Element With provider-type Defined

<netio>
    <name>myNetio</name>
    <port>12345</port>
    <provider-type>non-blocking</provider-type>
</netio>

9.1.2 IPv4 and IPv6 Support

Oracle CEP server is certified for use with IPv4 only or IPv4/IPv6 dual-stack.

Oracle CEP does not support IPv6.

For more information about IPv6, see RFC 2460: Internet Protocol, Version 6 (IPv6) Specification (http://www.ietf.org/rfc/rfc2460.txt).

9.2 Configuring Network I/O Server (netio)

You can define a network I/O service that may be used by other services to act as the server and listen for incoming connections.

Alternatively, you can create a client network I/O service as Section 9.3, "Configuring Network I/O Client (netio-client)" describes.

9.2.1 How to Configure Network I/O Server

You configure network I/O server services using the netio element in the Oracle CEP server config.xml file.

For more information, see:

Section 1.3.1, "Oracle CEP Server Configuration Files"

Section 9.1.1, "Network I/O Providers"

"netio" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

To configure network I/O server:

In the Oracle CEP server config.xml file, create a netio element as Example 9-2 shows.

Example 9-2 Oracle CEP netio Element

<netio>
</netio>

Add a name element that uniquely identifies this netio element on this Oracle CEP server as Example 9-3 shows.

Example 9-3 Oracle CEP netio Element With name Element

<netio>
    <name>MyNetIO</name>
</netio>

Add a port element to define the TCP/IP port on which this netio service will listen for connection requests as Example 9-4 shows.

Example 9-4 Oracle CEP netio Element With port Element

<netio>
    <name>MyNetIO</name>
    <port>9002</port>
</netio>

Optionally, specify a provider-type as Example 9-5 shows.

Example 9-5 Oracle CEP netio Element With port Element

<netio>
    <name>MyNetIO</name>
    <port>9002</port>
    <provider-type>NIO</provider-type>
</netio>

For more information, see Section 9.1.1, "Network I/O Providers".

Optionally, specify the other netio child elements.

For more information, see "netio" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

9.3 Configuring Network I/O Client (netio-client)

You can define a network I/O service that may be used to perform non-blocking network I/O, but which will not act as a server and will not listen for incoming connections.

Alternatively, you can create a server network I/O service as Section 9.2, "Configuring Network I/O Server (netio)" describes.

9.3.1 How to Configure Network IO Client

You configure network I/O client services using the netio-client element in the Oracle CEP server config.xml file.

For more information, see:

Section 1.3.1, "Oracle CEP Server Configuration Files"

Section 9.1.1, "Network I/O Providers"

"netio-client" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

To configure network I/O client:

In the Oracle CEP server config.xml file, create a netio-client element as Example 9-2 shows.

Example 9-6 Oracle CEP netio-client Element

<netio-client>
</netio-client>

Add a name element that uniquely identifies this netio element on this Oracle CEP server as Example 9-3 shows.

Example 9-7 Oracle CEP netio-client Element With name Element

<netio-client>
    <name>MyNetIOClient</name>
</netio-client>

Optionally, specify a provider-type as Example 9-5 shows.

Example 9-8 Oracle CEP netio-client Element With port Element

<netio-client>
    <name>MyNetIOClient</name>
    <provider-type>NIO</provider-type>
</netio-client>

For more information, see Section 9.1.1, "Network I/O Providers".

Optionally, specify the other netio-client child elements.

For more information, see "netio-client" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

10 Configuring Security for Oracle CEP

This chapter describes how to configure security in Oracle Complex Event Processing (Oracle CEP), including configuring a security provider, SSL and FIPS, as well as configuring HTTPS-only connections and the security auditor.

Section 10.1, "Overview of Security in Oracle CEP"

Section 10.2, "Configuring Java SE Security for Oracle CEP Server"

Section 10.3, "Configuring a Security Provider"

Section 10.4, "Configuring Password Strength"

Section 10.5, "Configuring SSL to Secure Network Traffic"

Section 10.6, "Configuring FIPS for Oracle CEP Server"

Section 10.7, "Configuring HTTPS-Only Connections for Oracle CEP Server"

Section 10.8, "Configuring Security for Oracle CEP Server Services"

Section 10.9, "Configuring Cross-Domain Security for Oracle CEP Visualizer"

Section 10.10, "Configuring the Oracle CEP Security Auditor"

Section 10.11, "Disabling Security"

10.1 Overview of Security in Oracle CEP

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.

To configure security for Oracle CEP server, consider the following general tasks:

Configure Java SE security.

See Section 10.1.1, "Java SE Security".

Configure a security provider for authorization and authentication.

See:

Section 10.1.2, "Security Providers"

Section 10.1.3, "Users, Groups, and Roles"

Configure password strength.

See Section 10.4, "Configuring Password Strength".

Configure SSL and FIPS.

See:

Section 10.1.4, "SSL"

Section 10.1.5, "FIPS"

Configure HTTPS-only connections.

See Section 10.7, "Configuring HTTPS-Only Connections for Oracle CEP Server".

Configure security for individual Oracle CEP server services.

See Section 10.8, "Configuring Security for Oracle CEP Server Services"

For more information, see:

Section 10.1.6, "Enabling and Disabling Security"

Section 10.1.7, "Security Utilities"

Section 10.1.8, "Specifying User Credentials When Using the Command-Line Utilities"

Section 10.1.9, "Security in Oracle CEP Examples and Domains"

10.1.1 Java SE Security

You can define Java SE security policies for:

All the bundles that make up Oracle CEP

Server startup

Web applications deployed to the Oracle CEP server Jetty HTTP server

Oracle CEP Visualizer

For more information, see:

Section 10.2, "Configuring Java SE Security for Oracle CEP Server"

http://java.sun.com/javase/technologies/security/

10.1.2 Security Providers

Oracle CEP supports various security providers for authentication, authorization, role mapping, and credential mapping.

Oracle CEP supports the following security providers:

File-based—Default out-of-the-box security provider. This type of provider uses an operating system file to access security data such as user, password, and group information. Provides both authentication (process whereby identity of users is proved or verified) and authorization (process whereby a user's access to an Oracle CEP resource is permitted or denied based on the user's security role and the security policy assigned to the requested Oracle CEP resource). Authentication typically involves username/password combinations.

LDAP—Provider that uses a Lightweight Data Access Protocol (LDAP) server to access user, password, and group information. Provides only authentication.

DBMS—Provider that uses a database management system (DBMS) to access user, password, and group information. Provides both authentication and authorization.

If you choose to use the default file-based security provider, then you do not need to do any further configuration of your domain; the Configuration Wizard performs all necessary configuration. However, if you want to use the LDAP or DBMS providers, you must perform further configuration. See Section 10.3, "Configuring a Security Provider"

Once you have configured the security provider, you can start using Oracle CEP Visualizer to add new users, assign them to groups, and map groups to roles. See Section 10.1.3, "Users, Groups, and Roles".

10.1.3 Users, Groups, and Roles

Oracle CEP uses role-based authorization control to secure the Oracle CEP Visualizer and the wlevs.Admin command-line utility. There are a variety of default out-of-the-box security groups. You can add users to different groups to give them the different roles.

Administrators who use Oracle CEP Visualizer, wlevs.Admin, or any custom administration application that uses JMX to connect to an Oracle CEP instance use role-based authorization to gain access.

You can also use role-based authorization to control access to the HTTP publish-subscribe server.

There are two types of role:

Application roles: application roles grant users the permission to access various Oracle CQL applications deployed to the Oracle CEP server. You can create application roles and associate them with the task roles that Oracle CEP provides.

By default, administrator users can access any application and non-administration users cannot access any applications. Before a none-administration user can access an application, an administration user must grant the user the associated application role.

Task roles: task roles grant users the permission to perform various tasks with the applications their application role authorizes them to access. Oracle CEP provides the default task roles that Table 10-1 describes.

Users that successfully authenticate themselves when using Oracle CEP Visualizer or wlevs.Admin are assigned roles based on their group membership, and then subsequent access to administrative functions is restricted according to the roles held by the user. Anonymous users (non-authenticated users) will not have any access to the Oracle CEP Visualizer or wlevs.Admin.

When an administrator uses the Configuration Wizard to create a new domain, they enter an administrator user that will be part of the wlevsAdministrators group. By default, this information is stored in a file-based provider filestore. The password is hashed using the SHA-256 algorithm. The default administrator user is named wlevs with password wlevs.

Table 10-1 describes the default Oracle CEP tasks roles available right after the creation of a new domain, as well as the name of the groups that are assigned to these roles.

Table 10-1 Default Oracle CEP Task Roles and Groups

Task Role
Group
Privileges

Admin

wlevsAdministrators

Has all privileges of all the preceding roles, as well as permission to:

Create users and groups

Configure HTTP publish-subscribe security

Change the system configuration, such as Jetty, work manager, and so on.

ApplicationAdmin

wlevsApplicationAdmins

Has all Operator privileges as well as permission to update the configuration of any deployed application.

BusinessUser

wlevsBusinessUsers

Has all Operator privileges as well as permission to update the Oracle CQL and EPL rules associated with the processor of a deployed application.

Deployer

wlevsDeployers

Has all Operator privileges as well as permission to deploy, undeploy, update, suspend, and resume any deployed application.

Monitor

wlevsMonitors

Has all Operator privileges as well as permission to enable/disable diagnostic functions, such as creating a diagnostic profile and recording events (then playing them back.)

Operator

wlevsOperators

Has read-only access to all server resources, services, and deployed applications.

Once the domain has been created, the administrator can use Oracle CEP Visualizer to create a group and associate it with one or more roles: each role grants access to an application. When you assign a user to a group, the roles you associate with the group give the user the privileges to access those applications.

For instructions on using Oracle CEP Visualizer to modify users, groups, and roles, see:

"Managing Users" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

"Managing Groups" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

"Managing Roles" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

For more information, see:

Section 10.8.4, "Configuring HTTP Publish-Subscribe Server Channel Security"

Section 10.1.8, "Specifying User Credentials When Using the Command-Line Utilities"

Chapter 3, "Administrating Oracle CEP Standalone-Server Domains"

Chapter 6, "Administrating Multi-Server Domains With Oracle Coherence"

Chapter 7, "Administrating Multi-Server Domains With Oracle CEP Native Clustering"

10.1.4 SSL

Oracle CEP provides one-way Secure Sockets Layer (SSL) to secure network traffic between Oracle CEP Visualizer and Oracle CEP server instances, between the Oracle CEP server instances of a multi-server domain, and between the wlevs.Admin command-line utility and Oracle CEP server instances.

You can configure Oracle CEP to use a Federal Information Processing Standards (FIPS)-certified pseudo-random number generator for SSL.

For more information, see:

Section 10.5, "Configuring SSL to Secure Network Traffic"

Section 10.1.5, "FIPS"

Section 6.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

Oracle Coherence: Section 7.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

Oracle CEP Native Clustering: Section A.4, "Running wlevs.Admin Utility in SSL Mode"

10.1.5 FIPS

The National Institute of Standards and Technology (NIST) creates standards for Federal computer systems. NIST issues these standards as Federal Information Processing Standards (FIPS) for use government-wide.

Oracle CEP supports FIPS using the com.rsa.jsafe.provider.JsafeJCE security provider. Using this provider, you can configure Oracle CEP to use a FIPS-certified pseudo-random number generator for SSL.

For more information, see:

Section 10.6, "Configuring FIPS for Oracle CEP Server"

Section 10.1.4, "SSL"

http://www.itl.nist.gov/fipspubs/

10.1.6 Enabling and Disabling Security

After you configure SSL, you can configure the Oracle CEP server to accept only client requests on the HTTPS port. See Section 10.7, "Configuring HTTPS-Only Connections for Oracle CEP Server".

Optionally, you can disable security. See Section 10.11, "Disabling Security".

10.1.7 Security Utilities

Oracle CEP provides a variety of command-line utilities to simplify security administration. In addition to command-line utilities, you can use Oracle CEP Visualizer to perform many security tasks.

For more information, see:

Appendix C, "Security Utilities Command-Line Reference"

Section 10.1.8, "Specifying User Credentials When Using the Command-Line Utilities"

"Security Tasks" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

10.1.8 Specifying User Credentials When Using the Command-Line Utilities

Oracle CEP provides the following command-line utilities for performing a variety of tasks:

wlevs.Admin: a command-line interface to administer Oracle CEP and, in particular, dynamically configure the rules for Oracle CQL and EPL processors and monitor the event latency and throughput of an application.

See Appendix A, "wlevs.Admin Command-Line Reference" for details

Deployer: a Java-based deployment utility that provides administrators and developers command-line based operations for deploying Oracle CEP applications.

See Appendix B, "Deployer Command-Line Reference" for details.

cssconfig: a command-line utility to generate a security configuration file (security.xml) that uses a password policy.

See Appendix C, "The cssconfig Command-Line Utility" for details.

encryptMSAConfig: an encryption command-line utility to encrypt cleartext passwords, specified by the password element, in XML files.

See Appendix C, "The encryptMSAConfig Command-Line Utility" for details.

For each utility, you can specify user credentials (username and password) using the following three methods:

On the command line using options such as -user and -password.

Interactively so that the command line utility always prompts for the credentials.

Specifying a filestore that stores the user credentials; the filestore itself is also password protected.

In a production environment you should never use the first option (specifying user credentials on the command line) but rather use only the second and third option.

When using interactive mode (command-line utility prompts for credentials), be sure you have the appropriate terminalio native libraries for your local computer in your CLASSPATH so that the user credentials are not echoed on the screen when you type them. Oracle CEP includes a set of standard native libraries for this purpose, but it may not include the specific one you need.

10.1.9 Security in Oracle CEP Examples and Domains

When you use the Configuration Wizard to create a new domain, you specify the administrator user and password, as well as the password to the domain identity keystore. This user is automatically added to the wlevsAdministrators group. All security configuration is stored using a file-based provider, by default.

All Oracle CEP examples are configured to have an administrator with username wlevs and password wlevs. When you create a new domain you specify the administrator name and password.

By default, security is disabled in the HelloWorld example. This means that any user can start the server, deploy applications, and run all commands of the administration tool (wlevs.Admin) without providing a password.

Security is enabled in the FX and AlgoTrading examples. In both examples, the user wlevs, with password wlevs, is configured to be the Oracle CEP administrator with full administrator privileges. The scripts to start the server for these examples use the appropriate arguments to pass this username and password to the java command. If you use the Deployer or wlevs.Admin utility, you must also pass this username/password pair using the appropriate arguments.

For more information, see Section 10.1.8, "Specifying User Credentials When Using the Command-Line Utilities".

10.2 Configuring Java SE Security for Oracle CEP Server

The Java SE platform defines a standards-based and interoperable security architecture that is dynamic and extensible. Security features — cryptography, authentication and authorization, public key infrastructure, and more — are built in.

Oracle CEP supports Java SE security by using the following security policies:

policy.xml—Defines the security policies of all the bundles that make up Oracle CEP. The first bundle set defines the policies for server-related bundles; the second bundle set defines the policies for application bundles.

security.policy—Defines the security policies for server startup and Web applications deployed to the Jetty HTTP server. This file also defines policies for the Oracle CEP Visualizer Web application.

Samples of the preceding files are shipped with the product and can be found in ORACLE_CEP_HOME/ocep_11.1/utils/security, where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP, such as /oracle_home.

You can enable all Java SE security features with Oracle CEP.

For more information, see Section 10.1.1, "Java SE Security".

To configure Java SE security on the Oracle CEP server:

Stop the Oracle CEP server, if it is currently running.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Copy policy.xml and security.policy:

From: ORACLE_CEP_HOME/ocep_11.1/utils/security

To: DOMAIN_DIR/servername/config

Where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP (such as /oracle_home), DOMAIN_DIR refers to the main Oracle CEP installation directory, servername refers to the name of your server (such as /oracle_cep/user_projects/domains/mydomain/myserver/config).

Edit the two security policy files to suit your needs.

Update the server startup script for your platform located in the DOMAIN_DIR/servername directory, startwlevs.cmd (Windows) or startwlevs.sh (UNIX), by adding the following three properties to the java command that actually starts the server:

-Djava.security.manager
-Djava.security.policy=./config/security.policy
-Dcom.bea.core.security.policy=./config/policy.xml

For example (in practice, the full command should be on one line):

"%JAVA_HOME%\bin\java" %DGC% %DEBUG% -Djava.security.manager
-Djava.security.policy=./config/security.policy
-Dcom.bea.core.security.policy=./config/policy.xml
-Dwlevs.home="%USER_INSTALL_DIR%" -Dbea.hoe="%BEA_HOME%"
-jar "%USER_INSTALL_DIR%\bin\wlevs.jar" %1 %2 %3 %4 %5 %6

Update the DOMAIN_DIR/servername/config/config.xml file of your Oracle CEP server and edit the Jetty configuration by adding a <scratch-directory> child element of the <jetty> element to specify the directory to which Jetty Web applications are deployed. For example:

<jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
    <secure-network-io-name>sslNetIo</secure-network-io-name>
    <scratch-directory>./JettyWork</scratch-directory>
</jetty>

Restart the Oracle CEP server for the changes to take effect.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

10.3 Configuring a Security Provider

A security provider performs authentication, authorization, or both.

Oracle CEP server supports file-based, LDAP, and DBMS security providers.

The file-based security provider is the default security provider that the Configuration Wizard configures. If you want to use the file-based security provider, no further configuration is required.

The LDAP security provider supports authentication only.

The DBMS security provider supports both authentication and authorization.

This section describes:

Section 10.3.1, "Configuring Authentication Using the LDAP Provider and Authorization Using the DBMS Provider"

Section 10.3.2, "Configuring Both Authentication and Authorization Using the DBMS Provider"

For more information, see Section 10.1.2, "Security Providers".

10.3.1 Configuring Authentication Using the LDAP Provider and Authorization Using the DBMS Provider

The following procedure describes how to configure the LDAP security provider for authentication and the DBMS provider for authorization.

Caution:

When using LDAP for authentication, you can not add or delete users and groups using Oracle CEP Visualizer, you can only change the password of a user.

To configure authentication using the LDAP provider and Authorization using the DBMS provider:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Add the ORACLE_CEP_HOME\ocep_11.1\bin directory to your PATH environment variable, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep:

prompt> set PATH=d:\oracle_cep\ocep_11.1\bin;%PATH% (Windows)
prompt> PATH=/oracle_cep/ocep_11.1/bin:$PATH (UNIX)

Change to the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the main directory of your domain, such as d:\oracle_cep\user_projects\domains\mydomain, and servername refers to the name of your server:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\defaultserver\config

Using your favorite text editor, create a file called myLDAPandDBMS.properties and copy into it the entire contents of Example 10-1.

Example 10-1 LDAP/DBMS Properties File

# For attributes of type boolean or Boolean, value can be "true" or "false"
# and it's case insensitive.
# For attributes of type String[], values are comma separated; blanks before
# and after the comma are ignored. For example, if the property is defined as:
#   saml1.IntersiteTransferURIs=uri1, uri2, uri3
# the IntersiteTransferURIs attribute value is String[]{"uri1", "uri2", "uri3"}
# For attributes of type Properties, the value should be inputted as
# a set of key=value pairs separated by commas; blanks before and after the
# commas are also ignored. For example (in practice, the property should be all on one line):
#  store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
ConnectionURL=jdbc:oracle:thin:@united.bea.com:1521:xe, Username=user, Password=user
domain.mbean=com.bea.common.management.configuration.LegacyDomainInfoMBean
domain.DomainName=legacy-domain-name
domain.ServerName=legacy-server-name
domain.RootDirectory=legacy-rootdir
#domain.ProductionModeEnabled=
#domain.WebAppFilesCaseInsensitive=
domain.DomainCredential=changeit
jaxp.mbean=com.bea.common.management.configuration.JAXPFactoryServiceMBean
#jaxp.DocBuilderFactory=
#jaxp.SaxParserFactory=
#jaxp.SaxTransformFactory=
#jaxp.TransformFactory=
#ldapssl.mbean=com.bea.common.management.configuration.LDAPSSLSocketFactoryLookupServiceMBean
#ldapssl.Protocol=
#ldapssl.TrustManagerClassName=
namedsql.mbean=com.bea.common.management.configuration.NamedSQLConnectionLookupServiceMBean
store.mbean=com.bea.common.management.configuration.StoreServiceMBean
# Split here for readability; in practice, a property should be all on one line.
store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
    ConnectionURL=jdbc:oracle:thin:@localhost:1521:orcl, Username=wlevs, Password=wlevs
#store.ConnectionProperties=
#store.NotificationProperties=
realm.mbean=weblogic.management.security.RealmMBean
realm.Name=my-realm
#realm.ValidateDDSecurityData=
#realm.CombinedRoleMappingEnabled=
#realm.EnableWebLogicPrincipalValidatorCache=
#realm.MaxWebLogicPrincipalsInCache=
#realm.DelegateMBeanAuthorization=
#realm.AuthMethods=
adt.1.mbean=weblogic.security.providers.audit.DefaultAuditorMBean
adt.1.Severity=INFORMATION
#adt.1.InformationAuditSeverityEnabled=
#adt.1.WarningAuditSeverityEnabled=
#adt.1.ErrorAuditSeverityEnabled=
#adt.1.SuccessAuditSeverityEnabled=
#adt.1.FailureAuditSeverityEnabled=
#adt.1.OutputMedium=
#adt.1.RotationMinutes=
#adt.1.BeginMarker=
#adt.1.EndMarker=
#adt.1.FieldPrefix=
#adt.1.FieldSuffix=
adt.1.Name=my-auditor
#adt.1.ActiveContextHandlerEntries=
atn.1.mbean=weblogic.security.providers.authentication.LDAPAuthenticatorMBean
#atn.1.UserObjectClass=
#atn.1.UserNameAttribute=
#atn.1.UserDynamicGroupDNAttribute=
atn.1.UserBaseDN=o=ECS,dc=bea,dc=com
atn.1.UserSearchScope=subtree
#atn.1.UserFromNameFilter=
#atn.1.AllUsersFilter=
atn.1.GroupBaseDN=ECS,dc=bea,dc=com
#atn.1.GroupSearchScope=
#atn.1.GroupFromNameFilter=
#atn.1.AllGroupsFilter=
#atn.1.StaticGroupObjectClass=
#atn.1.StaticGroupNameAttribute=
atn.1.StaticMemberDNAttribute=member
#atn.1.StaticGroupDNsfromMemberDNFilter=
#atn.1.DynamicGroupObjectClass=
#atn.1.DynamicGroupNameAttribute=
#atn.1.DynamicMemberURLAttribute=
atn.1.GroupMembershipSearching=unlimited
atn.1.MaxGroupMembershipSearchLevel=0
atn.1.UseRetrievedUserNameAsPrincipal=false
#atn.1.IgnoreDuplicateMembership=
#atn.1.KeepAliveEnabled=
atn.1.Credential=wlevs
#atn.1.Name=
#atn.1.PropagateCauseForLoginException=
atn.1.ControlFlag=REQUIRED
#atn.1.ConnectTimeout=
atn.1.Host=localhost
atn.1.Port=389
#atn.1.SSLEnabled=
atn.1.Principal=cn=Administrator,dc=bea,dc=com
#atn.1.CacheEnabled=
#atn.1.CacheSize=
#atn.1.CacheTTL=
atn.1.FollowReferrals=false
#atn.1.BindAnonymouslyOnReferrals=
#atn.1.ResultsTimeLimit=
#atn.1.ParallelConnectDelay=
#atn.1.ConnectionRetryLimit=
atn.1.EnableGroupMembershipLookupHierarchyCaching=true
#atn.1.MaxGroupHierarchiesInCache=
#atn.1.GroupHierarchyCacheTTL=
#atn.5.mbean=weblogic.security.providers.authentication.OpenLDAPAuthenticatorMBean
#atn.5.UserNameAttribute=
#atn.5.UserBaseDN=
#atn.5.UserFromNameFilter=
#atn.5.GroupBaseDN=
#atn.5.GroupFromNameFilter=
#atn.5.StaticGroupObjectClass=
#atn.5.StaticMemberDNAttribute=
#atn.5.StaticGroupDNsfromMemberDNFilter=
#atn.5.UserObjectClass=
#atn.5.UserDynamicGroupDNAttribute=
#atn.5.UserSearchScope=
#atn.5.AllUsersFilter=
#atn.5.GroupSearchScope=
#atn.5.AllGroupsFilter=
#atn.5.StaticGroupNameAttribute=
#atn.5.DynamicGroupObjectClass=
#atn.5.DynamicGroupNameAttribute=
#atn.5.DynamicMemberURLAttribute=
#atn.5.GroupMembershipSearching=
#atn.5.MaxGroupMembershipSearchLevel=
#atn.5.UseRetrievedUserNameAsPrincipal=
#atn.5.IgnoreDuplicateMembership=
#atn.5.KeepAliveEnabled=
#atn.5.Credential=
#atn.5.PropagateCauseForLoginException=
#atn.5.ControlFlag=
#atn.5.Name=
#atn.5.ConnectTimeout=
#atn.5.Host=
#atn.5.Port=
#atn.5.SSLEnabled=
#atn.5.Principal=
#atn.5.CacheEnabled=
#atn.5.CacheSize=
#atn.5.CacheTTL=
#atn.5.FollowReferrals=
#atn.5.BindAnonymouslyOnReferrals=
#atn.5.ResultsTimeLimit=
#atn.5.ParallelConnectDelay=
#atn.5.ConnectionRetryLimit=
#atn.5.EnableGroupMembershipLookupHierarchyCaching=
#atn.5.MaxGroupHierarchiesInCache=
#atn.5.GroupHierarchyCacheTTL=
cm.1.mbean=weblogic.security.providers.credentials.DefaultCredentialMapperMBean
cm.1.Name=my-credential-mapper
cm.1.CredentialMappingDeploymentEnabled=true
#cm.3.mbean=weblogic.security.providers.credentials.FileBasedCredentialMapperMBean
#cm.3.FileStorePath=
#cm.3.FileStorePassword=
#cm.3.EncryptAlgorithm=
#cm.3.Name=
#cm.3.CredentialMappingDeploymentEnabled=
rm.1.mbean=weblogic.security.providers.xacml.authorization.XACMLRoleMapperMBean
rm.1.Name=my-role-mapper
rm.1.RoleDeploymentEnabled=true
atz.1.mbean=weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBean
atz.1.Name=my-authorizer
atz.1.PolicyDeploymentEnabled=true
adj.1.mbean=weblogic.security.providers.authorization.DefaultAdjudicatorMBean
adj.1.RequireUnanimousPermit=false
adj.1.Name=my-adjudicator

Customize the property file by updating the store.StoreProperties property to reflect your database driver information, connection URL, and username and password of the user that connects to the database. This is how the default property is set:

# Split for readability; in practice, the property should be on one line.
store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
ConnectionURL=jdbc:oracle:thin:@mymachine:1521:orcl, Username=wlevs,
Password=wlevs

Also update the property that specifies your LDAP server configuration.

Leave all the other properties to their default values.

Make a backup copy of the existing security.xml file, in case you need to revert:

prompt> copy security.xml security.xml_save

Create a new security configuration file (security.xml) by executing the following cssconfig command:

prompt> cssconfig -p myLDAPandDBMS.properties -c security.xml -i security-key.dat

In the preceding command, myLDAPandDBMS.properties is the property file you created in step 4, security.xml is the name of the new security configuration file, and security-key.dat is an existing file, generated by the Configuration Wizard, that contains the identity key.

See Section C.1, "The cssconfig Command-Line Utility" for additional information.

Change to the ORACLE_CEP_HOME/ocep_11.1/utils/security/sql directory:

prompt> cd d:\oracle_cep\ocep_11.1\utils\security\sql

This directory contains SQL scripts for creating the required security-related database tables and populating them with initial data. Because you are using the DBMS provider only for authorization, the relevant scripts for this procedure are:

atz_create.sql—Creates all tables required for authorization.

atz_drop.sql—Drops all authorization-related tables.

Run the following SQL script against the database you specified as the database store in step 4:

atz_create.sql

Configure your LDAP server by adding the default groups described in Section 10.1.3, "Users, Groups, and Roles" as well as the administrator user you specified when you created the domain. By default, this user is called wlevs.

Refer to your LDAP server documentation for details.

Optionally, configure password strength in your new security.xml file.

See Section 10.4, "Configuring Password Strength".

10.3.2 Configuring Both Authentication and Authorization Using the DBMS Provider

The following procedure describes how to configure the DBMS security provider for both authentication and authorization.

To configure both authentication and authorization using the DBMS provider:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Add the ORACLE_CEP_HOME\ocep_11.1\bin directory to your PATH environment variable, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep:

prompt> set PATH=d:\oracle_cep\ocep_11.1\bin;%PATH% (Windows)
prompt> PATH=/oracle_cep/ocep_11.1/bin:$PATH (UNIX)

Change to the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the main directory of your domain, such as d:\oracle_cep\user_projects\domains\mydomain, and servername refers to the name of your server:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\defaultserver\config

Make a backup copy of the existing security.xml file, in case you need to revert:

prompt> copy security.xml security.xml_save

Using your favorite text editor, create a file called myDBMS.properties and copy into it the entire contents of Example 10-2.

Example 10-2 DBMS Property File

# For attributes of type boolean or Boolean, value can be "true" or "false"
# and it's case insensitive.
# For attributes of type String[], values are comma separated; blanks before
# and after the comma are ignored. For example, if the property is defined as:
#   saml1.IntersiteTransferURIs=uri1, uri2, uri3
# the IntersiteTransferURIs attribute value is String[]{"uri1", "uri2", "uri3"}
# For attributes of type Properties, the value should be inputted as
# a set of key=value pairs separated by commas; blanks before and after the
# commas are also ignored. For example (split for readability; in practice, the property should be all on one line):
#  store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
    ConnectionURL=jdbc:oracle:thin:@united.bea.com:1521:xe, Username=user, Password=user
domain.mbean=com.bea.common.management.configuration.LegacyDomainInfoMBean
domain.DomainName=legacy-domain-name
domain.ServerName=legacy-server-name
domain.RootDirectory=legacy-rootdir
#domain.ProductionModeEnabled=
#domain.WebAppFilesCaseInsensitive=
domain.DomainCredential=changeit
jaxp.mbean=com.bea.common.management.configuration.JAXPFactoryServiceMBean
#jaxp.DocBuilderFactory=
#jaxp.SaxParserFactory=
#jaxp.SaxTransformFactory=
#jaxp.TransformFactory=
#ldapssl.mbean=com.bea.common.management.configuration.LDAPSSLSocketFactoryLookupServiceMBean
#ldapssl.Protocol=
#ldapssl.TrustManagerClassName=
namedsql.mbean=com.bea.common.management.configuration.NamedSQLConnectionLookupServiceMBean
store.mbean=com.bea.common.management.configuration.StoreServiceMBean
# Split for readability; the property should be fully on one line.
store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
    ConnectionURL=jdbc:oracle:thin:@mymachine:1521:orcl, Username=wlevs, Password=wlevs
#store.ConnectionProperties=
#store.NotificationProperties=
realm.mbean=weblogic.management.security.RealmMBean
realm.Name=my-realm
#realm.ValidateDDSecurityData=
#realm.CombinedRoleMappingEnabled=
#realm.EnableWebLogicPrincipalValidatorCache=
#realm.MaxWebLogicPrincipalsInCache=
#realm.DelegateMBeanAuthorization=
#realm.AuthMethods=
sqlconn.1.mbean=com.bea.common.management.configuration.NamedSQLConnectionMBean
sqlconn.1.Name=POOL1
sqlconn.1.JDBCDriverClassName=oracle.jdbc.driver.OracleDriver
sqlconn.1.ConnectionPoolCapacity=5
sqlconn.1.ConnectionPoolTimeout=10000
sqlconn.1.AutomaticFailoverEnabled=false
sqlconn.1.PrimaryRetryInterval=0
sqlconn.1.JDBCConnectionURL=jdbc\:oracle\:thin\:@fwang02\:1521\:orcl
sqlconn.1.JDBCConnectionProperties=
sqlconn.1.DatabaseUserLogin=wlevs
sqlconn.1.DatabaseUserPassword=wlevs
sqlconn.1.BackupJDBCConnectionURL=
sqlconn.1.BackupJDBCConnectionProperties=
sqlconn.1.BackupDatabaseUserLogin=
sqlconn.1.BackupDatabaseUserPassword=
adt.1.mbean=weblogic.security.providers.audit.DefaultAuditorMBean
adt.1.Severity=INFORMATION
#adt.1.InformationAuditSeverityEnabled=
#adt.1.WarningAuditSeverityEnabled=
#adt.1.ErrorAuditSeverityEnabled=
#adt.1.SuccessAuditSeverityEnabled=
#adt.1.FailureAuditSeverityEnabled=
#adt.1.OutputMedium=
#adt.1.RotationMinutes=
#adt.1.BeginMarker=
#adt.1.EndMarker=
#adt.1.FieldPrefix=
#adt.1.FieldSuffix=
adt.1.Name=my-auditor
#adt.1.ActiveContextHandlerEntries=
atn.1.mbean=weblogic.security.providers.authentication.SQLAuthenticatorMBean
atn.1.PasswordAlgorithm=SHA-1
atn.1.PasswordStyle=SALTEDHASHED
atn.1.PasswordStyleRetained=true
atn.1.SQLCreateUser=INSERT INTO USERS VALUES ( ? , ? , ? )
atn.1.SQLRemoveUser=DELETE FROM USERS WHERE U_NAME \= ?
atn.1.SQLRemoveGroupMemberships=DELETE FROM GROUPMEMBERS WHERE G_MEMBER \= ? ORG_NAME \= ?
atn.1.SQLSetUserDescription=UPDATE USERS SET U_DESCRIPTION  \= ? WHERE U_NAME \= ?
atn.1.SQLSetUserPassword=UPDATE USERS SET U_PASSWORD \= ? WHERE U_NAME \= ?
atn.1.SQLCreateGroup=INSERT INTO GROUPS VALUES ( ? , ? )
atn.1.SQLSetGroupDescription=UPDATE GROUPS SET G_DESCRIPTION \= ? WHERE G_NAME \=  ?
atn.1.SQLAddMemberToGroup=INSERT INTO GROUPMEMBERS VALUES( ?, ?)
atn.1.SQLRemoveMemberFromGroup=DELETE FROM GROUPMEMBERS WHERE G_NAME \= ? AND G_MEMBER \= ?
atn.1.SQLRemoveGroup=DELETE FROM GROUPS WHERE G_NAME \= ?
atn.1.SQLRemoveGroupMember=DELETE FROM GROUPMEMBERS WHERE G_NAME \= ?
atn.1.SQLListGroupMembers=SELECT G_MEMBER FROM GROUPMEMBERS WHERE G_NAME \= ? AND G_MEMBER LIKE ?
atn.1.DescriptionsSupported=true
atn.1.SQLGetUsersPassword=SELECT U_PASSWORD FROM USERS WHERE U_NAME \= ?
atn.1.SQLUserExists=SELECT U_NAME FROM USERS WHERE U_NAME \= ?
atn.1.SQLListMemberGroups=SELECT G_NAME FROM GROUPMEMBERS WHERE G_MEMBER \= ?
atn.1.SQLListUsers=SELECT U_NAME FROM USERS WHERE U_NAME LIKE ?
atn.1.SQLGetUserDescription=SELECT U_DESCRIPTION FROM USERS WHERE U_NAME \= ?
atn.1.SQLListGroups=SELECT G_NAME FROM GROUPS WHERE G_NAME LIKE ?
atn.1.SQLGroupExists=SELECT G_NAME FROM GROUPS WHERE G_NAME \= ?
atn.1.SQLIsMember=SELECT G_MEMBER FROM GROUPMEMBERS WHERE G_NAME \= ? AND G_MEMBER \= ?
atn.1.SQLGetGroupDescription=SELECT G_DESCRIPTION FROM GROUPS WHERE G_NAME \= ?
atn.1.GroupMembershipSearching=unlimited
atn.1.MaxGroupMembershipSearchLevel=0
atn.1.DataSourceName=POOL1
atn.1.PlaintextPasswordsEnabled=true
atn.1.ControlFlag=REQUIRED
atn.1.Name=my-authenticator
atn.1.EnableGroupMembershipLookupHierarchyCaching=false
atn.1.MaxGroupHierarchiesInCache=100
atn.1.GroupHierarchyCacheTTL=60
cm.1.mbean=weblogic.security.providers.credentials.DefaultCredentialMapperMBean
cm.1.Name=my-credential-mapper
cm.1.CredentialMappingDeploymentEnabled=true
rm.1.mbean=weblogic.security.providers.xacml.authorization.XACMLRoleMapperMBean
rm.1.Name=my-role-mapper
rm.1.RoleDeploymentEnabled=true
atz.1.mbean=weblogic.security.providers.xacml.authorization.XACMLAuthorizerMBean
atz.1.Name=my-authorizer
atz.1.PolicyDeploymentEnabled=true
adj.1.mbean=weblogic.security.providers.authorization.DefaultAdjudicatorMBean
adj.1.RequireUnanimousPermit=false
adj.1.Name=my-adjudicator

Customize the property file by updating the store.StoreProperties property to reflect your database driver information, connection URL, and username and password of the user that connects to the database. This is how the default property is set (in practice, this setting should be on one line):

store.StoreProperties=DriverName=oracle.jdbc.driver.OracleDriver,
ConnectionURL=jdbc:oracle:thin:@mymachine:1521:orcl, Username=wlevs,
Password=wlevs

Leave all the other properties to their default values.

Create a new security configuration file (security.xml) by executing the following cssconfig command:

prompt> cssconfig -p myDBMS.properties -c security.xml -i security-key.dat

In the preceding command, myDBMS.properties is the property file you created in step 4, security.xml is the name of the new security configuration file, and security-key.dat is an existing file, generated by the Configuration Wizard, that contains the identity key.

See Section C.1, "The cssconfig Command-Line Utility" for additional information.

Change to the ORACLE_CEP_HOME/ocep_11.1/utils/security/sql directory:

prompt> cd d:\oracle_cep\ocep_11.1\utils\security\sql

This directory contains SQL scripts for creating the required security-related database tables and populating them with initial data. These scripts are:

atn_create.sql—Creates all tables required for authentication.

atn_drop.sql—Drops all authentication-related tables.

atn_init.sql—Inserts default values into the authentication-related user and group tables. In particular, the script inserts a single default administrator user called wlevs, with password wlevs, into the user table and specifies that the user belongs to the wlevsAdministrators group. The script also inserts the default groups listed in Table 10-1 into the group table.

atz_create.sql—Creates all tables required for authorization.

atz_drop.sql—Drops all authorization-related tables.

If, when you created your domain using the Configuration Wizard, you specified an administrator user other than the default wlevs, edit the atn_init.sql file and add the INSERT INTO USERS and corresponding INSERT INTO GROUPMEMBERS statements accordingly.

For example, to add an administrative user juliet, with password shackell, add the following statements to the atn_init.sql file:

INSERT INTO USERS (U_NAME, U_PASSWORD, U_DESCRIPTION) VALUES ('juliet','shackell','default admin');
INSERT INTO GROUPMEMBERS (G_NAME, G_MEMBER) VALUES ('wlevsAdministrators','juliet');

Run the following SQL script files, in the order listed, against the database you specified as the database store in step 4:

atn_create.sql

atn_init.sql

atz_create.sql

Optionally, configure password strength in your new security.xml file.

See Section 10.4, "Configuring Password Strength".

10.4 Configuring Password Strength

Password strength is a measurement of the effectiveness of a password as an authentication credential. How the password strength is configured determines the type of password a user can specify, such as whether the password can contain the username, the minimum length of the password, the minimum number of numeric characters it can contain, and so on.

You configure the strength of the passwords used for Oracle CEP authentication by updating the security configuration file (security.xml), located in the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to your domain directory, such as d:/oracle_cep/user_projects/domains/mydomain, and servername refers to your server, such as defaultserver.

The password strength configuration is contained in the <password-validator> element.

Example 10-3 shows a snippet from the security.xml file with the default values after creating a new domain using the Configuration Wizard.

Example 10-3 Default password-validator Element in the security.xml File

<sec:password-validator
   xmlns:pas="http://www.bea.com/ns/weblogic/90/security/providers/passwordvalidator"
   xsi:type="pas:system-password-validatorType">
   <sec:name>my-password-validator</sec:name>
   <pas:reject-equal-or-contain-username>true</pas:reject-equal-or-contain-username>
   <pas:reject-equal-or-contain-reverse-username>
      false
   </pas:reject-equal-or-contain-reverse-username>
   <pas:max-password-length>50</pas:max-password-length>
   <pas:min-password-length>6</pas:min-password-length>
   <pas:max-instances-of-any-character>0</pas:max-instances-of-any-character>
   <pas:max-consecutive-characters>0</pas:max-consecutive-characters>
   <pas:min-alphabetic-characters>1</pas:min-alphabetic-characters>
   <pas:min-numeric-characters>1</pas:min-numeric-characters>
   <pas:min-lowercase-characters>1</pas:min-lowercase-characters>
   <pas:min-uppercase-characters>1</pas:min-uppercase-characters>
   <pas:min-non-alphanumeric-characters>0</pas:min-non-alphanumeric-characters>
</sec:password-validator>

Table 10-2 describes all the child elements of <password-validator> you can configure.

If you manually update the security.xml file, you must restart the Oracle CEP server instance for the changes to take effect.

Table 10-2 Child Elements of <password-validator>

Child Element
Description
Default Value

reject-equal-or-contain-name

When set to true, Oracle CEP rejects a password if it is the same as, or contains, the username.

When set to false, Oracle CEP does not reject a password for this reason.

true

reject-equal-or-contain-reverse-username

When set to true, Oracle CEP rejects a password if it is the same as, or contains, the reversed username.

When set to false, Oracle CEP does not reject a password for this reason.

false

max-password-length

Specifies the maximum length of a password.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

50

min-password-length

Specifies the minimum length of a password.

Valid values for this element are integers greater than or equal to 0.

6

max-instances-of-any-character

Specifies the maximum number of times the same character can appear in the password. For example, if this element is set to 2, then the password bubble is invalid.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

0

max-consecutive-characters

Specifies the maximum number of repeating consecutive characters that are allowed in the password. For example, if this element is set to 2, then the password bubbble is invalid.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

0

min-alphabetic-characters

Specifies the minimum number of alphabetic characters that a password must contain.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

1

min-numeric-characters

Specifies the minimum number of numeric characters that a password must contain.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

1

min-lowercase-characters

Specifies the minimum number of lowercase characters that a password must contain.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

0

min-uppercase-characters

Specifies the minimum number of uppercase characters that a password must contain.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

0

min-non-alphanumeric-characters

Specifies the minimum number of non-alphanumeric characters that a password must contain. Non-alphanumeric characters include $, #, @, &, ! and so on.

A value of 0 means there is no restriction.

Valid values for this element are integers greater than or equal to 0.

0

10.5 Configuring SSL to Secure Network Traffic

Oracle CEP uses one-way Secure Sockets Layer (SSL) to secure the network traffic between:

A browser running the Oracle CEP Visualizer and the Oracle CEP instance that hosts the data-services application that the Oracle CEP Visualizer uses.

The wlevs.Admin command-line utility and an Oracle CEP instance.

See Section A.4, "Running wlevs.Admin Utility in SSL Mode".

The member servers of a multi-server domain.

You configure SSL in the server's config.xml file. When you create an Oracle CEP server using the Configuration Wizard, the server's config.xml automatically includes a default SSL configuration.

This section describes:

Section 10.5.1, "How to Configure SSL Manually"

Section 10.5.2, "How to Create a Key-Store Manually"

Section 10.5.3, "How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer"

For more information, see Section 10.1.4, "SSL".

10.5.1 How to Configure SSL Manually

This section describes how to configure SSL in Oracle CEP.

To configure SSL manually:

Create a domain using the Configuration Wizard.

See:

Section 3.1, "Creating an Oracle CEP Standalone-Server Domain"

Section 6.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle Coherence"

Section 7.1, "Creating an Oracle CEP Multi-Server Domain Using Oracle CEP Native Clustering"

Using your favorite XML editor, open the Oracle CEP server config.xml file.

By default, the Configuration Wizard creates the config.xml file in the ORACLE_CEP_HOME/user_projects/domains/DOMAIN_DIR/servername/config directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep), DOMAIN_DIR refers to the domain directory (such as my_domain), and servername refers to the server instance directory (such as server1).

For more information, see Section 1.3.1, "Oracle CEP Server Configuration Files".

Configure the ssl element.

Example 10-4 shows the default ssl element the Configuration Wizard creates.

Example 10-4 Default ssl Element

<ssl>
    <name>sslConfig</name>
    <key-store>./ssl/evsidentity.jks</key-store>
    <key-store-pass>
        <password>{Salted-3DES}sdlUX8aEDeNpQ4VhsaCnFA==</password>
    </key-store-pass>
    <key-store-alias>evsidentity</key-store-alias>
    <key-manager-algorithm>SunX509</key-manager-algorithm>
    <ssl-protocol>TLS</ssl-protocol>
    <enforce-fips>false</enforce-fips>
    <need-client-auth>false</need-client-auth>
</ssl>

The key-store element points to a certificate file. The Configuration Wizard creates a default certificate file, called evsidentity.jks, in the DOMAIN_DIR/servername/ssl directory; its password is the same as that entered when creating a server with the Configuration Wizard.

By default, the password for the certificate private key will be the same as the password for the identity keystore.

Note:

The Oracle CEP Server will not start unless the password for certificate private key is the same as the password for the identity keystore.

The evsidentity.jks contains a self-signed certificate. Optionally, create your own certificate file and either replace the evsidentity.jks file, or update the key-store element in the config.xml file.

Note:

In a production environment, the system administrator should replace the default self-signed certificate with a CA signed certificate.

For more information on creating a key-store yourself, see Section 10.5.2, "How to Create a Key-Store Manually".

For more information on the enforce-fips element, see Section 10.6, "Configuring FIPS for Oracle CEP Server".

Configure a netio element for SSL.

Example 10-5 shows the default netio element the Configuration Wizard creates.

Example 10-5 Default netio Element

<netio>
    <name>sslNetIo</name>
    <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
    <port>9003</port>
</netio>

The ssl-config-bean-name must match the ssl element name child element (see step 3).

Optionally, change this port to a port number that suits your needs.

The default secure port is 9003 by default.

Configure the jetty element to add a secure-network-io-name child element.

Example 10-6 shows the default jetty element the Configuration Wizard creates.

Example 10-6 Default jetty Element

<jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
    <secure-network-io-name>sslNetIo</secure-network-io-name>
</jetty>

The secure-network-io-name must match the SSL netio element name child element (see step 4).

Save and close the config.xml file.

Restart the Oracle CEP server (if running).

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

10.5.2 How to Create a Key-Store Manually

By default, the Configuration Wizard creates a default key-store certificate file, called evsidentity.jks, in the DOMAIN_DIR/servername/ssl directory; its password is the same as that entered when creating a server with the Configuration Wizard. Optionally, you can manually create your own key-store.

For more information, see:

Section 3.1.1, "Creating an Oracle CEP Standalone-Server Domain Using the Configuration Wizard in Graphical Mode"

Section 10.5.1, "How to Configure SSL Manually"

To create a key-store manually:

Use the JDK keytool command to generate a key-store:

keytool -genkey -alias evsidentity -keyalg RSA -validity 10958 -keystore evsidentity.jks -keysize 1024

Enter the key-store password, as prompted:

Enter keystore password:

Enter the key-store attributes, as prompted:

What is your first and last name?
  [Unknown]:  CEP
What is the name of your organizational unit?
  [Unknown]:  SOA
What is the name of your organization?
  [Unknown]:  ORACLE
What is the name of your City or Locality?
  [Unknown]:  SF
What is the name of your State or Province?
  [Unknown]:  CA
What is the two-letter country code for this unit?
  [Unknown]:  US
Is CN=CEP, OU=SOA, O=ORACLE, L=SF, ST=CA, C=US correct?
  [no]:  y

When prompted for a key password, do not enter a password; just press RETURN:

Enter key password for <evsidentity>
        (RETURN if same as keystore password):

Note:

The Oracle CEP Server will not start unless the password for certificate private key is the same as the password for the identity keystore.

Using your favorite XML editor, open the Oracle CEP server config.xml file.

By default, the Configuration Wizard creates the config.xml file in the ORACLE_CEP_HOME/user_projects/domains/DOMAIN_DIR/servername/config directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep), DOMAIN_DIR refers to the domain directory (such as my_domain), and servername refers to the server instance directory (such as server1).

For more information, see Section 1.3.1, "Oracle CEP Server Configuration Files".

Configure the ssl element.

Example 10-4 shows the default ssl element the Configuration Wizard creates.

Example 10-7 Default ssl Element

<ssl>
    <name>sslConfig</name>
    <key-store>KEYSTORE_PATH</key-store>
    <key-store-pass>
        <password>PASSWORD</password>
    </key-store-pass>
    <key-store-alias>KEYSTORE_ALIAS</key-store-alias>
    <key-manager-algorithm>SunX509</key-manager-algorithm>
    <ssl-protocol>TLS</ssl-protocol>
    <enforce-fips>false</enforce-fips>
    <need-client-auth>false</need-client-auth>
</ssl>

Where:

KEYSTORE_PATH is the file path to the key-store file (the file name is from the -keystore argument to the keytool command).

PASSWORD is the cleartext keystore password.

KEYSTORE_ALIAS is the keystore alias (from the -alias argument to the keytool command).

Save and close the config.xml file.

Encrypt the cleartext password in the key-store-pass element password child element of the config.xml file by using the encryptMSAConfig utility.

See Section C.2, "The encryptMSAConfig Command-Line Utility."

10.5.3 How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer

The following procedure shows how to configure one-way SSL between the server that hosts the Oracle CEP Visualizer data-services application and another server in a multi-server domain.

In the procedure, it is assumed that the server that hosts the Oracle CEP Visualizer data-services application is called server1 and the other server is called server2, and that both are located in the /oracle_cep/user_projects/domains/mydomain directory. Repeat this procedure for other servers in the domain, if required.

For information on securing the messages sent between servers in a multi=-server domain, see:

Oracle Coherence: Section 6.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

Oracle CEP Native Clustering: Section 7.3, "Securing the Messages Sent Between Servers in a Multi-Server Domain"

For information on starting Oracle CEP Visualizer in a multi-server domain, see "How to Start Oracle CEP Visualizer in a Multi-Server Domain" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

To configure SSL in a multi-server domain for use by Oracle CEP Visualizer:

Ensure that SSL is configured for the two servers in the domain.

If you used the Configuration Wizard to create the servers, then SSL is configured by default.

See Section 10.5.1, "How to Configure SSL Manually" for details, as well as information on how to change the default configuration.

Start server2.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Change to the ssl sub-directory of the server1 directory:

prompt> cd /oracle_cep/user_projects/domains/mydomain/server1/ssl

Generate a trust keystore for server1 that includes the certificate of server2 by specifying the following command (split for readability; in practice, the command should be on one line):

prompt> java -classpath ORACLE_CEP_HOME\ocep_11.1\common\lib\evspath.jar;ORACLE_CEP_HOME\ocep_11.1\utils\security\wlevsgrabcert.jar
com.bea.wlevs.security.util.GrabCert host:secureport
-alias=alias truststorepath

where

ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep)

host refers to the computer on which server2 is running.

secureport refers to the SSL network i/o port configured for server2. Default value is 9003.

For more information, see Example 10-5 in Section 10.5.1, "How to Configure SSL Manually."

alias refers to the alias for the certificate in the trust keystore. Default value is the hostname.

truststorepath refers to the full pathname of the generated trust keystore file; default is evstrust.jks

For example (split for readability; in practice, the command should be on one line):

prompt> java -classpath C:\OracleCEP\ocep_11.1\common\lib\evspath.jar;C:\OracleCEP\ocep_11.1\utils\security\wlevsgrabcert.jar
com.bea.wlevs.security.util.GrabCert server2:9003
-alias=server2 evstrust.jks

For more information, see Section C.3, "The GrabCert Command-Line Utility".

When prompted, enter the Oracle CEP administrator password:

Please enter the Password for the supplied user : wlevs

When prompted, select the certificate sent by server2:

Created TrustStore evstrust.jks
Opening connection to server2:9003...
Starting SSL handshake...

No certificates in evstrust.jks are trusted by server2:9003

Server sent 1 certificate(s):

 1 Subject CN=localhost, OU=Event Server, O=BEA, L=San Jose, ST=California, C=US
   Issuer  CN=localhost, OU=Event Server, O=BEA, L=San Jose, ST=California, C=US
   sha1    00 07 c0 f4 10 48 9a f9 07 82 4f b6 9c 7f 7c d0 37 57 90 7d
   md5     a4 d4 ff d2 43 69 95 ca c3 43 e6 f6 b8 08 df b7

Enter certificate to add to trusted keystore evstrust.jks or 'q' to quit: [1]

Update the config.xml file of server1, adding trust keystore information to the ssl element and adding a use-secure-connections element, as shown in bold in the following snippet:

<ssl>
    <name>sslConfig</name>
    <key-store>./ssl/evsidentity.jks</key-store>
    <key-store-pass>
        <password>{Salted-3DES}s4YUEvH4Wl2DAjb45iJnrw==</password>
    </key-store-pass>
    <key-store-alias>evsidentity</key-store-alias>
    <key-manager-algorithm>SunX509</key-manager-algorithm>
    <ssl-protocol>TLS</ssl-protocol>
    <trust-store>./ssl/evstrust.jks</trust-store>
    <trust-store-pass>
        <password>wlevs</password>
    </trust-store-pass>
    <trust-store-alias>evstrust</trust-store-alias>
    <trust-store-type>JKS</trust-store-type>
    <trust-manager-algorithm>SunX509</trust-manager-algorithm>
    <enforce-fips>false</enforce-fips>
    <need-client-auth>false</need-client-auth>
</ssl>
<use-secure-connections>
    <value>true</value>
</use-secure-connections>

The config file is located in the config subdirectory of the main server directory, such as /oracle_cep/user_projects/domains/mydomain/server1/config/.

Encrypt the cleartext password in the trust-store-pass element password child element of the config.xml file by using the encryptMSAConfig utility.

See Section C.2, "The encryptMSAConfig Command-Line Utility."

Start server1.

10.6 Configuring FIPS for Oracle CEP Server

You can configure Oracle CEP server to use a Federal Information Processing Standards (FIPS)-certified pseudo-random number generator.

For more information, see Section 10.1.5, "FIPS".

To configure FIPS for Oracle CEP server:

Configure Java SE security.

See Section 10.2, "Configuring Java SE Security for Oracle CEP Server".

Configure SSL.

See Section 10.5, "Configuring SSL to Secure Network Traffic".

Copy com.bea.core.jsafejcefips_version.jar:

From: ORACLE_CEP_HOME/ocep_11.1/utils/security

To: JRE_HOME/jre/lib/ext

Where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP and JRE_HOME refers to the directory that contains your JRockit JRE:

If using the JRockit JDK installed with Oracle JRockit Real Time, copy the com.bea.core.jsafejcefips_version.jar into the JROCKIT_HOME/JROCKIT_RT_HOME/jre/lib/ext directory.

Where JROCKIT_HOME is the directory in which you installed Oracle JRockit Real Time, such as d:\jrockit.

If using the JRockit JDK installed with Oracle CEP, copy the com.bea.core.jsafejcefips_version.jar into the ORACLE_CEP_HOME/JROCKIT_HOME/jre/lib/ext directory.

Where ORACLE_CEP_HOME is the directory in which you installed Oracle CEP server such as d:\oracle_cep.

Stop the Oracle CEP server, if it is currently running.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Edit the JRE_HOME/jre/lib/security/java.security file to add com.bea.core.jsafejcefips_2.0.0.0.jar as a JCE provider as Example 10-8 shows.

Example 10-8 Editing java.security to Add jsafejcefips JAR as a JCE Provider

security.provider.N=com.rsa.jsafe.provider.JsafeJCE

Where N is a unique integer that specifies the order in which Java accesses security providers.

To make the JsafeJCE provider the default provider, set N to 1. In this case, change the value of N for any other providers in the java.security file so that each provider has a unique number as Example 10-9 shows.

Example 10-9 Making JsafeJCE the Default Provider

security.provider.1=com.rsa.jsafe.provider.JsafeJCE
security.provider.2=sun.security.provider.Sun

Edit the server.config file ssl element as Example 10-10 shows to add the following child elements:

enforce-fips: set this option to true.

secure-random-algorithm: set this option to FIPS186PRNG

secure-random-provider: set this option to JsafeJCE.

Example 10-10 Editing server.config to Enable Fips

<ssl>
    <name>sslConfig</name>
    <key-store>./ssl/evsidentity.jks</key-store>
    <key-store-pass>
        <password>s4YUEvH4Wl2DAjb45iJnrw==</password>
    </key-store-pass>
    <key-store-alias>evsidentity</key-store-alias>
    <key-manager-algorithm>SunX509</key-manager-algorithm>
    <ssl-protocol>TLS</ssl-protocol>
    <enforce-fips>true</enforce-fips>
    <need-client-auth>false</need-client-auth>
    <secure-random-algorithm>FIPS186PRNG</secure-random-algorithm>
    <secure-random-provider>JsafeJCE</secure-random-provider>
</ssl>

Restart the Oracle CEP server for the changes to take effect.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

10.7 Configuring HTTPS-Only Connections for Oracle CEP Server

This section describes how to lock down the server so that only HTTPS connections are allowed.

To configure HTTPS-Only connections for Oracle CEP server:

Ensure that SSL is configured for the server.

See Section 10.5, "Configuring SSL to Secure Network Traffic" for details.

Remove the HTTP port configuration from the server's DOMAIN_DIR/servername/config/config.xml file, leaving only the configuration for the HTTPS port.

Example 10-11 shows a config.xml snippet with a standard configuration in which both an HTTP and HTTPS port have been configured. The HTTP port is 9002 and the HTTPS port is 9003. Clients can access the Jetty server using both ports.

Example 10-11 Typical config.xml File With Both HTTP and HTTPS Access

<netio>
   <name>NetIO</name>
   <port>9002</port>
</netio>
<netio>
   <name>sslNetIo</name>
   <port>9003</port>
   <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
</netio>
<jetty>
   <name>JettyServer</name>
   <network-io-name>NetIO</network-io-name>
   <secure-network-io-name>sslNetIo</secure-network-io-name>
   ...
</jetty>
<ssl>
   <name>sslConfig</name>
   <key-store>./ssl/evsidentity.jks</key-store>
   ...
</ssl>

Example 10-12 shows the same config.xml file with HTTP access removed. Clients can now access the Jetty server only using the HTTPS port.

Example 10-12 Typical config.xml File With HTTP Access Removed

<netio>
   <name>sslNetIo</name>
   <port>9003</port>
   <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
</netio>
<jetty>
   <name>JettyServer</name>
   <secure-network-io-name>sslNetIo</secure-network-io-name>
   ...
</jetty>
<ssl>
   <name>sslConfig</name>
   <key-store>./ssl/evsidentity.jks</key-store>
   ...
</ssl>

If you have a multi-server domain, be sure that SSL has been configured between the member servers.

See Section 10.5.3, "How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer" for details.

10.8 Configuring Security for Oracle CEP Server Services

After you complete basic security tasks such as configuring Java SE security, a security service provider, and SSL, you can configure security details specific to the various services that Oracle CEP server provides.

This section describes:

Section 10.8.1, "Configuring Jetty Security"

Section 10.8.2, "Configuring JMX Security"

Section 10.8.3, "Configuring JDBC Security"

Section 10.8.4, "Configuring HTTP Publish-Subscribe Server Channel Security"

10.8.1 Configuring Jetty Security

Oracle CEP supports Jetty (see http://www.mortbay.org/) as Java Web server to deploy HTTP servlets and static resources.

The following security tasks affect Jetty configuration:

Section 10.2, "Configuring Java SE Security for Oracle CEP Server"

Section 10.5, "Configuring SSL to Secure Network Traffic"

For more information on Jetty, see Chapter 11, "Configuring Jetty for Oracle CEP".

10.8.2 Configuring JMX Security

Clients that access the Oracle CEP server using JMX are subject to Oracle CEP role-based authentication.

For more information, see:

Section 10.1.3, "Users, Groups, and Roles"

"Managing Groups" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

"Managing Users" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

For more information about JMX, see Chapter 12, "Configuring JMX for Oracle CEP".

10.8.3 Configuring JDBC Security

If you update a data-source with a new password using the Configuration Wizard, the Configuration Wizard performs password encryption for you.

If you update the config.xml file manually by adding or modifying a data-source element, you enter the password in plain text and then encrypt the password using the encryption utility encryptMSAConfig.

Example 10-13 shows a config.xml file data-source element with a new plain text password secret specified in the properties element with name password.

Example 10-13 Oracle CEP config.xml File data-source Element After Encryption

<data-source>
   <name>epcisDS</name>
   <driver-params>
      <url>jdbc:sqlserver://localhost:1433;databaseName=myDB;SelectMethod=cursor</url>
      <driver-name>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-name>
      <properties>
         <element>
            <name>user</name>
            <value>juliet</value>
         </element>
         <element>
            <name>password</name>
            <value>secret</value>
         </element>
      </properties>
   </driver-params>
</data-source>
<transaction-manager>
   <name>TM</name>
   <rmi-service-name>RMI</rmi-service-name>
</transaction-manager>

Example 10-14 shows the config.xml file data-source element after encryption. Note the plain text password has been encrypted.

Example 10-14 Oracle CEP config.xml File data-source Element After Encryption

<data-source>
   <name>epcisDS</name>
   <driver-params>
      <url>jdbc:sqlserver://localhost:1433;databaseName=myDB;SelectMethod=cursor</url>
      <driver-name>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-name>
      <properties>
         <element>
            <name>user</name>
            <value>juliet</value>
         </element>
         <element>
            <name>password</name>
            <value>{Salted-3DES}hVgC5iZ3nZA=</value>
         </element>
      </properties>
   </driver-params>
</data-source>
<transaction-manager>
   <name>TM</name>
   <rmi-service-name>RMI</rmi-service-name>
</transaction-manager>

For more information, see:

Section 10.1.8, "Specifying User Credentials When Using the Command-Line Utilities"

Section C.2, "The encryptMSAConfig Command-Line Utility"

For more information about JDBC, see Chapter 13, "Configuring JDBC for Oracle CEP"

10.8.4 Configuring HTTP Publish-Subscribe Server Channel Security

After you configure at least one HTTP publish-subscribe server channel, you can use role-based authentication to control access to individual HTTP publish-subscribe server channels using the Oracle CEP Visualizer.

For more information, see:

Section 10.1.3, "Users, Groups, and Roles"

Chapter 14, "Configuring HTTP Publish-Subscribe for Oracle CEP"

"Configuring Security for the HTTP Publish-Subscribe Channels" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

10.9 Configuring Cross-Domain Security for Oracle CEP Visualizer

Oracle CEP Visualizer provides an Adobe Flash-based user interface with which you can create and configure event processing networks. In order to provide the most flexible default performance for Oracle CEP Visualizer, the software is installed with a configured trust level that allows access to Visualizer data from any domain. If you find that this trust level is inappropriate for your deployment, you can edit the application's Flash cross-domain policy file in order to restrict access.

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

You'll find a more thorough description on editing cross-domain policy at the Adobe web site. For more information on using Adobe cross-domain policy files, see the Adobe security web site.

Updating cross-domain security involves opening the Oracle CEP Visualizer JAR file. Here are the high-level steps:

Locate the Oracle CEP Visualizer JAR file. By default in an Oracle CEP installation, you'll find it at:

CEP_HOME/modules/com.bea.wlevs.visualizer.jmxhttpadapter_version.jar

For example, on a Windows installation, that might be:

C:\Oracle\Middleware\ocep_11.1\modules\com.bea.wlevs.visualizer.jmxhttpadapter_11.1.1.6_0.jar

Expand the JAR file to locate crossdomain.war.

Expand crossdomain.war to locate crossdomain.xml.

Edit crossdomain.xml to reflect your cross-domain security needs.

Repackage crossdomain.war and the Oracle CEP Visualizer JAR file.

10.10 Configuring the Oracle CEP Security Auditor

Oracle CEP provides a security auditor that logs security-related activity.

By default, the security auditor logs to DOMAIN_DIR/servername/legacy-rootdir/servers/legacy-server-name/logs/DefaultAuditRecorder.log file, where DOMAIN_DIR refers to the main directory of your domain, such as d:\oracle_cep\user_projects\domains\mydomain, and servername refers to the name of your server.

By default, the Oracle CEP security auditor will only log security errors or failures. This helps keep the security auditor log file at a manageable size.

Optionally, you can configure the level at which the Oracle CEP security auditor logs information.

For more information, see "Configuring the WebLogic Auditing Provider" in the Oracle Fusion Middleware Securing Oracle WebLogic Server.

To configure security auditor logging:

Change to the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the main directory of your domain, such as d:\oracle_cep\user_projects\domains\mydomain, and servername refers to the name of your server:

prompt> cd d:\oracle_cep\user_projects\domains\mydomain\defaultserver\config

Using your favorite text editor, edit the security.xml file.

Locate the sec:auditor element.

Example 10-15 shows the default sec:auditor element configuration:

Example 10-15 Default sec:auditor Element

<sec:auditor xsi:type="wls:default-auditorType">
    <sec:name>my-auditor</sec:name>
    <wls:severity>CUSTOM</wls:severity>
    <wls:rotation-minutes>720</wls:rotation-minutes>
    <wls:error-audit-severity-enabled>true</wls:error-audit-severity-enabled>
    <wls:failure-audit-severity-enabled>true</wls:failure-audit-severity-enabled>
</sec:auditor>

Modify the sec:auditor element as required:

wls:rotation-minutes: Specifies how many minutes to wait before creating a new DefaultAuditRecorder.log file. At the specified time, the audit file is closed and a new one is created. A backup file named DefaultAuditRecorder.YYYYMMDDHHMM.log (for example, DefaultAuditRecorder.200405130110.log) is created in the same directory.

wls:severity: Specifies the severity level appropriate for your Oracle CEP server as Table 10-3 lists. The Oracle CEP security auditor audits security events of the specified severity, as well as all events with a higher numeric severity rank. For example, if you set the severity level to ERROR, the Oracle CEP security auditor audits security events of severity level ERROR, SUCCESS, and FAILURE.

Table 10-3 Oracle CEP Security Auditor Severity Levels

Event Severity
Rank

INFORMATION

1

WARNING

2

ERROR

3

SUCCESS

4

FAILURE

5

You can also set the wls:severity level to CUSTOM, and then enable (set to true) or disable (set to false) the specific severity levels you want to audit using one or more of the following child elements as Example 10-15 shows:

wls:information-audit-severity-enabled: If the severity value is set to CUSTOM, setting this child element to true causes the Oracle CEP security auditor to generate audit records for events with a severity level of INFORMATION.

wls:warning-audit-severity-enabled: If the severity value is set to CUSTOM, setting this child element to true causes the Oracle CEP security auditor to generate audit records for events with a severity level of WARNING.

wls:error-audit-severity-enabled: If the severity value is set to CUSTOM, setting this child elemnent to true causes the Oracle CEP security auditor to generate audit records for events with a severity level of ERROR.

wls:success-audit-severity-enabled: If the severity value is set to CUSTOM, setting this child elemnent to true causes the Oracle CEP security auditor to generate audit records for events with a severity level of SUCCESS.

wls:failure-audit-severity-enabled: If the severity value is set to CUSTOM, setting this child elemnent to true causes the Oracle CEP security auditor to generate audit records for events with a severity level of FAILURE.

Save and close the security.xml file.

Restart the Oracle CEP server for the changes to take effect.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

10.11 Disabling Security

You can disable security entirely on the Oracle CEP server. While this configuration may be appropriate for development environments, Oracle does not recommend disabling security in a production environment.

To temporarily disable security, you can run the startwlevs.cmd or startwlevs.sh script with the -disablesecurity argument on the command line. For example:

startwlevs.cmd -disablesecurity

Note:

In some sample domains, the startwlevs.cmd and startwlevs.sh scripts already include a -disablesecurity argument. Executing such a script with -disablesecurity on the command line will fail with an Illegal argument error.

11 Configuring Jetty for Oracle CEP

This chapter describes how to configure Jetty for use with Oracle Complex Event Processing (Oracle CEP), including configuring network I/O, and work managers, as well as configuring a Jetty server instance.

Section 11.1, "Overview of Jetty Support in Oracle Complex Event Processing"

Section 11.2, "Configuring a Jetty Server Instance"

Section 11.3, "Example Jetty Configuration"

11.1 Overview of Jetty Support in Oracle Complex Event Processing

Oracle CEP supports Jetty (see http://www.mortbay.org/) as Java Web server to deploy HTTP servlets and static resources.

Oracle CEP support for Jetty is based on Version 1.2 the OSGi HTTP Service. This API provides ability to dynamically register and unregister http://java.sun.com/products/servlet/docs.html objects with the run time and static resources. This specification requires at minimum version 2.1 of the Java Servlet API.

Oracle CEP supports the following features for Jetty:

Section 11.1.1, "Servlets"

Section 11.1.2, "Network I/O Integration"

Section 11.1.3, "Thread Pool Integration"

Section 11.1.4, "Jetty Work Managers"

For details about configuring Jetty, see Section 11.2, "Configuring a Jetty Server Instance."

11.1.1 Servlets

In addition to supporting typical (synchronous) Java servlets, Oracle CEP supports asynchronous servlets. An asynchronous servlet receives a request, gets a thread and performs some work, and finally releases the thread while waiting for those actions to complete before re-acquiring another thread and sending a response.

11.1.2 Network I/O Integration

Oracle CEP uses network I/O (NetIO) to configure the port and listen address of Jetty services.

Note:

Jetty has a built-in capability for multiplexed network I/O. However, it does not support multiple protocols on the same port.

11.1.3 Thread Pool Integration

Oracle CEP Jetty services use the Oracle CEP Work Manager to provide for scalable thread pooling. See Section 11.3, "Example Jetty Configuration."

Note:

Jetty provides its own thread pooling capability. However, Oracle recommends using the Oracle CEP self-tuning thread pool to minimize footprint and configuration complexity.

11.1.4 Jetty Work Managers

Oracle CEP allows you to configure how your application prioritizes the execution of its work. Based on rules you define and by monitoring actual run time performance, you can optimize the performance of your application and maintain service level agreements. You define the rules and constraints for your application by defining a work manager.

This section describes:

Section 11.1.4.1, "Understanding How Oracle CEP Uses Thread Pools"

Section 11.1.4.2, "Understanding Work Manager Configuration"

For more information, see Section 11.2.3, "work-manager Configuration Object."

11.1.4.1 Understanding How Oracle CEP Uses Thread Pools

Oracle CEP uses is a single thread pool, in which all types of work are executed. Oracle CEP prioritizes work based on rules you define, and run-time metrics, including the actual time it takes to execute a request and the rate at which requests are entering and leaving the pool.

The common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count. For example, if historical throughput statistics indicate that a higher thread count increased throughput, Oracle CEP increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, Oracle CEP decreases the thread count.

11.1.4.2 Understanding Work Manager Configuration

Oracle CEP prioritizes work and allocates threads based on an execution model that takes into account defined parameters and run-time performance and throughput.

You can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components. For example, you can associate one set of scheduling guidelines for one application, and another set of guidelines for other applications. At run time, Oracle CEP uses these guidelines to assign pending work and enqueued requests to execution threads.

To manage work in your applications, you define one or more of the following work manager components:

fairshare—Specifies the average thread-use time required to process requests.

For example, assume that Oracle CEP is running two modules. The Work Manager for ModuleA specifies a fairshare of 80 and the Work Manager for ModuleB specifies a fairshare of 20.

During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, Oracle CEP allocates 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.

Note:

The value of a fair share request class is specified as a relative value, not a percentage. Therefore, in the above example, if the request classes were defined as 400 and 100, they would still have the same relative values.

max-threads-constraint—This constraint limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined.

A max-threads-constraint can be defined in terms of a the availability of resource that requests depend upon, such as a connection pool.

A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the Oracle CEP does not schedule requests of this type until the number of concurrent executions falls below the limit. The Oracle CEP then schedules work based on the fair share or response time goal.

min-threads-constraint—This constraint guarantees a number of threads the server will allocate to affected requests to avoid deadlocks. The default is zero. A min-threads-constraint value of one is useful, for example, for a replication update request, which is called synchronously from a peer.

A min-threads-constraint might not necessarily increase a fair share. This type of constraint has an effect primarily when the Oracle CEP instance is close to a deadlock condition. In that case, it the constraint causes Oracle CEP to schedule a request even if requests in the service class have gotten more than their fair share recently.

11.2 Configuring a Jetty Server Instance

You use the following configuration objects to configure an instance of the Jetty HTTP server in the config.xml file that describes your Oracle CEP domain:

jetty: See Section 11.2.1, "jetty Configuration Object" for details.

netio: See Section 11.2.2, "netio Configuration Object" for details.

work-manager: See Section 11.2.3, "work-manager Configuration Object" for details.

jetty-web-app: See Section 11.2.4, "jetty-web-app Configuration Object" for details

For information on security configuration tasks that affect Jetty, see Section 10.8.1, "Configuring Jetty Security".

For more information, see:

Section 11.2.5, "Developing Servlets for Jetty"

Section 11.2.6, "Web Application Deployment"

Section 11.3, "Example Jetty Configuration"

11.2.1 jetty Configuration Object

Use the parameters described in the following table to define a jetty configuration object in your config.xml file.

Table 11-1 Configuration Parameters for the jetty Element

Parameter
Type
Description

network-io-name

String

The name of the NetIO service used. The NetIO service defines the port the server listens on.

See Section 11.2.2, "netio Configuration Object" for details.

work-manager-name

String

The name of the Work Manager that should be used for thread pooling. If not specified, the default work manager is used.

See Section 11.2.3, "work-manager Configuration Object."

scratch-directory

String

The name of a directory where temporary files required for web applications, JSPs, and other types of Web artifacts are kept.

debug-enabled

boolean

Enable debugging in the Jetty code using the OSGi Log Service.

name

String

The name of the jetty server instance.

11.2.2 netio Configuration Object

Use the parameters described in the following table to define a netio configuration object in your config.xml file.

Table 11-2 Configuration Parameters for the netio Element

Parameter
Type
Description

name

String

The name of this configuration object.

port

int

The listening port number.

listen-address

String

The address on which an instance of netio service listens for incoming connections.

It may be set to a numeric IP address in the a.b.c.d format, or to a host name.

If not set, the service listens on all network interfaces.

The value of this parameter cannot be validated until the service has started.

11.2.3 work-manager Configuration Object

Use the parameters described in the following table to define a work-manager configuration object in your config.xml file.

Table 11-3 Configuration Parameters for the work-manager Element

Parameter
Type
Description

min-threads-constraint

Integer

The minimum threads this work manager uses.

fairshare

Integer

The fairshare value this work manager uses.

max-threads-constraint

Integer

The maximum threads constraint this work manager uses.

name

String

The name of this work manager.

11.2.4 jetty-web-app Configuration Object

Use the following configuration object to define a Web application for use by Jetty:

Table 11-4 Configuration Parameters for the jetty-web-app Element

Parameter
Type
Description

context-path

String

The context path where this web app is deployed in the web server's name space.

If not set, it defaults to "/".

scratch-directory

String

The location where Jetty stores temporary files for this web app.

Overrides the scratch-directory parameter in the Section 11.2, "Configuring a Jetty Server Instance."

path

String

A file name that points to the location of the web app on the server. It may be a directory or a WAR file.

jetty-name

String

The name of the Jetty service where this web application is deployed. It must match the name of an existing Section 11.2, "Configuring a Jetty Server Instance."

name

String

The name of this configuration object.

11.2.5 Developing Servlets for Jetty

Oracle CEP supports development of servlets for deployment to Jetty by creating a standard Java EE Web Application and configuring it using the Section 11.2.4, "jetty-web-app Configuration Object."

11.2.6 Web Application Deployment

Oracle CEP supports deployments packaged either as WAR files or as exploded WAR files, as described in version 2.4 of the Java Servlet Specification.

You can deploy pre-configured web applications from an exploded directory or WAR file by including them in the server configuration.

Security constraints specified in the standard web.xml file are mapped to the Common Security Services security provider. The Servlet API specifies declarative role-based security, which means that particular URL patterns can be mapped to security roles.

11.3 Example Jetty Configuration

The following snippet of a config.xml file provides an example Jetty configuration; only Jetty-related configuration information is shown:

Example 11-1 Example Jetty Configuration

<config>
  <netio>
    <name>JettyNetIO</name>
    <port>9002</port>
  </netio>
  <work-manager>
    <name>WM</name>
    <max-threads-constraint>64</max-threads-constraint>
    <min-threads-constraint>3</min-threads-constraint>
  </work-manager>
  <jetty>
    <name>TestJetty</name>
    <work-manager-name>WM</work-manager-name>
    <network-io-name>JettyNetIO</network-io-name>
    <debug-enabled>false</debug-enabled>
    <scratch-directory>JettyWork</scratch-directory>
  </jetty>
  <jetty-web-app>
    <name>test</name>
    <context-path>/test</context-path>
    <path>testWebApp.war</path>
    <jetty-name>TestJetty</jetty-name>
  </jetty-web-app>
</config>

12 Configuring JMX for Oracle CEP

This chapter describes how to configure Java Management Extensions (JMX) for use with Oracle Complex Event Processing (Oracle CEP), including accessing MBeans, JMX configuration objects and programmatically connecting and configuring components with JMX APIs.

Section 12.1, "Overview of JMX Support in Oracle CEP"

Section 12.2, "Configuring JMX"

Section 12.3, "Managing With JMX"

12.1 Overview of JMX Support in Oracle CEP

Oracle CEP provides standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification. Software developers can use these interfaces to monitor Oracle CEP MBeans, to change the configuration of an Oracle CEP domain, and to monitor Oracle CEP applications.

For more information, see:

Section 12.1.1, "Understanding JMX Configuration"

Section 12.1.2, "Understanding JMX Management"

12.1.1 Understanding JMX Configuration

Before you can manage Oracle CEP applications, servers, and domains using JMX and Oracle CEP MBeans, you must first configure the JMX service on your Oracle CEP server.

You configure the Oracle CEP JMX service using the following elements in the config.xml file that describes your Oracle CEP domain:

jmx: See Section 12.2.1, "jmx Configuration Object" for details.

rmi: See Section 12.2.2, "rmi Configuration Object" for details.

jndi-context: See Section 12.2.3, "jndi-context Configuration Object" for details.

exported-jndi-context: See Section 12.2.4, "exported-jndi-context Configuration Object" for details

For more information, see Section 12.2, "Configuring JMX".

12.1.2 Understanding JMX Management

Oracle CEP applications define an event processing network (EPN) that is made up of components such as adapters, channels, and processors. You deploy these applications to an Oracle CEP instance that has been started in a domain.

Note:

Components are also sometimes referred to as stages, in particular in the management Javadocs. However, for consistency with the rest of the Oracle CEP documentation, this section uses the term components.

You can dynamically configure each component in the EPN using managed beans, or MBeans. Typical configuration tasks include adding and removing Oracle CQL or EPL rules, changing channel max size, subscribing to notifications, and executing operations.

You manipulate the MBeans using any of the following:

Oracle CEP Visualizer: the Oracle CEP graphical administration console.

For more information, see Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

wlevs.Admin: the Oracle CEP command-line administration utility.

For more information, see Appendix A, "wlevs.Admin Command-Line Reference".

Deployer: the Oracle CEP command-line deployment utility.

For more information, see Appendix B, "Deployer Command-Line Reference".

jconsole: the JMX console that the Java JDK provides.

Your own Java code using standard JMX APIs: http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement.

This section describes:

Section 12.1.2.1, "Accessing the Oracle CEP JMX Server"

Section 12.1.2.2, "Accessing Configuration MBeans"

Section 12.1.2.3, "Accessing Oracle CEP Runtime MBeans"

For more information, see:

Section 12.1.3, "Understanding Oracle CEP MBeans"

Section 12.3, "Managing With JMX"

12.1.2.1 Accessing the Oracle CEP JMX Server

To access Oracle CEP MBeans, you must first connect to the Oracle CEP JMX server.

Oracle CEP does not support 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 copy the following Oracle CEP server JAR files to the client classpath of the host from which you want to connect to the Oracle CEP server:

ORACLE_CEP_HOME\modules\com.bea.core.jmx_8.0.0.0.jar

ORACLE_CEP_HOME\modules\com.bea.core.rmi_7.0.0.0.jar

ORACLE_CEP_HOME\modules\com.bea.core.jndi.context_8.0.0.0.jar

ORACLE_CEP_HOME\modules\com.bea.core.logging_1.8.0.0.jar

ORACLE_CEP_HOME\modules\com.bea.core.bootbundle_11.0.0.0.jar

Where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP (such as d:\oracle_home).

You must launch your JMX client (such as jconsole) using the following command line options and classpath (split for readability; in practice, the command should be on one line):

prompt> java -Djmx.remote.protocol.provider.pkgs=com.bea.core.jmx.remote.provider
-Dmx4j.remote.resolver.pkgs=com.bea.core.jmx.remote.resolver
-Djava.naming.factory.initial=com.bea.core.jndi.context.ContextFactory
-classpath %JAVA_HOME%\lib\jconsole.jar;MODULE_HOME\modules\com.bea.core.jmx_8.0.0.0.jar;
MODULE_HOME\modules\com.bea.core.rmi_7.0.0.0.jar;MODULE_HOME\modules\com.bea.core.jndi.context_7.0.0.0.jar;
MODULE_HOME\modules\com.bea.core.logging_1.5.0.0.jar;MODULE_HOME\modules\com.bea.core.bootbundle_8.0.0.0.jar
sun.tools.jconsole.JConsole

Where MODULE_HOME is the directory you copied the Oracle CEP server JAR files to.

To connect to the Oracle CEP JMX server, you must 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:

Section 12.3.1, "How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client"

Section 12.3.6, "How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled"

12.1.2.2 Accessing Configuration MBeans

You can also perform some configuration and application life cycle management of the server, domain, and deployed applications using MBeans, although this section predominantly describes configuring individual application components. However, because server, domain, and application configuration is also done using MBeans, much of the information in this section is applicable.

Each component in a deployed application (adapter, channel, or processor) has a configuration MBean that manages the underlying configuration of the component. Each type of component has its own set of manageable artifacts. For example, you can dynamically configure the maximum number of threads for a channel or the Oracle CQL rules associated with a processor.

12.1.2.3 Accessing Oracle CEP Runtime MBeans

You can also gather monitoring information for each component in the EPN using runtime MBeans. Monitoring information includes throughput (number of events passing through a component) and latency (how long it takes an event to pass through a component).

12.1.3 Understanding Oracle CEP MBeans

Oracle CEP exposes the following types of MBeans:

Configuration MBeans—Contain information about the configuration of components in an EPN, a deployed Oracle CEP application, the server and domain configurations. These MBeans have a fixed management interface and represent the information contained in the domain config.xml file and the component configuration XML files. Examples of standard MBeans include CQLProcessorMBean and EventChannelMBean.

Runtime MBeans—Contain information about throughput and latency of a component.

For full reference information about Oracle CEP MBeans and management in general, see the following classes in the Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing:

com.bea.wlevs.management.configuration

com.bea.wlevs.management.runtime

com.bea.wlevs.monitor.management

com.bea.wlevs.monitor

com.bea.wlevs.processor.epl.management

com.bea.wlevs.deployment.mbean

This section describes:

Section 12.1.3.1, "Oracle CEP Configuration MBeans"

Section 12.1.3.2, "Oracle CEP Runtime MBeans"

Section 12.1.3.3, "Oracle CEP MBean Hierarchy"

12.1.3.1 Oracle CEP Configuration MBeans

When you deploy an Oracle CEP application, the server automatically creates a configuration MBean for each component in the EPN whose manageability has been enabled, or in other words, for each component registered in the EPN assembly file. If you have extended the configuration of an adapter, then the server deploys a custom configuration MBean for the adapter.

Using JMX, you can dynamically configure the component using its configuration MBean. For example, using the StreamMBean.setMaxSize() method you can set the size of a channel component.

12.1.3.1.1 Configuration MBean Naming

Oracle CEP configuration MBeans are arranged in a hierarchy. The object name of each MBean reflects its position in the hierarchy. A typical object naming pattern is as follows:

com.bea.wlevs:Name=name,Type=type,[TypeOfParentMBean=NameOfParentMBean]

where:

com.bea.wlevs: is the JMX domain name.

Name=name,Type=type,[TypeOfParentMBean=NameOfParentMBean] is a set of JMX key properties.

The order of the key properties is not significant, but the object name must begin with com.bea:wlevs:.

For example, the object name of the MBean corresponding to a processor called myprocessor in the application myapplication in the domain is as follows:

com.bea.wlevs:Name=myprocessor,Type=EPLProcessor,Application=myapplication

Table 12-1 describes the key properties that Oracle CEP encodes in its MBean object names.

Table 12-1 Oracle CEP MBean Object Name Key Properties

This Key Property
Specifies

Name=name

The string that you provided when you created the resource that the MBean represents. This is typically the name of a component.

The name of a particular component is specified in the EPN assembly file using the id attribute of the component registration.

For example, in the case of processors, the entry in the EPN assembly file might look like the following:

<wlevs:processor id="myprocessor" advertise="true" />

In this case, the key property would be Name=myprocessor.

Type=type

The short name of the MBean's type. The short name is the unqualified type name without the MBean suffix.

For example, for an MBean that is an instance of the CQLProcessorMBean, use CQLProcessor. In this case, the key property would be Type=CQLProcessor.

TypeOfParentMBean=NameOfParentMBean

Specifies the type and name of the parent MBean.

For components, this is always Application=application_name, where application_name refers to the name of the application of which the component is a part.

The name of a particular Oracle CEP application is specified with the Bundle-SymbolicName header of the MANIFEST.MF file of the application bundle. For example, if an application has the following MANIFEST.MF snippet (only relevant parts are shown):

Manifest-Version: 1.0
Archiver-Version:
Build-Jdk: 1.5.0_06
....
Bundle-SymbolicName: myapplication

then the key property would be Application=myapplication.

Table 12-2 shows examples of configuration MBean objects names that correspond to the component declarations in the HelloWorld sample EPN assembly file. In each example, the application name is helloworld and the domain name is mydomain.

Table 12-2 Component Declaration Example With Corresponding MBean Object Names

EPN Assembly File Component Declaration
Corresponding Configuration MBean Object Name

<wlevs:processor id="helloworldProcessor" />

com.bea.wlevs:Name=helloworldProcessor,Type=EPLProcessor,Application=helloworld,Domain=mydomain

EPLProcessor is the standard configuration MBean for processor components. The manageable property is rules.

<wlevs:channel id="helloworldInstream">
  <wlevs:listener ref="helloworldProcessor"/>
  <wlevs:source ref="helloworldAdapter"/>
</wlevs:channel>

com.bea.wlevs:Name=helloworldInstream,Type=Channel,Application=helloworld,Domain=mydomain

Channel is the standard configuration MBean for a channel component. The manageable properties are MaxSize and MaxThreads.

12.1.3.2 Oracle CEP Runtime MBeans

You can also gather monitoring information for each component in the EPN using runtime MBeans. Oracle CEP server defines the following metrics that you can monitor for each component:

Throughput—The number of events processed by the component. The parameters for this metric are: throughput time interval, aggregation time interval, the unit of time for the intervals.

Average Latency—The average amount of time it takes an event to pass through a component, or latency. Parameters: aggregation time interval, the unit of time for the interval.

Maximum Latency—The maximum amount of time it takes an event to pass through a component. Parameters: aggregation time interval, the unit of time for the interval.

Average Latency Threshold—Specifies whether the average latency of events between the start- and end-points of a component crosses a specified threshold. Parameters: aggregation time interval, threshold, the unit of time for the interval.

12.1.3.2.1 Runtime MBean Naming

Runtime MBeans are named using the same pattern as with configuration mbeans except for one extra property: Direction. This property has two valid values: OUTBOUND or INBOUND that refer to the point at which you want to gather the statistic OUTBOUND means that you want to gather throughput or latency as events flow out of the specified component; similarly INBOUND means you want to gather the monitoring information as events flow into a component.

For example, the object name of the runtime MBean corresponding to a processor called myprocessor in the application myapplication, in which events will be monitored as they flow into the component, is as follows:

com.bea.wlevs:Name=myprocessor,Type=EPLProcessor,Application=myapplication,Direction=INBOUND

See Section 12.1.3.1.1, "Configuration MBean Naming" for details about configuration MBean naming.

12.1.3.3 Oracle CEP MBean Hierarchy

Figure 12-1 describes the Oracle CEP MBean tree.

Figure 12-1 Oracle CEP MBean Tree

All MBeans must be registered in an MBean server under an object name of type javax.management.ObjectName. Oracle CEP follows a convention in which object names for child MBeans contain part of its parent MBean object name.

There are two main MBean roots: DomainMBean and DomainRuntimeMBean. The former includes configuration MBeans for the entire domain, the latter contains runtime information, such as statistics, and local services, such as Monitor, that are generally scoped to a single server instance.

ApplicationMBean is a child of the DomainMBean instead of the ServerMBean. This is because an application is unique within a domain, and can span multiple servers.

Figure 12-2 shows the main classes and relationships that make up the object model.

Figure 12-2 Oracle CEP MBean Object Model

Most MBeans are notification emitters that generate AttributeChangeNotifications. In other words, a JMX client can register to receive attribute change notifications regarding changes to application state, insertion and removal of applications at the domain, channel size and thread changes, insertion and removal of rules, and so on.

12.2 Configuring JMX

You configure the Oracle CEP JMX service using the following elements in the config.xml file that describes your Oracle CEP domain:

jmx: See Section 12.2.1, "jmx Configuration Object" for details.

rmi: See Section 12.2.2, "rmi Configuration Object" for details.

jndi-context: See Section 12.2.3, "jndi-context Configuration Object" for details.

exported-jndi-context: See Section 12.2.4, "exported-jndi-context Configuration Object" for details

For information on security configuration tasks that affect JMX, see Section 10.8.2, "Configuring JMX Security".

For more information, see:

Section 12.1.1, "Understanding JMX Configuration"

Section 12.2.5, "Example of Configuring JMX"

12.2.1 jmx Configuration Object

Table 12-3 lists the jmx element child elements in the config.xml file that you must configure.

Table 12-3 Configuration Parameters for the jmx Element

Parameter
Type
Description

rmi-service-name

String

The name of the RMI service with which the jmx server will register to receive calls.

jndi-service-name

String

The name of the JNDI service to which the jmx server will bind its object.

12.2.2 rmi Configuration Object

The Oracle CEP RMI service provides:

Ability to register a POJO interface in a server for remote method invocation from a client.

Ability to register for any context propagation from the client to the server on a remote method invocation, intercept, and act on this propagated context in the server.

Table 12-4 lists the rmi element child elements in the config.xml file that you use to export server-side objects to remote clients.

Table 12-4 Configuration Parameters for the rmi Element

Parameter
Type
Description

heartbeat-period

int

The number of failed heartbeat attempts before triggering disconnect notifications to all registered listeners.

http-service-name

String

The name of the HTTP service used to register remote objects (such as Jetty, see Section 11.1, "Overview of Jetty Support in Oracle Complex Event Processing").

heartbeat-interval

int

The amount of time, in milliseconds, between heartbeats.

Once the number of unsuccessful heartbeat attempts has reached the value specified by the HeartbeatPeriod parameter, all registered DisconnectListener instances are notified.

name

String

The name of this configuration object.

12.2.3 jndi-context Configuration Object

The JNDI Factory Manager is responsible for supporting JNDI in an OSGi environment. It allows JNDI providers to be supplied as OSGi bundles, and for code running inside OSGi bundles to have full access to the JNDI environment.

The Factory Manager consists of two components:

An OSGi bundle, which provides the OSGi-specific factory management code, to look up JNDI objects using the appropriate OSGi classloader.

JNDI "glue code," internal to Oracle CEP, that initializes the JNDI environment to support the factory manager bundle.

Table 12-5 lists the jndi-context element child elements in the config.xml file that you must configure.

Table 12-5 Configuration Parameters for the jndi-context Element

Parameter
Type
Description

default-provider

boolean

If true, the default Oracle CEP JNDI provider is used.

Default value is true.

name

String

The name of this configuration object.

12.2.4 exported-jndi-context Configuration Object

Requires a configured Section 12.2.3, "jndi-context Configuration Object."

Use this configuration object to export a remote JNDI service to a client using RMI. A JNDI context is registered with the RMI service to provide remote access to clients that pass a provider URL parameter in their InitialContext object.

Table 12-6 lists the exported-jndi-context element child elements in the config.xml file that you must configure.

Table 12-6 Configuration Parameters for the exported-jndi-context Element

Parameter
Type
Description

rmi-service-name

String

The name of the RMI service that should be used to serve this JNDI context over the network. It must match an existing <rmi> configuration object. See Section 12.2.2, "rmi Configuration Object."

name

String

The name of this configuration object.

The value of this element must be different from the value of the <name> child element of <jndi-context> in the same config.xml file.

12.2.5 Example of Configuring JMX

Example 12-1 shows a config.xml snippet with JMX configuration; only relevant parts of the file are shown.

Example 12-1 JMX Configuration

<config>
  <netio>
    <name>JettyNetio</name>
    <port>12345</port>
  </netio>
  <work-manager>
    <name>WM</name>
    <fairshare>5</fairshare>
    <min-threads-constraint>1</min-threads-constraint>
    <max-threads-constraint>4</max-threads-constraint>
  </work-manager>
  <jetty>
    <name>TestJetty</name>
    <work-manager-name>WM</work-manager-name>
    <network-io-name>JettyNetio</network-io-name>
  </jetty>
  <rmi>
    <name>RMI</name>
    <http-service-name>TestJetty</http-service-name>
  </rmi>
  <jndi-context>
    <name>JNDI</name>
  </jndi-context>
  <exported-jndi-context>
    <name>exportedJNDI</name>
    <rmi-service-name>RMI</rmi-service-name>
  </exported-jndi-context>
  <jmx>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-service-name>RMI</rmi-service-name>
  </jmx>
</config>

12.3 Managing With JMX

This section describes detailed examples of managing Oracle CEP components using JMX, including:

Section 12.3.1, "How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client"

Section 12.3.2, "How to Programmatically Connect to the Oracle CEP JMX Server From an Oracle CEP Client"

Section 12.3.3, "How to Programmatically Configure an Oracle CEP Component Using JMX APIs"

Section 12.3.4, "How to Programmatically Monitor the Throughput and Latency of an Oracle CEP Component Using JMX APIs"

Section 12.3.5, "How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Enabled"

Section 12.3.6, "How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled"

Note:

When using JConsole, you must start it with the Oracle CEP wlevsjconsole.cmd or wlevsjconsole.sh script. You cannot start jconsole directly.

For more information, see:

Section 12.1.1, "Understanding JMX Configuration"

Section 12.1.2, "Understanding JMX Management"

12.3.1 How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client

This section describes how to write Java code using the JMX API (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement) to connect to the Oracle CEP JMX server from a non-Oracle CEP client. This is the first step to all programmatic JMX management.

For information on connecting to the Oracle CEP JMX server from another Oracle CEP server, see Section 12.3.2, "How to Programmatically Connect to the Oracle CEP JMX Server From an Oracle CEP Client".

To programmatically connect to the Oracle CEP JMX server from a non-Oracle CEP client:

Be sure that the JMX service is configured for your domain.

For details see Section 12.2, "Configuring JMX".

Write the http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement Java code to configure the component using the appropriate MBean.

Consider the following JMX programming hints.

One of the first things you must do in your JMX program is to establish a connection to the JMX server running in the Oracle CEP server as Example 12-2 shows.

Example 12-2 Establishing a Connection to the Oracle CEP JMX Server

public static void initConnection(String hostname, int port, String username, char[] password)
  throws IOException,MalformedURLException {

  Map<String,Object> env = makeSecureEnv();
  env.put("jmx.remote.protocol.provider.pkgs","com.bea.core.jmx.remote.provider");
  env.put("mx4j.remote.resolver.pkgs","com.bea.core.jmx.remote.resolver");
  env.put("java.naming.factory.initial","com.bea.core.jndi.context.ContextFactory");

  JMXServiceURL serviceUrl = new JMXServiceURL(
      "MSARMI","localhost",9002,"/jndi/jmxconnector"
  );

  System.out.println("Service: " + serviceURL.toString());

  JMXConnector connector = JMXConnectorFactory.connect(serviceUrl,env);

  MBeanServerConnection connection = connector.getMBeanServerConnection();
}

// The JMXConnectorFactory.connect() method's second parameter is a Map object that sets up a
// secure environment using the makeSecureEnv() method, which looks like the following:

private static Map<String,Object> makeSecureEnv() {
    Map<String,Object> env = new HashMap<String,Object>();
    String username = "wlevs" ;
    char[] password = { 'w','l','e','v','s' };
    env.put(JMXConnector.CREDENTIALS, new Serializable[]{username,password});
    env.put("jmx.remote.authenticator", "com.bea.core.jmx.server.CEAuthenticator");
    System.setProperty("jmx.remote.authenticator", "com.bea.core.jmx.server.CEAuthenticator");
    return env;
}

12.3.2 How to Programmatically Connect to the Oracle CEP JMX Server From an Oracle CEP Client

This section describes how to write Java code using the JMX API (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement) to connect to the Oracle CEP JMX server from another Oracle CEP server. This is the first step to all programmatic JMX management.

For information on connecting to the Oracle CEP JMX server from a non-Oracle CEP client, see Section 12.3.1, "How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client".

To programmatically connect to the Oracle CEP JMX server from an Oracle CEP client:

Be sure that the JMX service is configured for your domain.

For details see Section 12.2, "Configuring JMX".

Write the http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement Java code to configure the component using the appropriate MBean.

Consider the following JMX programming hints.

One of the first things you must do in your JMX program is to establish a connection to the JMX server running in the Oracle CEP server as Example 12-2 shows.

Example 12-3 Establishing a Connection to the Oracle CEP JMX Server

public static void initConnection(String hostname, int port, String username, char[] password)
  throws IOException,MalformedURLException {

  Map<String,Object> env = makeSecureEnv();

  // This is an OSGi necessity
  env.put(
      JMXConnectorFactory.DEFAULT_CLASS_LOADER,
      com.bea.core.jmx.remote.provider.msarmi.ServerProvider.class.getClassLoader()
  );
  env.put(
      JMXConnectorFactory.PROTOCOL_PROVIDER_CLASS_LOADER,
      com.bea.core.jmx.remote.provider.msarmi.ServerProvider.class.getClassLoader()
  );

  JMXServiceURL serviceUrl = new JMXServiceURL(
      "MSARMI","localhost",9002,"/jndi/jmxconnector"
  );

  System.out.println("Service: " + serviceURL.toString());

  env.put(
      JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
      "com.bea.core.jmx.remote.provider"
  );

  System.setProperty("mx4j.remote.resolver.pkgs", "com.bea.core.jmx.remote.resolver");

  JMXConnector connector = JMXConnectorFactory.connect(url, env);
  connector.connect();

  MBeanServerConnection connection = connector.getMBeanServerConnection();
  ...
}

// The JMXConnectorFactory.connect() method's second parameter is a Map object that sets up a
// secure environment using the makeSecureEnv() method, which looks like the following:

private static Map<String,Object> makeSecureEnv() {
    Map<String,Object> env = new HashMap<String,Object>();
    String username = "wlevs" ;
    char[] password = { 'w','l','e','v','s' };
    env.put(JMXConnector.CREDENTIALS, new Serializable[]{username,password});
    env.put("jmx.remote.authenticator", "com.bea.core.jmx.server.CEAuthenticator");
    System.setProperty("jmx.remote.authenticator", "com.bea.core.jmx.server.CEAuthenticator");
    return env;
}

12.3.3 How to Programmatically Configure an Oracle CEP Component Using JMX APIs

This section describes how to write Java code using the JMX API (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement) to access Oracle CEP MBeans.

To programmatically configure an Oracle CEP component using JMX APIs:

Acquire a connection to the Oracle CEP JMX server.

For details see Section 12.3.1, "How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client".

Write the http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement Java code to configure the component using the appropriate MBean.

Consider the following JMX programming hints.

Example 12-4 shows how to use the connection to start getting information about the domain and its deployed applications by querying MBeans.

First the code shows how to get all MBeans whose type is Domain; there should only be one. Then, using the DomainMBean, the sample shows how to retrieve a list of all the deployed applications in the domain (using ApplicationMBean):

Example 12-4 Querying MBeans

Set domainObjectNames = connection.queryMBeans(
    ObjectName.getInstance(
        ManagementConstants.DOMAIN_NAME + ":" +
        ManagementConstants.TYPE_PROPERTY + "=" +
        DomainMBean.MBEAN_TYPE + ",*"
    ),
    null
);
ObjectName domainName =  ((ObjectInstance) domainObjectNames.iterator().next()).getObjectName();
System.out.println("Domain Name: " + domainName.getKeyProperty(ManagementConstants.NAME_PROPERTY));
ObjectName [] applicationNames =
     (ObjectName[]) connection.getAttribute(domainName, "ApplicationMBeans");
ObjectName selectedApplicationObjectName = null ;
for (ObjectName applicationName : applicationNames) {
   String name =
     applicationName.getKeyProperty(ManagementConstants.NAME_PROPERTY);
   String status =
     (String) connection.getAttribute(applicationName, "State");
    System.out.println("Application: " + name + " Status: " + status);
    selectedApplicationObjectName = applicationName ;
}

12.3.4 How to Programmatically Monitor the Throughput and Latency of an Oracle CEP Component Using JMX APIs

This section describes how to write Java code using the JMX API (http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement) to access Oracle CEP MBeans and dynamically monitor the throughput and latency of an Oracle CEP component.

To dynamically configure an Oracle CEP component using JMX APIs:

Acquire a connection to the Oracle CEP JMX server.

For details see Section 12.3.1, "How to Programmatically Connect to the Oracle CEP JMX Server From a Non-Oracle CEP Client".

Acquire an instance of a MonitorRuntimeMBean for the component you want to monitor as Example 12-5 shows.

Example 12-5 Acquiring an Instance of a MonitorRuntimeMBean

m_processorInbound = ObjectName.getInstance(
    "com.bea.wlevs:Name=myprocessor,
    Type=EPLProcessor,
    Application=myapplication,
    Direction=INBOUND"
);

Be sure you specify whether you want to monitor incoming events (INBOUND) or outgoing events (OUTBOUND). For example:

Use the MonitorRuntimeMBean to acquire an instance of ProbeRuntimeMBean for the type of statistic you want as Example 12-6 shows.

Example 12-6 Acquiring an Instance of ProbeRuntimeMBean

ProbeRuntimeMBean probeON = m_testBean.getMonitorRuntimeMBean().monitorAvgThroughput(
    m_processorInbound,
    1000,
    1000
);

The MonitorRuntimeMBean has methods for each type of statistic you can gather. For example, you execute monitorAvgLatency() if you want to monitor the average latency, monitorAvgThroughput() to monitor the average throughput, and so on. These methods all return ProbeRuntimeMBean.

Use the ProbeRuntimeMbean instance to get the actual runtime metrics in one of the following ways:

Use the ProbeRuntimeMBean method getMetric() to pull the information.

Use javax.management.NotificationBroadcaster.addNotificationListener() to have the information pushed to you every time there is a change in the metrics.

When you are finished gathering monitoring information, unregister the MBean from the MBean server as Example 12-7 shows.

Example 12-7 Unregistering the MBean

probON.terminate();

For additional details about these MBean interfaces and how to use them to monitor throughput and latency, see the com.bea.wlevs.monitor.management package in the Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing.

12.3.5 How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Enabled

You can use the wlevsjconsole script to connect to an Oracle CEP JMX server running on your local host or on a remote host to browse and manage Oracle CEP MBeans with the JDK jconsole.

This procedure describes how to use JConsole when the Oracle CEP server has security enabled. This is the default configuration and is recommended for production servers. Alternatively, you can connect to the JMX server with security disabled (see Section 12.3.6, "How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled").

For more information, see Section 12.1.2.1, "Accessing the Oracle CEP JMX Server".

Note:

When using JConsole, you must start it with the Oracle CEP wlevsjconsole.cmd or wlevsjconsole.sh script. You cannot start jconsole directly.

To connect to a local or remote Oracle CEP JMX server using JConsole with security enabled:

Ensure that the local or remote Oracle CEP server is running.

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Launch jconsole using the wlevsjconsole.cmd or wlevsjconsole.sh script located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP (such as /oracle_home).

To connect to a local Oracle CEP server, enter:

prompt> wlevsjconsole.cmd

To connect to a remote Oracle CEP server, enter:

prompt> wlevsjconsole.cmd HOST-NAME:PORT

Where HOST-NAME is the name of the remote host and PORT is the NetIO port as configured in the remote host's ORACLE_CEP_HOME/user_projects/domains/DOMAIN-NAME/defaultserver/config/config.xml file.

The jconsole browser attempts to log into the JMX server and initially fails as Figure 12-3 shows.

Figure 12-3 Jconsole Initial Login Attempt

Click Cancel.

The Jconsole New Connection dialog appears as shown in Figure 12-4.

Figure 12-4 JConsole New Connection Dialog

Configure the New Connection dialog as Table 12-7 describes.

Table 12-7 JConsole New Connection Attributes

Attribute
Description

Remote Process

Enter the following URL:

service:jmx:msarmi://HOST-NAME:PORT/jndi/jmxconnector

Where HOST-NAME is the name of the local or remote host and PORT is the NetIO port as configured in the remote host's ORACLE_CEP_HOME/user_projects/domains/DOMAIN-NAME/defaultserver/config/config.xml file (default: 9002).

Username

Enter an Oracle CEP administration password.

Default: wlevs.

Password

Enter the password for the Oracle CEP administration password you chose.

Default: wlevs.

Click Connect.

The jconsole browser opens and provides access to Oracle CEP MBeans as Figure 12-6 shows.

Figure 12-5 JConsole Browser

12.3.6 How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Disabled

You can use the wlevsjconsole script to connect to an Oracle CEP JMX server running on your local host or on a remote host to browse and manage Oracle CEP MBeans with the JDK jconsole.

This procedure describes how to use JConsole when the Oracle CEP server has security disabled. This is a common development configuration and is not recommended for production servers. Alternatively, you can connect to the JMX server with security enabled (see Section 12.3.5, "How to Connect to a Local or Remote Oracle CEP JMX Server Using JConsole With Security Enabled").

For more information, see Section 12.1.2.1, "Accessing the Oracle CEP JMX Server".

Note:

When using JConsole, you must start it with the Oracle CEP wlevsjconsole.cmd or wlevsjconsole.sh script. You cannot start jconsole directly.

To connect to a local or remote Oracle CEP JMX server using JConsole with security disabled:

Ensure that the local or remote Oracle CEP server is running with security disabled.

For more information, see Section 10.11, "Disabling Security".

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Launch jconsole using the wlevsjconsole.cmd or wlevsjconsole.sh script located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME refers to the directory in which you installed Oracle CEP (such as /oracle_home).

To connect to a local Oracle CEP server, enter:

prompt> wlevsjconsole.cmd

To connect to a remote Oracle CEP server, enter:

prompt> wlevsjconsole.cmd HOST-NAME:PORT

Where HOST-NAME is the name of the remote host and PORT is the NetIO port as configured in the remote host's ORACLE_CEP_HOME/user_projects/domains/DOMAIN-NAME/defaultserver/config/config.xml file.

The script automatically connects to the JMX server and the jconsole browser opens and provides access to Oracle CEP MBeans as Figure 12-6 shows.

Figure 12-6 JConsole Browser

13 Configuring JDBC for Oracle CEP

This chapter describes how to configure Java Database Connectivity (JDBC) for use with Oracle Complex Event Processing (Oracle CEP), including information on configuring data sources and on using Oracle and Type 4 Data Direct JDBC drivers.

Section 13.1, "Overview of Database Access from an Oracle CEP Application"

Section 13.2, "Description of Oracle CEP Data Sources"

Section 13.3, "Configuring Access to a Database Using the Oracle JDBC Driver"

Section 13.4, "Configuring Access to a Database Using the Type 4 JDBC Drivers from Data Direct"

Section 13.5, "Configuring Access to a Different Database Driver or Driver Version"

13.1 Overview of Database Access from an Oracle CEP Application

Oracle CEP supports Java Database Connectivity (JDBC) 3.0 (see http://java.sun.com/products/jdbc/download.html#corespec30) for relational database access.

The JDBC API (see http://java.sun.com/javase/technologies/database/index.jsp) provides a standard, vendor-neutral mechanism for connecting to and interacting with database servers and other types of tabular resources that support the API. The JDBC javax.sql.DataSource interface specifies a database connection factory that is implemented by a driver. Instances of DataSource objects are used by applications to obtain database connections (instances of java.sql.Connection). After obtaining a connection, an application interacts with the resource by sending SQL commands and receiving results.

Oracle CEP provides the following JDBC drivers:

Oracle 11.2 thin driver (see Section 13.1.1, "Oracle JDBC Driver")

SQL Server Type 4 JDBC Driver from DataDirect (see Section 13.1.2, "Type 4 JDBC Driver for SQL Server from DataDirect")

Optionally, you can use your own JDBC driver (see Section 13.5.3, "How to Access a Database Driver Using bootclasspath").

Oracle CEP also provides a DataSource abstraction that encapsulates a JDBC driver DataSource object and manages a pool of pre-established connections, and the Oracle WebLogic Server WLConnection interface provides useful methods for accessing and manipulating Oracle data sources. For more information, see Section 13.2, "Description of Oracle CEP Data Sources".

13.1.1 Oracle JDBC Driver

Oracle CEP includes the Oracle 11.2 Thin driver packaged in the following JAR files:

ORACLE_CEP_HOME/modules/com.bea.oracle.ojdbc5_1.0.0.0_11-2-0-0.jar: for use with Java SE 5.

ORACLE_CEP_HOME/modules/com.bea.oracle.ojdbc6_1.0.0.0_11-2-0-0.jar: for use with Java SE 6.

The JDBC Thin driver is a pure Java, Type IV driver that can be used in applications and applets. It is platform-independent and does not require any additional Oracle software on the client side. The JDBC Thin driver communicates with the server using SQL*Net to access the Oracle Database.

For more information, see:

Section 13.1.3.1, "Databases Supported by the Oracle JDBC Driver"

Section 13.3, "Configuring Access to a Database Using the Oracle JDBC Driver"

http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html

13.1.2 Type 4 JDBC Driver for SQL Server from DataDirect

Oracle CEP provides a Type 4 JDBC driver from DataDirect for high-performance JDBC access to the SQL Server database. The Type 4 JDBC driver is optimized for the Java environment, allowing you to incorporate Java technology and extend the functionality and performance of your existing system.

The Oracle CEP Type 4 JDBC drivers from DataDirect are proven drivers that:

Support performance-oriented and enterprise functionality such as distributed transactions, savepoints, multiple open result sets and parameter metadata.

Are Java EE Compatibility Test Suite (CTS) certified and tested with the largest JDBC test suite in the industry.

Include tools for testing and debugging JDBC applications.

For more information, see:

Section 13.1.3.2, "Databases Supported by the Type 4 JDBC Driver for SQL Server from DataDirect"

Section 13.4, "Configuring Access to a Database Using the Type 4 JDBC Drivers from Data Direct"

13.1.3 Supported Databases

Oracle CEP server supports different databases depending on the type of JDBC driver you use:

Section 13.1.3.1, "Databases Supported by the Oracle JDBC Driver"

Section 13.1.3.2, "Databases Supported by the Type 4 JDBC Driver for SQL Server from DataDirect"

13.1.3.1 Databases Supported by the Oracle JDBC Driver

Using the Oracle JDBC driver, you can access the following Oracle databases:

Oracle Database 11g release 2 (11.2)

For more information, see Section 13.1.1, "Oracle JDBC Driver".

13.1.3.2 Databases Supported by the Type 4 JDBC Driver for SQL Server from DataDirect

Using the SQL Server Type 4 JDBC Driver from DataDirect, you can access the following SQL Server databases:

Microsoft SQL Server 2005

Microsoft SQL Server 2000

Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)

Microsoft SQL Server 2000 Enterprise Edition (64-bit)

Microsoft SQL Server 7.0

For more information, see Section 13.1.2, "Type 4 JDBC Driver for SQL Server from DataDirect".

13.2 Description of Oracle CEP Data Sources

Oracle CEP DataSource provides a JDBC data source connection pooling implementation that supports the Java Database Connectivity (JDBC 3.0) specification. Applications reserve and release Connection objects from a data source using the standard DataSource.getConnection and Connection.close APIs respectively.

Figure 13-1 shows the relationship between data source, connection pool, and Connection instances.

Figure 13-1 Oracle CEP Data Source

You must use the Oracle CEP server default data source or configure your own Oracle CEP DataSource in the server's config.xml file if you want to access a relational database:

From an Oracle CQL processor rule.

See "Configuring an Oracle CQL Processor Table Source" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

From an EPL processor rule.

See "Configuring an EPL Processor" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Event record and playback.

See "Storing Events in the Persistent Event Store" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

From a cache loader or store.

See:

"Configuring an Oracle CEP Local Cache Store" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

"Configuring an Oracle Coherence Cache Loader or Store" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse

You do not have to configure a DataSource in the server's config.xml file if you use the JDBC driver's API, such as DriverManager, directly in your application code.

For more information, see:

Section 13.2.1, "Default Data Source Configuration"

Section 13.2.2, "Custom Data Source Configuration"

13.2.1 Default Data Source Configuration

By default, the Oracle CEP server creates a local transaction manager. The transaction manager in turn depends on a configured RMI object, as described in Section 12.2.2, "rmi Configuration Object." Oracle CEP server guarantees that there will never be more than one transaction manager instance in the system.

If a database is unavailable at the time you start Oracle CEP server, by default, an Oracle CEP server data source retries every 10 seconds until it can create a connection. This allows the Oracle CEP server to successfully start up even if a database is unavailable. You can change the retry interval in the Oracle CEP server config.xml file using the connection-pool-params element connection-creation-retry-frequency-seconds child element. Setting this element to zero disables connection retry.

For more information, see Section 13.2.2, "Custom Data Source Configuration".

13.2.2 Custom Data Source Configuration

The Oracle CEP server config.xml file requires a configuration element for each data source that is to be created at runtime that references an external JDBC module descriptor.

This section describes how to configure a custom data source configuration. For more information on default data source configuration, see Section 13.2.1, "Default Data Source Configuration".

When you create an Oracle CEP domain using the Configuration Wizard, you can optionally configure a JDBC data source that uses one of the two DataDirect JDBC drivers; in this case the wizard updates the config.xml file for you. You configure the data source with basic information, such as the database you want to connect to and the connection username and password. You can also use the Configuration Wizard to update an existing server in a domain and add new data sources.

For more information, see:

"Creating and Updating Oracle CEP Standalone-Server Domains" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing

"Creating and Updating Oracle CEP Multi-Server Domains" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing

You can also update the config.xml file manually by adding a data-source element as Example 13-1 shows.

Example 13-1 Custom Data Source Configuration in Oracle CEP Server config.xml

<data-source>
    <name>rdbms</name>
    <data-source-params>
        <global-transactions-protocol>None</global-transactions-protocol>
    </data-source-params>
    <connection-pool-params>
        <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
        <initial-capacity>5</initial-capacity>
        <max-capacity>10</max-capacity>
        <connection-creation-retry-frequency-seconds>
            60
        </connection-creation-retry-frequency-seconds>
    </connection-pool-params>
    <driver-params>
        <url>jdbc:oracle:thin:@localhost:5521:rdb</url>
        <driver-name>oracle.jdbc.OracleDriver</driver-name>
        <properties>
            <element><name>user</name><value>scott</value></element>
            <element><name>password</name><value>tiger</value></element>
        </properties>
        <use-xa-data-source-interface>true</use-xa-data-source-interface>
    </driver-params>
</data-source>
<transaction-manager>
    <name>TM</name>
    <rmi-service-name>RMI</rmi-service-name>
</transaction-manager>

A data source depends on the availability of a local transaction manager. You can rely on the default Oracle CEP server transaction manager or configure one using the transaction-manager element of config.xml as Example 13-1 shows. The transaction manager in turn depends on a configured RMI object, as described in Section 12.2.2, "rmi Configuration Object."

If a database is unavailable at the time you start Oracle CEP server, by default, an Oracle CEP server data source retries every 10 seconds until it can create a connection. This allows the Oracle CEP server to successfully start up even if a database is unavailable. Example 13-1 shows how you can change the retry interval in the Oracle CEP server config.xml file using the connection-pool-params element connection-creation-retry-frequency-seconds child element. Setting this element to zero disables connection retry.

For the full list of child elements of the data-source element, in particular the connection-pool-params and data-source-params elements, see "Server Configuration XSD Schema: wlevs_server_config.xsd" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

For information on security configuration tasks that affect JDBC, see Section 10.8.3, "Configuring JDBC Security".

13.2.3 Getting the Native JDBC Connection

The Oracle Fusion Middleware Oracle WebLogic Server API Reference provides a WLConnection interface that contains useful methods for getting and manipulating Oracle data sources. For example, the following Java code gets the native Oracle database connection from the pooled connection object.

private DataSource ods;
private Connection wlConnection;
private OracleConnection connection;

wlConnection = ods.getConnection();
connection = (OracleConnection) ((WLConnection) wlConnection)
.getVendorConnection();

Note:

Be sure to close pooled connections when you are finished with them, and do not use a native connection object after the pooled connection has been closed.

13.3 Configuring Access to a Database Using the Oracle JDBC Driver

The Oracle JDBC driver is automatically installed with Oracle CEP and ready to use. For more information, see Section 13.1.1, "Oracle JDBC Driver".

To configure access to a database using the Oracle JDBC driver:

Configure the data source in the server's config.xml file:

To update the Oracle CEP server config.xml file using the Configuration Wizard, see "Creating and Updating Oracle CEP Standalone-Server Domains" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing.

To update the Oracle CEP server config.xml file manually, see Section 13.2.2, "Custom Data Source Configuration."

Note:

The url element for the Oracle JDBC driver is of the form:

<url>jdbc:oracle:thin:@HOST:PORT:SID</url>

If Oracle CEP is running, restart it so it reads the new data source information.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

13.4 Configuring Access to a Database Using the Type 4 JDBC Drivers from Data Direct

The type 4 JDBC drivers from DataDirect for SQL Server are automatically installed with Oracle CEP and ready to use. For more information, see Section 13.1.2, "Type 4 JDBC Driver for SQL Server from DataDirect".

To configure access to a database using the Type 4 JDBC drivers from Data Direct:

Configure the data source in the server's config.xml file:

To update the Oracle CEP server config.xml file using the Configuration Wizard, see "Creating and Updating Oracle CEP Standalone-Server Domains" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing.

To update the Oracle CEP server config.xml file manually, see Section 13.2.2, "Custom Data Source Configuration."

Note:

The url element for the type 4 JDBC drivers from DataDirect is of the form:

<url>jdbc:weblogic:sqlserver://HOST:PORT</url>

If Oracle CEP is running, restart it so it reads the new data source information.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

13.5 Configuring Access to a Different Database Driver or Driver Version

In some cases, you may need to use a different version of the Oracle Database driver or Data Direct drivers than the version bundled with Oracle CEP or you may need to use a database driver other than the Oracle Database driver or Data Direct drivers.

This section describes the following:

Section 13.5.1, "How to Access a Database Driver Using an Application Library Built With bundler.sh": this is the preferred method; you must create an OSGi bundle for your database driver.

Section 13.5.2, "How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse": this is the preferred method; you must create an OSGi bundle for your database driver.

Use this option if you wish to manually configure the activator implementation.

Section 13.5.3, "How to Access a Database Driver Using bootclasspath": this is an optional method; you do not need to create an OSGi bundle for your database driver.

13.5.1 How to Access a Database Driver Using an Application Library Built With bundler.sh

This procedure describes how to create an OSGi bundle for your driver using the bundler utility and deploy it on the Oracle CEP server.

This is the preferred method. If wish to manually configure the activator implementation, see Section 13.5.2, "How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse".

For more information, see "Creating Application Libraries" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

To access a database driver using an application library built with bundler.sh:

Set up your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Execute the bundler.sh script to create an OSGi bundle containing your driver.

The bundler.sh script is located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME is the directory in which you installed the Oracle CEP server.

Example 13-2 lists the bundler.sh command line options and Table 13-1 describes them.

Example 13-2 bundler.sh Command Line Options

bundler.sh
    -source <jar>
    -name <name>
    -version <version>
    [-factory <class>+]
    [-service <interface>+]
    [-stagedir <path>]
    [-targetdir <path>]

Table 13-1 bundler.sh Command Line Options

Argument
Description

-source

The path of the source JAR file to be bundled.

-name

The symbolic name of the bundle. The root of the target JAR file name is derived from the name value.

-version

The bundle version number. All exported packages are qualified with a version attribute with this value. The target JAR file name contains the version number.

-factory

An optional argument that specifies a space-delimited list of one or more factory classes that are to be instantiated and registered as OSGi services. Each service is registered with the OSGi service registry with name (-name) and version (-version) properties.

-service

An optional argument that specifies a space-delimited list of one or more Java interfaces that are used as the object class of each factory object service registration. If no interface names are specified, or the number of interfaces specified does not match the number of factory classes, then each factory object will be registered under the factory class name.

-stagedir

An optional argument that specifies where to write temporary files when creating the target JAR file.

Default: ./bundler.tmp

-targetdir

An optional argument that specifies the location of the generated bundle JAR file.

Default: current working directory (.).

Example 13-3 shows how to use the bundler.sh to create an OSGi bundle for an Oracle JDBC driver.

Example 13-3 Using the Bundler Utility

bundler.sh \
    -source C:\drivers\com.oracle.ojdbc14_11.2.0.jar \
    -name oracle11g \
    -version 11.2.0 \
    -factory oracle.jdbc.xa.client.OracleXADataSource oracle.jdbc.OracleDriver \
    -service javax.sql.XADataSource java.sql.Driver \
    -targetdir C:\stage

The source JAR is an Oracle driver located in directory C:\drivers. The name of the generated bundle JAR is the concatenation of the -name and -version arguments (oracle10g_11.2.0.jar) and is created in the C:\stage directory. The bundle JAR contains the files that Example 13-4 shows.

Example 13-4 Bundle JAR Contents

   1465 Thu Jun 29 17:54:04 EDT 2006 META-INF/MANIFEST.MF
1540457 Thu May 11 00:37:46 EDT 2006 com.oracle.ojdbc14_11.2.0.jar
   1700 Thu Jun 29 17:54:04 EDT 2006 com/bea/core/tools/bundler/Activator.class

The command line options specify that there are two factory classes that will be instantiated and registered as an OSGi service when the bundle is activated, each under a separate object class as Table 13-2 shows.

Table 13-2 Factory Class and Service Interface

Factory Class
Service Interface

oracle.jdbc.xa.client.OracleXADataSource

javax.sql.XADataSource

oracle.jdbc.OracleDriver

java.sql.Driver

Each service registration will be made with a name property set to oracle11g and a version property with a value of 11.2.0. Example 13-5 shows the Oracle CEP server log messages showing the registration of the services.

Example 13-5 Service Registration Log Messages

...
INFO: [Jun 29, 2006 5:54:18 PM] Service REGISTERED: { version=11.2.0, name=oracle11g, objectClass=[ javax.sql.XADataSource ], service.id=23 }
INFO: [Jun 29, 2006 5:54:18 PM] Service REGISTERED: { version=11.2.0, name=oracle11g, objectClass=[ java.sql.Driver ], service.id=24 }
INFO: [Jun 29, 2006 5:54:18 PM] Bundle oracle11g STARTED
...

Copy the bundler JAR to the Oracle CEP server library extensions directory.

Because your Oracle CEP application is an application library which contains a driver, you copy it to the Oracle CEP server library extensions directory is the DOMAIN_DIR/servername/modules/ext directory, where DOMAIN_DIR refers to the domain directory such as /oracle_cep/user_projects/domains/mydomain and servername refers to the server instance, such as myserver. For example:

c:\oracle_cep\user_projects\domains\mydomain\myserver\modules\ext

For more information, see "Library Extensions Directory" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

In the Oracle CEP server config.xml file, create a custom data-source element for your driver version and add a driver-params child element as Example 13-6 shows. For more information, see Section 1.3.1, "Oracle CEP Server Configuration Files".

Example 13-6 driver-params Child Element

    <driver-params>
      <url>jdbc:oracle:thin:@lcw2k18:1531:lcw101</url>
      <driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name
      <properties>
        <element>
          <name>user</name>
          <value>scott</value>
        </element>
        <element>
          <name>password</name>
          <value>{3DES}EoIfSBMhnW8=</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceName</name>
          <value>oracle11g</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceVersion</name>
          <value>11.2.0</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceObjectClass</name>
          <value>javax.sql.XADataSource</value>
        </element>
      </properties>
      <use-xa-data-source-interface>true</use-xa-data-source-interface>
    </driver-params>

Table 13-4 describes the relevant properties.

Table 13-3 driver-params Child Element Properties

Property
Description

com.bea.core.datasource.serviceName

Specifies the value of the serviceName registration property.

This must match the NAME property in your Activator class.

com.bea.core.datasource.serviceVersion

Specifies the value of the serviceVersion registration property.

This must match the VERSION property in your Activator class.

com.bea.core.datasource.serviceObjectClass

Specifies the interface name of the OSGI service registration.

For more information, see Section 13.2.2, "Custom Data Source Configuration".

Stop and start the Oracle CEP server.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

13.5.2 How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse

This procedure describes how to create an OSGi bundle for your driver using the Oracle CEP IDE for Eclipse and deploy it on the Oracle CEP server.

This is the preferred method. If do not wish to manually configure the activator implementation, see Section 13.5.1, "How to Access a Database Driver Using an Application Library Built With bundler.sh".

For more information, see "Creating Application Libraries" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

To access a database driver using an application library built with Oracle CEP IDE for Eclipse:

Using the Oracle CEP IDE for Eclipse, create a new Oracle CEP project.

For more information, see "Creating Oracle CEP Projects" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Right-click your project folder and select New > Folder.

Enter lib in the Folder name field and click Finish.

Outside of the Oracle CEP IDE for Eclipse, copy your JDBC JAR file into the lib folder.

Inside the Oracle CEP IDE for Eclipse, right-click the lib folder and select Refresh.

The JAR file appears in the lib folder as Figure 13-2 shows.

Figure 13-2 Oracle CEP IDE for Eclipse lib Directory

Right-click the src directory and select New > Class.

The Java Class dialog appears as Figure 13-3 shows.

Figure 13-3 New Java Class Dialog

Configure the New Java Class dialog as Table 13-4 shows.

Table 13-4 New Java Class Parameters

Parameter
Description

Package

The package name. For example, com.foo.

Name

The name of the class. For example, MyActivator.

Leave the other parameters at their default values.

Click Finish.

A new Java class is added to your project.

Edit the Java class to implement it as Example 13-7 shows.

Be sure to set the NAME and VERSION so that they supersede the existing version of JDBC driver. In this example, the existing version is:

oracle10g

10.0.0

To supersede the existing version, the MyActivator class sets these values to:

oracle11g

11.2.0

Example 13-7 MyActivator Class Implementation

package com.foo;

import java.util.Dictionary;
import java.util.Properties;

import javax.sql.XADataSource;
import java.sql.Driver;

import org.osgi.framework.BundleActivator;
import org.osgi.framework.BundleContext;
import org.osgi.framework.ServiceRegistration;

public class MyActivator implements BundleActivator {

  private static final String NAME="oracle11g";
  private static final String VERSION="11.2.0";

  private String[] factories = {"oracle.jdbc.xa.client.OracleXADataSource","oracle.jdbc.OracleDriver"};
  private String[] interfaces= {"javax.sql.XADataSource","java.sql.Driver"};
  private ServiceRegistration[] serviceRegistrations = new ServiceRegistration[factories.length];

  public void start(BundleContext bc) throws Exception {
    Dictionary props = new Properties();
    props.put("name", NAME);
    props.put("version", VERSION);
    for (int i=0; i<factories.length; i++) {
      Object svc = bc.getBundle().loadClass(factories[i]).newInstance();
      serviceRegistrations[i] = bc.registerService(interfaces[i], svc, props);
    }
  }

  public void stop(BundleContext bc) throws Exception {
    for (int i=0; i<serviceRegistrations.length; i++) {
      serviceRegistrations[i].unregister();
    }
  }
}

Right-click the META-INF/MANIFEST.MF file and select Open With > Plug-in Manifest Editor.

The Manifest Editor appears as Figure 13-4 shows.

Figure 13-4 Manifest Editor: Overview Tab

Click the Runtime tab.

The Runtime tab appears as Figure 13-5 shows.

Figure 13-5 Manifest Editor: Runtime Tab

In the Classpath pane, click Add.

The JAR Selection dialog appears as Figure 13-6 shows.

Figure 13-6 JAR Selection Dialog

Expand the lib directory and select your database driver JAR file.

Click OK.

Click the Dependencies tab.

The Dependencies tab appears as Figure 13-7 shows.

Figure 13-7 Manifest Editor: Dependencies Tab

In the Imported Packages pane, click Add.

The Package Selection dialog appears as Figure 13-8 shows.

Figure 13-8 Package Selection Dialog

In the Exported Packages field, enter org.osgi.framework.

The list box shows all the packages with that prefix as Figure 13-8 shows.

Select org.osgi.framework in the list box and click OK.

Click the MANIFEST.MF tab.

The MANIFEST.MF tab appears as Figure 13-9 shows.

Figure 13-9 Manifest Editor

Un-JAR your database driver JAR to a temporary directory as Example 13-8 shows.

Example 13-8 Un-JAR the Database Driver

$ pwd
/tmp
$ ls com.*
com.bea.oracle.ojdbc6_1.0.0.0_11-1-0-7.jar
$ mkdir driver
$ cd driver
$ jar -xvf ../com.bea.oracle.ojdbc6_1.0.0.0_11-1-0-7.jar
$ ls
META-INF  oracle
$ cd META-INF
$ ls
MANIFEST.MF  services

Open your database driver JAR MANIFEST.MF file and copy its Export-Package entry and paste it into the Manifest Editor as Example 13-9 shows.

Example 13-9 Adding Export-Package to the Manifest Editor

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %project.name
Bundle-SymbolicName: JDBCDriver
Bundle-Version: 1.0.0
Bundle-Localization: bundle
Bundle-Vendor: %project.vendor
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ClassPath: .
Import-Package: com.bea.wlevs.configuration;version="11.1.1.4_0", ...
Export-Package: oracle.core.lmx;version=1.0.0.0_11-1-0-7,oracle.core.l
 vf;version=1.0.0.0_11-1-0-7,oracle.jdbc;version=1.0.0.0_11-1-0-7,orac
 le.jdbc.aq;version=1.0.0.0_11-1-0-7,oracle.jdbc.connector;version=1.0
 .0.0_11-1-0-7,oracle.jdbc.dcn;version=1.0.0.0_11-1-0-7,oracle.jdbc.dr
 iver;version=1.0.0.0_11-1-0-7,oracle.jdbc.internal;version=1.0.0.0_11
 -1-0-7,oracle.jdbc.oci;version=1.0.0.0_11-1-0-7,oracle.jdbc.oracore;v
 ersion=1.0.0.0_11-1-0-7,oracle.jdbc.pool;version=1.0.0.0_11-1-0-7,ora
 cle.jdbc.rowset;version=1.0.0.0_11-1-0-7,oracle.jdbc.util;version=1.0
 .0.0_11-1-0-7,oracle.jdbc.xa;version=1.0.0.0_11-1-0-7,oracle.jdbc.xa.
 client;version=1.0.0.0_11-1-0-7,oracle.jpub.runtime;version=1.0.0.0_1
 1-1-0-7,oracle.net.ano;version=1.0.0.0_11-1-0-7,oracle.net.aso;versio
 n=1.0.0.0_11-1-0-7,oracle.net.jndi;version=1.0.0.0_11-1-0-7,oracle.ne
 t.ns;version=1.0.0.0_11-1-0-7,oracle.net.nt;version=1.0.0.0_11-1-0-7,
 oracle.net.resolver;version=1.0.0.0_11-1-0-7,oracle.security.o3logon;
 version=1.0.0.0_11-1-0-7,oracle.security.o5logon;version=1.0.0.0_11-1
 -0-7,oracle.sql;version=1.0.0.0_11-1-0-7,oracle.sql.converter;version
 =1.0.0.0_11-1-0-7

Add a Bundle-Activator element to the Manifest Editor as Example 13-10 shows.

The value of the Bundle-Activator is the fully qualified class name of your Activator class.

Example 13-10 Adding a Bundle-Activator Element to the Manifest Editor

Manifest-Version: 1.0
Bundle-Activator: com.foo.MyActivator
Bundle-ManifestVersion: 2
Bundle-Name: %project.name
Bundle-SymbolicName: JDBCDriver
Bundle-Version: 1.0.0
Bundle-Localization: bundle
Bundle-Vendor: %project.vendor
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ClassPath: .
Import-Package: com.bea.wlevs.configuration;version="11.1.1.4_0", ...
Export-Package: oracle.core.lmx;version=1.0.0.0_11-1-0-7, ...
...

Add a DynamicImport-Package element to the Manifest Editor as Example 13-11 shows.

Example 13-11 Adding a DynamicImport-Package Element to the Manifest Editor

Manifest-Version: 1.0
Bundle-Activator: com.foo.MyActivator
Bundle-ManifestVersion: 2
Bundle-Name: %project.name
Bundle-SymbolicName: JDBCDriver
Bundle-Version: 1.0.0
Bundle-Localization: bundle
Bundle-Vendor: %project.vendor
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ClassPath: .
DynamicImport-Package: *
Import-Package: com.bea.wlevs.configuration;version="11.1.1.4_0", ...
Export-Package: oracle.core.lmx;version=1.0.0.0_11-1-0-7, ...
...

Export your Oracle CEP application to a JAR file.

For more information, see "How to Export an Oracle CEP Project" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Because your Oracle CEP application is an application library which contains a driver, you will copy your exported JAR to the Oracle CEP server library extensions directory.

The Oracle CEP server library extensions directory is the DOMAIN_DIR/servername/modules/ext directory, where DOMAIN_DIR refers to the domain directory such as /oracle_cep/user_projects/domains/mydomain and servername refers to the server instance, such as myserver. For example:

c:\oracle_cep\user_projects\domains\mydomain\myserver\modules\ext

In the Oracle CEP server config.xml file, create a custom data-source element for your driver version and add a driver-params child element as Example 13-12 shows. For more information, see Section 1.3.1, "Oracle CEP Server Configuration Files".

Example 13-12 driver-params Child Element

    <driver-params>
      <url>jdbc:oracle:thin:@lcw2k18:1531:lcw101</url>
      <driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name
      <properties>
        <element>
          <name>user</name>
          <value>scott</value>
        </element>
        <element>
          <name>password</name>
          <value>{3DES}EoIfSBMhnW8=</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceName</name>
          <value>oracle11g</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceVersion</name>
          <value>11.2.0</value>
        </element>
        <element>
          <name>com.bea.core.datasource.serviceObjectClass</name>
          <value>javax.sql.XADataSource</value>
        </element>
      </properties>
      <use-xa-data-source-interface>true</use-xa-data-source-interface>
    </driver-params>

Table 13-5 describes the relevant properties.

Table 13-5 driver-params Child Element Properties

Property
Description

com.bea.core.datasource.serviceName

Specifies the value of the serviceName registration property.

This must match the NAME property in your Activator class.

com.bea.core.datasource.serviceVersion

Specifies the value of the serviceVersion registration property.

This must match the VERSION property in your Activator class.

com.bea.core.datasource.serviceObjectClass

Specifies the interface name of the OSGI service registration.

For more information, see Section 13.2.2, "Custom Data Source Configuration".

Stop and start the Oracle CEP server.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

13.5.3 How to Access a Database Driver Using bootclasspath

Optionally, you can use the bootclasspath to access your own JDBC driver with Oracle CEP.

Oracle recommends that you use an application library instead, as Section 13.5.1, "How to Access a Database Driver Using an Application Library Built With bundler.sh" or Section 13.5.2, "How to Access a Database Driver Using an Application Library Built With Oracle CEP IDE for Eclipse" describes.

To access a database driver using bootclasspath:

Update the server start script in the server directory of your domain directory so that Oracle CEP finds the appropriate JDBC driver JAR file when it boots up.

The name of the server start script is startwlevs.cmd (Windows) or startwlevs.sh (UNIX), and the script is located in the server directory of your domain directory. The out-of-the-box sample domains are located in ORACLE_CEP_HOME/ocep_11.1/samples/domains, and the user domains are located in ORACLE_CEP_HOME/user_projects/domains, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory, such as d:\oracle_cep.

Update the start script by adding the -Xbootclasspath/a option to the Java command that executes the wlevs_3.0.jar file. Set the -Xbootclasspath/a option to the full pathname of the JDBC driver you are going to use.

For example, if you want to use the Windows Oracle thin driver, update the java command in the start script as follows -- the updated section is shown in bold (split for readability; in practice, the command should be on one line):

%JAVA_HOME%\bin\java -Dwlevs.home=%USER_INSTALL_DIR% -Dbea.home=%BEA_HOME%
-Xbootclasspath/a:%USER_INSTALL_DIR%\bin\com.bea.oracle.ojdbc14_10.2.0.jar
-jar "%USER_INSTALL_DIR%\bin\wlevs_3.0.jar" -disablesecurity %1 %2 %3 %4 %5 %6

In the example, %USER_INSTALL_DIR% points to ORACLE_CEP_HOME\ocep_11.1.

Configure the data source in the server's config.xml file:

To update the Oracle CEP server config.xml file using the Configuration Wizard, see "Creating and Updating Oracle CEP Standalone-Server Domains" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing.

To update the Oracle CEP server config.xml file manually, see Section 13.2.2, "Custom Data Source Configuration."

If Oracle CEP is running, restart it so it reads the new java option and data source information.

For more information, see Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

14 Configuring HTTP Publish-Subscribe for Oracle CEP

This chapter describes how to configure HTTP publish-subscribe (based on the Bayeux protocol) for use with Oracle Complex Event Processing (Oracle CEP), including how to create and configure an HTTP publish-subscribe server and an example configuration.

Section 14.1, "Overview of HTTP Publish-Subscribe"

Section 14.2, "Creating a New HTTP Publish-Subscribe Server"

Section 14.3, "Configuring an Existing HTTP Publish-Subscribe Server"

Section 14.4, "Example HTTP Publish-Subscribe Server Configuration"

14.1 Overview of HTTP Publish-Subscribe

An HTTP Publish-Subscribe Server (HTTP pub-sub server) is a mechanism whereby Web clients subscribe to channels and then publish messages to these channels using asynchronous messages over HTTP.

The simple request/response nature of a standard Web application requires that all communication be initiated by the client; this means that the server can only push updated data to its clients if it receives an explicit request. This mechanism is adequate for traditional applications in which data from the server is required only when a client requests it, but inadequate for dynamic real-time applications in which the server must send data even if a client has not explicitly requested it. The client can use the traditional HTTP pull approach to check and retrieve the latest data at regular intervals, but this approach is lacking in scalability and leads to high network traffic because of redundant checks. The HTTP Publish-Subscribe Server solves this problem by allowing clients to subscribe to a channel (similar to a topic in JMS) and receive messages as they become available.

The HTTP pub-sub server is based on the Bayeux protocol proposed by the cometd project. The Bayeux protocol defines a contract between the client and the server for communicating with asynchronous messages over HTTP. It allows clients to register and subscribe to channels, which are named destinations or sources of events. Registered clients, or the HTTP pub-sub server itself, then publishes messages to these channels which in turn any subscribed clients receive.

The HTTP pub-sub server can communicate with any client that can understand the Bayeux protocol. The HTTP pub-sub server is responsible for identifying clients, negotiating trust, exchanging Bayeux messages, and, most importantly, pushing event messages to subscribed clients.

Figure 14-1 describes the basic architecture of the HTTP pub-sub server included in Oracle CEP.

Figure 14-1 HTTP Publish-Subscribe Server in Oracle CEP

14.1.1 How the HTTP Pub-Sub Server Works

There is a one-to-one relationship between a servlet and an HTTP pub-sub server; in other words, each servlet has access to one unique HTTP pub-sub server. Each HTTP pub-sub server has its own list of channels. The servlet uses a context object to get a handle to its associated HTTP pub-sub server.

In Oracle CEP, HTTP pub-sub server instances are configured in the config.xml file of the server instance. System administrator uses the config.xml to configure the name of the HTTP pub-sub server, specify the transport and other parameters. You then use Oracle CEP Visualizer to add new channels and configure security for the channels.

Oracle CEP application developers can optionally use the built-in HTTP pub-sub adapters to publish and subscribe to channels within their applications. If, however, developers need the HTTP pub-sub server to perform additional steps, such as monitoring, collecting, or interpreting incoming messages from clients, then they must use the server-side HTTP pub-sub server APIs to program this functionality.

For Web 2.0 Ajax clients (such as Dojo) or rich internet applications (such as Adobe Flex) to communicate with the HTTP pub-sub server, the clients need a library that supports the Bayeux protocol. The Dojo JavaScript library provides four different transports, of which two are supported by the HTTP pub-sub server: long-polling and callback-polling.

14.1.2 HTTP Pub-Sub Server Support in Oracle CEP

Every Oracle CEP server includes a default HTTP pub-sub server. This server is used internally by Oracle CEP Visualizer and by the Record and Playback example. You can either use the default HTTP pub-sub server for your own Web 2.0 application or create a new one.

The default HTTP pub-sub server has the following properties:

HTTP pub-sub server URL— http://host:port/pubsub, where host and port refer to the computer on which Oracle CEP is running and the port number to which it listens, respectively.

Transport: Uses long-polling transport.

Allows clients to publish messages to a channel without having explicitly connected to the HTTP pub-sub server.

Includes the following three channels used internally by Oracle CEP Visualizer; do not delete these channels:

/evsmonitor

/evsalert/

/evsdomainchange

For details about configuring the default HTTP pub-sub server, or creating a new one, see:

Section 14.2, "Creating a New HTTP Publish-Subscribe Server"

Section 14.3, "Configuring an Existing HTTP Publish-Subscribe Server."

Section 14.4, "Example HTTP Publish-Subscribe Server Configuration."

Oracle CEP also includes two built-in adapters that easily harness HTTP pub-sub server functionality in your applications. By adding these adapters to your application you can both publish messages or subscribe to a server to receive messages, using either the local HTTP pub-sub server or a remote one.

For more information, see "Using and Creating HTTP Publish-Subscribe Adapters" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

14.2 Creating a New HTTP Publish-Subscribe Server

The following procedure describes how to create a new HTTP pub-sub server. See Section 14.4, "Example HTTP Publish-Subscribe Server Configuration" for a full example from the config.xml of a configured HTTP pub-sub server.

To create a new HTTP publish-subscribe server:

If the Oracle CEP server is running, stop it.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Using your favorite XML editor, open the Oracle CEP server's config.xml file.

This file is located in the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the domain directory and servername refers to the name of the server, such as /oracle_cep/user_projects/myDomain/defaultserver/config.

Add an http-pubsub child element of the root config element of config.xml, with name, path and pub-sub-bean child elements, as shown in bold:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:config xmlns:ns2="http://www.bea.com/ns/wlevs/config/server">
    <domain>
        <name>myDomain</name>
    </domain>
    ....
    <http-pubsub>
      <name>myPubSubServer</name>
      <path>/myPath</path>
      <pub-sub-bean>
         ...
      </pub-sub-bean>
    </http-pubsub>
    ...
</ns2:config>

Set the name element to the internal name of the HTTP pub-sub server.

Set the path element to the string that you want to appear in the URL for connecting to the HTTP pub-sub server.

The next step describes the pub-sub-bean element.

Add server-config and channels child elements of the pub-sub-bean element:

    <http-pubsub>
      <name>myPubSubServer</name>
      <path>/myPath</path>
      <pub-sub-bean>
        <server-config>
           ...
        </server-config>
        <channels>
           ...
        </channels>
      </pub-sub-bean>
    </http-pubsub>

Update the server-config child element of the pub-sub-bean element with HTTP pub-sub server configuration as required.

For the full list of possible elements, see "Server Configuration XSD Schema: wlevs_server_config.xsd" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

The following are the most common configuration options:

Add a supported-transport element to specify the transport.

The format of this element is as follows:

<server-config>
    <supported-transport>
        <types>
            <element>long-polling</element>
        </types>
    </supported-transport>
...
</server-config>

Oracle CEP server supports the following transports:

long-polling: Using this transport, the client requests information from Oracle CEP server and if Oracle CEP server does not have information available, it does not reply until it has. When the Oracle CEP server replies, the client typically sends another request immediately.

callback-polling: Use this transport for HTTP publish-subscribe applications using a cross domain configuration in which the browser downloads the page from one Web server (including the JavaScript code) and connects to another server as an HTTP publish-subscribe client. This is required by the Bayeux protocol. For more information on the Bayeux protocol, see http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html.

Add a publish-without-connect-allowed element to specify whether clients can publish messages without having explicitly connected to the HTTP pub-sub server; valid values are true or false:

<server-config>
...
    <publish-without-connect-allowed>true</publish-without-connect-allowed>
</server-config>

Add a work-manager element to specify the name of the work manager that delivers messages to clients. The value of this element corresponds to the value of the <name> child element of the work-manager you want to assign.

<server-config>
...
    <work-manager>myWorkManager</work-manager>
</server-config>

For more information, see "work-manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Add a client-timeout-secs element to specify the number of seconds after which the HTTP pub-sub server disconnects a client if the client does has not sent back a connect/reconnect message.

<server-config>
...
    <client-timeout-secs>600</client-timeout-secs>
</server-config>

Update the channels child element with at least one channel pattern.

Channel patterns always begin with a forward slash (/). Clients subscribe to these channels to either publish or receive messages. Add a channel pattern as shown:

<channels>
    <element>
        <channel-pattern>/mychannel</channel-pattern>
    </element>
</channels>

Save the config.xml file.

Start the Oracle CEP server.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Use Oracle CEP Visualizer to configure or add channels. See:

"Configuring HTTP Publish-Subscribe Server Channels" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Use Oracle CEP Visualizer to configure security for the channels. See:

"Configuring Security for the HTTP Publish-Subscribe Channels" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Section 10.8.4, "Configuring HTTP Publish-Subscribe Server Channel Security"

14.3 Configuring an Existing HTTP Publish-Subscribe Server

The following procedure describes how to configure an existing HTTP pub-sub server. See Section 14.4, "Example HTTP Publish-Subscribe Server Configuration" for a full example from the config.xml of a configured HTTP pub-sub server.

To configure an existing HTTP publish-subscribe server:

If the Oracle CEP server is running, stop it.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Using your favorite XML editor, open the Oracle CEP server's config.xml file.

This file is located in the DOMAIN_DIR/servername/config directory, where DOMAIN_DIR refers to the domain directory and servername refers to the name of the server, such as /oracle_cep/user_projects/myDomain/defaultserver/config.

Search for the http-pubsub element that corresponds to the HTTP pub-sub server you want to configure. For example, the default HTTP pub-sub server is as follows:

<http-pubsub>
    <name>pubsub</name>
    <path>/pubsub</path>
    <pub-sub-bean>
        <server-config>
        ...
</http-pubsub>

Update the server-config child element of the pub-sub-bean element (which in turn is a child element of http-pubsub) with HTTP pub-sub server configuration as required.

For the full list of possible elements, see "Server Configuration XSD Schema: wlevs_server_config.xsd" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

The following are the most common configuration options:

Add a supported-transport element to specify the transport.

The format of this element is as follows:

<server-config>
    <supported-transport>
        <types>
            <element>long-polling</element>
        </types>
    </supported-transport>
...
</server-config>

Oracle CEP server supports the following transports:

long-polling: Using this transport, the client requests information from Oracle CEP server and if Oracle CEP server does not have information available, it does not reply until it has. When the Oracle CEP server replies, the client typically sends another request immediately.

callback-polling: Use this transport for HTTP publish-subscribe applications using a cross domain configuration in which the browser downloads the page from one Web server (including the JavaScript code) and connects to another server as an HTTP publish-subscribe client. This is required by the Bayeux protocol. For more information on the Bayeux protocol, see http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html.

Add a publish-without-connect-allowed element to specify whether clients can publish messages without having explicitly connected to the HTTP pub-sub server; valid values are true or false:

<server-config>
...
    <publish-without-connect-allowed>true</publish-without-connect-allowed>
</server-config>

Add a work-manager element to specify the name of the work manager that delivers messages to clients. The value of this element corresponds to the value of the name child element of the work-manager you want to assign.

<server-config>
...
    <work-manager>myWorkManager</work-manager>
</server-config>

For more information, see "work-manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Add a client-timeout-secs element to specify the number of seconds after which the HTTP pub-sub server disconnects a client if the client does has not sent back a connect/reconnect message.

<server-config>
...
    <client-timeout-secs>600</client-timeout-secs>
</server-config>

Save the config.xml file.

Start the Oracle CEP server.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Use Oracle CEP Visualizer to configure or add channels. See:

"Configuring HTTP Publish-Subscribe Server Channels" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Use Oracle CEP Visualizer to configure security for the channels. See:

"Configuring Security for the HTTP Publish-Subscribe Channels" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing

Section 10.8.4, "Configuring HTTP Publish-Subscribe Server Channel Security"

14.4 Example HTTP Publish-Subscribe Server Configuration

The following snippet of the config.xml file shows the configuration of the default HTTP pub-sub server present in every Oracle CEP server:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:config xmlns:ns2="http://www.bea.com/ns/wlevs/config/server">
    <domain>
        <name>myDomain</name>
    </domain>
    ....
    <http-pubsub>
        <name>pubsub</name>
        <path>/pubsub</path>
        <pub-sub-bean>
            <server-config>
                <supported-transport>
                    <types>
                    <element>long-polling</element>
                    </types>
                </supported-transport>
                <publish-without-connect-allowed>true</publish-without-connect-allowed>
            </server-config>
            <channels>
                <element>
                    <channel-pattern>/evsmonitor</channel-pattern>
                </element>
                <element>
                    <channel-pattern>/evsalert</channel-pattern>
               </element>
                <element>
                    <channel-pattern>/evsdomainchange</channel-pattern>
                </element>
            </channels>
        </pub-sub-bean>
    </http-pubsub>
...
</ns2:config>

15 Configuring Logging and Debugging for Oracle CEP

This chapter describes how to configure logging and debugging for Oracle Complex Event Processing (Oracle CEP), including using the Oracle CEP logging service, Log4j, the and Apache Commons logging API, as well as configuring debugging options.

Section 15.1, "Overview of Logging and Debugging Configuration"

Section 15.2, "Configuring the Oracle CEP Logging Service"

Section 15.3, "Configuring Log4j Logging"

Section 15.4, "Using the Apache Commons Logging API"

Section 15.5, "Configuring Oracle CEP Debugging Options"

15.1 Overview of Logging and Debugging Configuration

System administrators and developers configure logging output and filter log messages to troubleshoot errors or to receive notification for specific events.

The following tasks describe some logging configuration scenarios:

Stop DEBUG and INFO messages from going to the log file.

Allow INFO level messages from the HTTP subsystem to be published to the log file, but not to standard out.

Specify that a handler publishes messages that are WARNING severity level or higher.

Specify a default logging level for the entire Oracle CEP server, and then have a specific Oracle CEP module override the default logging level. For example, the default logging level of the server could be WARNING while the logging level of the CEP module is DEBUG.

Configure a logging level for a user-application deployed to Oracle CEP. In this case, the application must use the Commons Apache Logging Framework if the application is required to output log messages into the single server-wide log file to which the modules of the server itself also log their messages.

Oracle CEP supports the following logging systems:

Section 15.1.1, "Commons Apache Logging Framework"

Section 15.1.2, "OSGi Framework Logger"

Section 15.1.3, "Log4j Logger"

Oracle CEP also provides a variety of debugging options that you can enable and disable to help diagnose your Oracle CEP applications. See Section 15.5, "Configuring Oracle CEP Debugging Options".

Note:

For information on Oracle CEP security auditor logging, see Section 10.10, "Configuring the Oracle CEP Security Auditor".

Note:

For information how to parse message catalogs to validate and generate classes used for localizing text in log messages, see "Managing Log Message Catalogs" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

15.1.1 Commons Apache Logging Framework

Oracle CEP provides a commons-logging interface. The interface provides commons.logging.LogFactory and Log interface implementations. It includes an extension of the org.apache.commons.logging.LogFactory class that acts as a factory to create an implementation of the org.apache.commons.logging.Log that delegates to the LoggingService in the logging module. The name of this default implementation is weblogic.logging.commons.LogFactoryImpl.

This section describes the following:

Section 15.1.1.1, "Setting the Log Factory"

Section 15.1.1.2, "Using Log Severity Levels"

Section 15.1.1.3, "Log Files"

Section 15.1.1.4, "Log Message Format"

Section 15.1.2, "OSGi Framework Logger"

For more information, see http://jakarta.apache.org/commons/logging/apidocs/index.html.

15.1.1.1 Setting the Log Factory

The following provides information on setting the log factory using system properties:

The highest priority is given to the system property org.apache.commons.logging.LogFactory.

You can set logging from the command line using:

-Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl

You can programmatically implement the logging by:

import org.apache.commons.logging.LogFactory;
System.setProperty(
    LogFactory.FACTORY_PROPERTY,
    "weblogic.logging.commons.LogFactoryImpl"
);

The weblogic.logging.commons.LogFactoryImpl is the default log factory, if not explicitly set.

To use another logging implementation, you must use the standard commons logging factory implementation. The org.apache.commons.logging.impl.LogFactoryImpl implementation is available in the commons logging jar. For example:

-Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl

or the equivalent programming would be:

System.setProperty(
    LogFactory.FACTORY_PROPERTY,
    "org.apache.commons.logging.impl.LogFactoryImpl"
);

15.1.1.2 Using Log Severity Levels

Each log message has an associated severity level. The level gives a rough guide to the importance and urgency of a log message. Predefined severities, ranging from TRACE to EMERGENCY, are converted to a log level when dispatching a log request to the logger. A log level object can specify any of the following values, from lowest (left-most) to highest (right-most) impact:

TRACE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY

You can set a log severity level on the logger, the handler, and a user application. When set on the logger, none of the handlers receive an event which is rejected by the logger. For example, if you set the log level to NOTICE on the logger, none of the handlers will receive INFO level events. When you set a log level on the handler, the restriction only applies to that handler and not the others. For example, turning DEBUG off for the File Handler means no DEBUG messages will be written to the log file, however, DEBUG messages will be written to standard out.

Users (Oracle CEP module owners or owners of user applications) are free to define the names that represent the logging category type used by the Apache commons logging for individual modules. However if the category names are defined as package names then based on the naming convention, a logging level hierarchy is assumed by default. For example, if two modules name their logging category names com.oracle.foo and com.oracle.foo.bar, then com.oracle.foo becomes the root node of com.oracle.foo.bar. This way any logging level applied to parent node (com.oracle.foo) automatically applies to com.oracle.foo.bar, unless the child node overrides the parent.

In other words, if the logging severity is specified for a node, it is effective unless the severity is inherited from the nearest parent whose severity is explicitly configured. The root node is always explicitly configured, so if nothing else if set, then all the nodes inherit the severity from the root.

Table 15-1 lists the severity levels of log messages.

Table 15-1 Log Message Severity

Severity
Meaning

TRACE

Used for messages from the Diagnostic Action Library. Upon enabling diagnostic instrumentation of server and application classes, TRACE messages follow the request path of a method.

DEBUG

A debug message was generated.

INFO

Used for reporting normal operations, a low-level informational message.

NOTICE

An informational message with a higher level of importance.

WARNING

A suspicious operation or configuration has occurred but it might not affect normal operation.

ERROR

A user error has occurred. The system or application can handle the error with no interruption and limited degradation of service.

CRITICAL

A system or service error has occurred. The system can recover but there might be a momentary loss or permanent degradation of service.

ALERT

A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem.

EMERGENCY

The server is in an unusable state. This severity indicates a severe system failure or panic.

The system generates many messages of lower severity and fewer messages of higher severity. For example, under normal circumstances, they generate many INFO messages and no EMERGENCY messages.

15.1.1.3 Log Files

By default, Oracle CEP server writes log messages to the server.log and consoleoutput.log files in the ORACLE_CEP_HOME/user_projects/domains/DOMAIN_DIR/servername directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep), DOMAIN_DIR refers to the domain directory (such as my_domain), and servername refers to the server instance directory (such as server1).

For information on configuring log file attributes, see Section 15.2.2, "log-file".

For information on server.log file message format, see Section 15.1.1.4.1, "Format of Output to a Log File".

For information on consoleoutput.log file message format, see Section 15.1.1.4.2, "Format of Output to Console, Standard Out, and Standard Error".

15.1.1.4 Log Message Format

Oracle CEP server writes log messages in different formats depending on the type of log file it is writing to:

Section 15.1.1.4.1, "Format of Output to a Log File"

Section 15.1.1.4.2, "Format of Output to Console, Standard Out, and Standard Error"

For more information on log files, see Section 15.1.1.3, "Log Files".

15.1.1.4.1 Format of Output to a Log File

The system writes a message to the specified log file consisting of a #### prefix, Timestamp, Severity, Subsystem, Server Name, Connection, Thread ID or User ID or Transaction ID, Message ID, and the Message, along with a stacktrace if any. Each attribute is contained between angle brackets.

The following is an example of a message in the server log file (split for readability; in practice, the message might be on one line):

####<Feb 25, 2009 10:23:32 AM EST> <Notice> <Deployment> <> <myServer>
<RMI TCP Connection(4)-141.144.123.236> <> <> <> <1235575412801> <BEA-2045000>
<The application bundle "Hello" was deployed successfully to file
[C:\OracleCEP\user_projects\domains\ocep_domain\defaultserver\applications\Hello\Hello.jar]
with version 1235575412708>

15.1.1.4.2 Format of Output to Console, Standard Out, and Standard Error

The system writes a message to the console, standard out, or standard error consisting of Locale-formatted Timestamp, Severity, Subsystem, Message ID, and Message.

The following is an example of how the message from the previous section would be printed to standard out (split for readability; in practice, the message might be on one line):

<Feb 25, 2009 10:23:32 AM EST> <Notice> <Deployment> <BEA-2045000>
<The application bundle "Hello" was deployed successfully to file
[C:\OracleCEP\user_projects\domains\ocep_domain\defaultserver\applications\Hello\Hello.jar]
with version 1235575412708>

15.1.2 OSGi Framework Logger

Oracle CEP has a low-level framework logger that is started before the OSGi framework. It is used to report logging event deep inside the OSGi framework and function as a custom default for the logging subsystem before it is configured.

For example, a user may see some log message, which has lower level or severity than what is set in the config.xml but higher or equal to what is set on the Launcher command line on the console or in the log file. Until the logging subsystem has started, log messages come from the framework logger and use the framework logging level to filter messages.

15.1.3 Log4j Logger

Log4j is an open source tool developed for putting log statements in your application. Log4j has three main components:

Section 15.1.3.1, "Loggers"

Section 15.1.3.2, "Appenders"

Section 15.1.3.3, "Layouts"

The Log4j Java logging facility was developed by the Jakarta Project of the Apache Foundation. See:

The Log4j Project at http://logging.apache.org/log4j/.

The Log4j API at http://logging.apache.org/log4j/docs/api/index.html.

Short introduction to log4j at http://logging.apache.org/log4j/1.2/manual.html.

For more information, see Section 15.3, "Configuring Log4j Logging"

15.1.3.1 Loggers

Log4j defines a Logger class. An application can create multiple loggers, each with a unique name. In a typical usage of Log4j, an application creates a Logger instance for each application class that will emit log messages. Loggers exist in a namespace hierarchy and inherit behavior from their ancestors in the hierarchy.

15.1.3.2 Appenders

Log4j defines appenders (handlers) to represent destinations for logging output. Multiple appenders can be defined. For example, an application might define an appender that sends log messages to standard out, and another appender that writes log messages to a file. Individual loggers might be configured to write to zero or more appenders. One example usage would be to send all logging messages (all levels) to a log file, but only ERROR level messages to standard out.

15.1.3.3 Layouts

Log4j defines layouts to control the format of log messages. Each layout specifies a particular message format. A specific layout is associated with each appender. This lets you specify a different log message format for standard out than for file output, for example.

15.2 Configuring the Oracle CEP Logging Service

You configure Oracle CEP logging service attributes using Oracle CEP Visualizer or by editing the Oracle CEP server config.xml file.

For more information on configuring logging using Oracle CEP Visualizer, see "Managing Logs" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

The config.xml file is located in the ORACLE_CEP_HOME/user_projects/domains/DOMAIN_DIR/servername/config directory, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep), DOMAIN_DIR refers to the domain directory (such as my_domain), and servername refers to the server instance directory (such as server1).

Example 15-1 shows a typical Oracle CEP server config.xml file with logging elements.

Example 15-1 Oracle CEP Server config.xml File With Logging Configuration

<?xml version="1.0" encoding="UTF-8"?>
<!--Sample XML file generated by XMLSpy v2007 sp2 (http://www.altova.com)-->
<n1:config
    xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd"
    xmlns:n1="http://www.bea.com/ns/wlevs/config/server"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
...
        <name>myLogService</name>
        <log-file-config>myFileConfig</log-file-config>
        <stdout-config>myStdoutConfig</stdout-config>
        <logger-severity>Notice</logger-severity>
        <logger-severity-properties>
            <entry>
                <key>LifeCycle</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Management</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>CQLProcessor</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>EplProcessor</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Stream</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Ede</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Cache</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Adapters</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Spring</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Channel</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Recplay</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Monitor</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Server</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>EventTrace</key>
                <value>Notice</value>
            </entry>
            <entry>
                <key>Deployment</key>
                <value>Notice</value>
            </entry>
        </logger-severity-properties>
    </logging-service>
    <log-file>
        <name>myFileConfig</name>
        <rotation-type>none</rotation-type>
    </log-file>
    <log-stdout>
        <name>myStdoutConfig</name>
        <stdout-severity>Debug</stdout-severity>
    </log-stdout>

</n1:config>

The following sections provide information on configuring Oracle CEP logging:

Section 15.2.1, "logging-service"

Section 15.2.2, "log-file"

Section 15.2.3, "log-stdout"

Section 15.2.4, "Configuring Severity for an Individual Module"

15.2.1 logging-service

This section provides information on the logging-service element:

Table 15-2 Configuration Parameters for logging-service

Parameter
Type
Description

name

String

The name of this configuration object.

log-file-config

String

The configuration of the log file and its rotation policies.

See Section 15.2.2, "log-file."

stdout-config

String

The name of the stdout configuration object used to configure stdout output. See Section 15.2.3, "log-stdout."

logger-severity

String

Defines the threshold importance of the messages that are propagated to the handlers.

The default value is Info.

To see Debug and Trace messages, configure the logger-severity to either Debug or Trace.

Valid values are: Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug, and Trace.

logger-severity-properties

One or more <entry> child elements.

List of name-value pairs, enclosed in an <entry> element, that list individual modules (package name, application name, class name, or component such as CQLProcessor) and their logging severity. These severities override the default severity of the Oracle CEP server.

See Section 15.2.4, "Configuring Severity for an Individual Module."

15.2.2 log-file

This section provides information on the log-file element:

Table 15-3 Configuration Parameters for log-file

Parameter
Type
Description

name

String

The name of this configuration object.

base-log-file-name

String

The log file name. Default value is server.log.

log-file-severity

String

Specifies the least important severity of messages written to the log file. Default value is Trace.

Valid values are:

Emergency

Alert

Critical

Error

Warning

Notice

Info

Debug

Trace

log-file-rotation-dir

String

Specifies the directory where old rotated files are stored.

If not set, the old files are stored in the same directory as the base log file.

rotation-type

String

Specifies how rotation is performed based on size, time, or not at all.

Valid values are:

bySize

byTime

none

rotation-time

String

The time in k:mm format, where k is the hour specified in 24 hour notation and mm is the minutes.

Default is 00:00

rotation-time-span-factor

Long

Factor applied to the timespan to determine the number of milliseconds that becomes the frequency of time based log rotations. Default is 3600000.

rotated-file-count

Integer

Specifies the number of old rotated files to keep if number-of-files-limited is true. Default value is 7.

rotation-size

Integer

The size threshold, in KB, at which the log file is rotated. Default is 500.

rotation-time-span

Integer

Specifies the interval for every time-based log rotation. Default value is 24.

rotate-log-on-startup-enabled

Boolean

If true, the log file is rotated on startup. Default value is true.

number-of-files-limited

Boolean

If true, old rotated files are deleted. Default is false.

15.2.3 log-stdout

This section provides information on the log-stdout element:

Table 15-4 Configuration Parameters for log-stdout

Parameter
Type
Description

name

String

The name of this configuration object.

stdout-severity

String

The threshold severity for messages sent to stdout. Default value is Notice.

Valid values are:

Emergency

Alert

Critical

Error

Warning

Notice

Info

Debug

Trace

stack-trace-depth

Integer

The number of stack trace frames to display on stdout.

A default value of -1 means all frames are displayed.

stack-trace-enabled

Boolean

If true, stack traces are dumped to the console when included in logged messages. Default value is true.

15.2.4 Configuring Severity for an Individual Module

Individual modules of Oracle CEP can specify their logging severity. This severity overrides the default logging severity of Oracle CEP server.

You do this by specifying an entry child element in the logger-severity-properties element in the Oracle CEP server config.xml file. You may specify multiple entry child elements for any number of modules.

To configure severity for an individual module:

Edit the Oracle CEP server config.xml file.

Add an entry child element to the logger-severity-properties element as Example 15-2 shows.

Example 15-2 entry Child Element of the logger-severity-properties Element

  <logging-service>
    <name>myLogService</name>
    <logger-severity>Warning</logger-severity>
    <logger-severity-properties>
    ...
        <entry>
            <key>CQLProcessor</key>
            <value>Debug</value>
        </entry>
    ...
    </logger-severity-properties>
    ...
  </logging-service>

Set the key element to any of the following:

Component name: a component name constant exactly as Table 15-5 lists.

Table 15-5 Logging Component Name Constants

Component Name Constant
Description

Adapters

Applies to log messages from adapter instances running on the Oracle CEP server.

Cache

Applies to log messages from caching systems and cache instances running on the Oracle CEP server.

Channel

Applies to log messages from channels running on the Oracle CEP server.

CQLProcessor

Applies to log messages from Oracle CQL processors running on the Oracle CEP server.

CQLServer

Applies to log messages from the CQLEngine, which is at the core of each CQLProcessor.

CQLServerTrace

Applies to log messages from the CQLEngine, which is at the core of each CQLProcessor

EplProcessor

Applies to log messages from EPL processors running on the Oracle CEP server.

Ede

Applies to log messages from the Event-Driven Environment, the Oracle CEP server event-dispatching infrastructure.

EventTrace

When set to Info or Debug, allows you to trace events as they flow through the EPN for all applications. You can dynamically change the severity of this log key using Oracle CEP Visualizer.

At the Info severity, you see log messages like:

<May 26, 2009 5:53:49 PM PDT> <Info> <EventTrace>
    <BEA-000000> <Application [helloworld],
    Stage [helloworldOutputChannel] received insert event>

At the Debug severity, the log messages include details of the event:

<May 26, 2009 6:02:34 PM PDT> <Debug> <EventTrace>
    <BEA-000000> <Application [helloworld],
    Stage [helloworldOutputChannel] received insert
    event [HelloWorldEvent: HelloWorld - the current
    time is: 6:02:34 PM]>

Lifecycle

Applies to log messages from Oracle CEP server and application lifecycle operations.

Management

Applies to log messages from Oracle CEP server general JMX-related management API operations.

Monitor

Applies to log messages from the Oracle CEP server monitoring service.

Recplay

Applies to log messages from Oracle CEP server event recording and playback operations.

Spring

Applies to log messages from Spring container operations.

Stream

Applies to log messages from stream instances running on the Oracle CEP server.

For example:

<entry>
    <key>CQLProcessor</key>
    <value>Debug</value>
</entry>

Application name: the module name of any Oracle CEP server or user-defined application. For example:

<entry>
    <key>sample.HelloWorld</key>
    <value>Debug</value>
</entry>

Package name: the name of any Oracle CEP server or user-supplied Java package. For example:

<entry>
    <key>com.bea.wlevs.ede</key>
    <value>Debug</value>
</entry>

For more information on Oracle CEP server packages, see the Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing.

Class name: the fully qualified name of any Oracle CEP server or user-defined class. For example:

<entry>
    <key>com.bea.wlevs.cep.core.EPRuntimeImpl</key>
    <value>Debug</value>
</entry>

For more information on Oracle CEP server classes, see the Oracle Fusion Middleware Java API Reference for Oracle Complex Event Processing.

Set the value element to a severity level.

See Section 15.1.1.2, "Using Log Severity Levels".

For example:

<entry>
    <key>CQLProcessor</key>
    <value>Debug</value>
</entry>

This severity level applies to the module you specified in the key element and overrides the default Oracle CEP server logging severity level set in the logger-severity element that Example 15-2 shows.

Repeat from step 2 for any other modules.

Save and close the config.xml file.

15.3 Configuring Log4j Logging

Oracle CEP supports the open-source log4j logging system.

This section describes the following tasks:

Section 15.3.1, "Configuring log4j Properties"

Section 15.3.2, "Configuring Application Manifest"

Section 15.3.3, "Enabling Log4j Logging"

Section 15.3.4, "Debugging Log4j Logging"

For more information, see Section 15.1.3, "Log4j Logger".

15.3.1 Configuring log4j Properties

The default configuration file is log4j.properties. It can be overridden by using the log4j.configuration system property. See https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp.

The following is an example of a log4j.properties file:

Example 15-3 Example log4j.properties File

   log4j.rootLogger=debug, R
   log4j.appender.R=org.apache.log4j.RollingFileAppender
   log4j.appender.R.File=D:/log4j/logs/mywebapp.log
   log4j.appender.R.MaxFileSize=10MB
   log4j.appender.R.MaxBackupIndex=10
   log4j.appender.R.layout=org.apache.log4j.PatternLayout
   log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
   log4j.logger=DEBUG, R

15.3.2 Configuring Application Manifest

Update the MANIFEST.MF file of your application to import the following required Log4j packages.

Import-Package:
    org.apache.log4j;version="1.2.13",
    org.apache.log4j.config;version="1.2.13",
    ...

15.3.3 Enabling Log4j Logging

To specify logging to a Log4j Logger, set the following system properties on the command line:

   -Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
   -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
   -Dlog4j.configuration=<URL>/log4j.properties

Another very useful command line property is -Dlog4j.debug=true. Use this property when log4j output fails to appear or you get cryptic error messages.

15.3.4 Debugging Log4j Logging

If log4j output fails to appear or you get cryptic error messages, consider using the command line property -Dlog4j.debug=true on the command line.

For more information, see Section 15.3.3, "Enabling Log4j Logging".

15.4 Using the Apache Commons Logging API

You can use Apache Commons logging API in your Oracle CEP applications to log application-specific messages to the Oracle CEP server.log and consoleoutput.log files.

To use the commons logging API:

Set the system property org.apache.commons.logging.LogFactory to weblogic.logging.commons.LogFactoryImpl.

This LogFactory creates instances of weblogic.logging.commons.LogFactoryImpl that implement the org.apache.commons.logging.Log interface.

From the LogFactory, get a reference to the Commons Log object by name.

This name appears as the subsystem name in the log file.

Use the Log object to issue log requests to logging services.

The Commons Log interface methods accept an object. In most cases, this will be a string containing the message text.

The Commons LogObject takes a message ID, subsystem name, and a string message argument in its constructor. See org.apache.commons.logging at http://jakarta.apache.org/commons/logging/api/index.html.

The weblogic.logging.commons.LogImpl log methods direct the message to the server log.

Example 15-4 Commons Code Example

import org.apache.commons.logging.LogFactory;
import org.apache.commons.logging.Log;

public class MyCommonsTest {
  public void testCommonsLogging() {
    System.setProperty(LogFactory.FACTORY_PROPERTY,
      "weblogic.logging.commons.LogFactoryImpl");
    Log clog = LogFactory.getFactory().getInstance("MyCommonsLogger");
    // Log String objects
    clog.debug("Hey this is common debug");
    clog.fatal("Hey this is common fatal", new Exception());
    clog.error("Hey this is common error", new Exception());
    clog.trace("Dont leave your footprints on the sands of time");
  }
}

15.5 Configuring Oracle CEP Debugging Options

Table 15-6 lists the debugging options that Oracle CEP provides. You can enable and disable these debugging options to help diagnose problems with your Oracle CEP applications.

Table 15-6 Debug Flags

Debug Flag
Description

com.bea.core.debug.DebugBootBundle

Boot Debugging

com.bea.core.debug.DebugBootBundle.stdout

Boot Debugging debug strings go to stdout

com.bea.core.debug.DebugCM

Configuration Manager

com.bea.core.debug.DebugCM.stdout

Configuration Manager debug strings go to stdout

com.bea.core.debug.DebugConfigurationRuntime

Runtime information from the Runtime MBeans

com.bea.core.debug.DebugCSS

CSS

com.bea.core.debug.DebugCSS.stdout

CSS debug strings go to stdout

com.bea.core.debug.DebugCSSServices

CSS Services

com.bea.core.debug.DebugCSSServices.stdout

CSS Services debug strings go to stdout

com.bea.core.debug.DebugJDBCConn

JDBC Connection

com.bea.core.debug.DebugJDBCInternal

JDBC Internal

com.bea.core.debug.DebugJDBCRMI

JDBC RMI

com.bea.core.debug.DebugJDBCSQL

JDBC SQL

com.bea.core.debug.DebugJTA2PC

JTA 2PC

com.bea.core.debug.DebugJTA2PCDetail

JTA 2PCDetail

com.bea.core.debug.DebugJTA2PCStackTrace

JTA 2PCStackTrace

com.bea.core.debug.DebugJTAGateway

JTA Gateway

com.bea.core.debug.DebugJTAGatewayStackTrace

JTA GatewayStackTrace

com.bea.core.debug.DebugJTAHealth

JTA Health

com.bea.core.debug.DebugJTAJDBC

JTA JDBC

com.bea.core.debug.DebugJTALifecycle

JTA Lifecycle

com.bea.core.debug.DebugJTALLR

JTA LLR

com.bea.core.debug.DebugJTAMigration

JTA Migration

com.bea.core.debug.DebugJTANaming

JTA Naming

com.bea.core.debug.DebugJTANamingStackTrace

JTA NamingStackTrace

com.bea.core.debug.DebugJTANonXA

JTA NonXA

com.bea.core.debug.DebugJTAPropagate

JTA Propagate

com.bea.core.debug.DebugJTARecovery

JTA Recovery

com.bea.core.debug.DebugJTAResourceHealth

JTA ResourceHealth

com.bea.core.debug.DebugJTATLOG

JTA TLOG

com.bea.core.debug.DebugJTAXA

JTA XA

com.bea.core.debug.DebugJTAXAStackTrace

JTA XAStackTrace

com.bea.core.debug.DebugNetIO

NetIO

com.bea.core.debug.DebugOX

OSGi to JMX (OX)

com.bea.core.debug.DebugOX.stdout

OSGi to JMX (OX), debug goes to standard out.

com.bea.core.debug.DebugSCP

Simple Configuration Provider

com.bea.core.debug.DebugSCP.stdout

Simple Configuration Provider debug strings go to stdout

com.bea.core.debug.DebugSDS

Simple Declarative Services

com.bea.core.debug.DebugSDS.stdout

SDS debug strings go to stdout

com.bea.core.debug.DebugServiceHelper

Service Helper

com.bea.core.debug.DebugServiceHelper.stdout

Service Helper debug strings go to stdout

com.bea.core.debug.DebugStoreAdmin

Store Administration

com.bea.core.debug.DebugStoreIOLogical

Store IOLogical

com.bea.core.debug.DebugStoreIOLogicalBoot

Store IOLogicalBoot

com.bea.core.debug.DebugStoreIOPhysical

Store IOPhysical

com.bea.core.debug.DebugStoreIOPhysicalVerbose

Store IOPhysicalVerbose

com.bea.core.debug.DebugStoreXA

Store XA

com.bea.core.debug.DebugStoreXAVerbose

Store XAVerbose

com.bea.core.debug.servicehelper.dumpstack

Dump stack traces when Service Helper times out.

The following sections provide information on how to use these Oracle CEP debugging options:

Section 15.5.1, "How to Configure Oracle CEP Debugging Options Using System Properties"

Section 15.5.2, "How to Configure Oracle CEP Debugging Options Using a Configuration File"

If you are using Log4j logging, see also Section 15.3.4, "Debugging Log4j Logging".

15.5.1 How to Configure Oracle CEP Debugging Options Using System Properties

Use the following steps to configure debugging using system properties.

In this procedure, you will turn on Simple Declarative Services (SDS) debugging (com.bea.core.debug.DebugSDS from Table 15-6) using the Oracle CEP server startwlevs.sh file.

To configure Oracle CEP debugging options using system properties:

Locate the DebugSDS flag in Table 15-6:

com.bea.core.debug.DebugSDS

Create a property by prepending -D to the flag:

-Dcom.bea.core.debug.DebugSDS

Enable this debug flag by setting the property to true:

-Dcom.bea.core.debug.DebugSDS=true

Start the Oracle CEP server using the startwlevs.sh with this property:

./startwlevs.sh -Dcom.bea.core.debug.DebugSDS=true

15.5.2 How to Configure Oracle CEP Debugging Options Using a Configuration File

Use the following steps to configure debugging from a configuration file.

In this procedure, you will turn on Simple Declarative Services (SDS) debugging (com.bea.core.debug.DebugSDS from Table 15-6) in the Oracle CEP server config.xml file.

To configure Oracle CEP debugging options using a configuration file:

Locate the DebugSDS flag in Table 15-6:

com.bea.core.debug.DebugSDS

Create an XML tag by omitting the com.bea.core.debug. package name from the flag name:

<DebugSDS></DebugSDS>

Edit the Oracle CEP server config.xml file and add a debug element with a debug-properties child element as Example 15-5 shows.

Add your DebugSDS element to the debug-properties element as Example 15-5 shows.

Enable this debug flag by setting the DebugSDS element to true as Example 15-5 shows.

Example 15-5 Creating a debug-properties Element for the Debug Flag

<config>
   <debug>
      <debug-properties>
         <DebugSDS>true</DebugSDS>
      </debug-properties>
   </debug>

</config>

Set logger-severity to Debug in the logging-service element as Example 15-6 shows.

Set stdout-severity to Debug in the log-stdout element as Example 15-6 shows.

Example 15-6 Enabling Debug Logging

<config>
   <debug>
      <debug-properties>
         <DebugSDS>true</DebugSDS>
      </debug-properties>
   </debug>

   <logging-service>
      <logger-severity>Debug</logger-severity>
      <stdout-config>logStdout</stdout-config>
      <log-file-config>logFile</log-file-config>
   </logging-service>

   <log-file>
   <name>logFile</name>
   <log-file-severity>Debug</log-file-severity>
   <number-of-files-limited>true</number-of-files-limited>
   <rotated-file-count>4</rotated-file-count>
   <rotate-log-on-startup-enabled>true</rotate-log-on-startup-enabled>
   </log-file>

   <log-stdout>
      <name>logStdout</name>
      <stdout-severity>Debug</stdout-severity>
   </log-stdout>
</config>

Part V

References

Part V contains the following chapters:

Appendix A, "wlevs.Admin Command-Line Reference"

Appendix B, "Deployer Command-Line Reference"

Appendix C, "Security Utilities Command-Line Reference"

A wlevs.Admin Command-Line Reference

This appendix provides a reference to the Oracle Complex Event Processing (Oracle CEP) wlevs.Adminutility, which you can use to administer Oracle CEP, dynamically configure rules for Oracle Continuous Query Language processors, and monitor event latency and throughput.

Section A.1, "Overview of the wlevs.Admin Utility"

Section A.2, "Configuring the wlevs.Admin Utility Environment"

Section A.3, "Running the wlevs.Admin Utility Remotely"

Section A.4, "Running wlevs.Admin Utility in SSL Mode"

Section A.5, "Syntax for Invoking the wlevs.Admin Utility"

Section A.6, "Connection Arguments"

Section A.7, "User Credentials Arguments"

Section A.8, "Common Arguments"

Section A.9, "Command for Getting Usage Help"

Section A.10, "Commands for Managing the Server Life Cycle"

Section A.11, "Commands for Managing the Oracle CQL Rules of an Application"

Section A.12, "Commands for Managing the EPL Rules of an Application"

Section A.13, "Commands for Managing Oracle CEP MBeans"

Section A.14, "Commands for Controlling Event Record and Playback"

Section A.15, "Commands for Monitoring Throughput and Latency"

Section A.16, "Commands for Managing Configuration History"

A.1 Overview of the wlevs.Admin Utility

The wlevs.Admin utility is a command-line interface to administer Oracle CEP and, in particular, dynamically configure the rules for Oracle CQL and EPL processors and monitor the event latency and throughput of an application. The utility internally uses JMX to query the configuration and runtime MBeans of both the Oracle CEP server and deployed applications.

The Oracle CEP configuration framework allows concurrent changes to both the application and Oracle CEP server configuration by multiple users. The framework does not use locking to manage this concurrency, but rather uses optimistic version-based concurrency. This means that two users can always view the configuration of the same object with the intention to update it, but only one user is allowed to commit their changes. The other user will then get an error if they try to update the same configuration object, and must refresh their session to view the updated configuration.

Each wlevs.Admin utility command runs in its own transaction, which means that there is an implicit commit after each execution of a command. If you want to batch multiple configuration changes in a single transaction, you must use JMX directly to make these changes rather than the wlevs.Admin utility.

A.2 Configuring the wlevs.Admin Utility Environment

Before you can use the wlevs.Admin utility, you must configure your environment appropriately.

To configure the wlevs.Admin utility environment:

Install and configure the Oracle CEP software, as described in "Installing Oracle CEP" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Configure JMX connectivity for the domain you want to administer. See Chapter 12, "Configuring JMX for Oracle CEP."

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Set your CLASSPATH in one of the following ways:

Implicitly set your CLASSPATH by using the -jar argument when you run the utility.

Set the argument to the ORACLE_CEP_HOME/ocep_11.1/bin/wlevsadmin.jar file, where ORACLE_CEP_HOME refers to the main Oracle CEP installation directory.

When you use the -jar argument, you do not specify the wlevs.Admin utility name at the command line. For example:

prompt> java -jar d:/oracle_cep/ocep_11.1/bin/wlevsadmin.jar
-url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
UPLOAD -application helloworld -processor helloworldProcessor
-sourceURL file:///d:/test/newrules2.xml

Explicitly update your CLASSPATH by adding the following files to the CLASSPATH environment variable:

ORACLE_CEP_HOME/ocep_11.1/bin/wlevsadmin.jar
ORACLE_CEP_HOME/ocep_11.1/bin/wlevs.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.deployment.server_11.1.0.0.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.ede_11.1.0.0.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.management_11.1.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.jndi.context_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.jmx_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.rmi_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.i18n_1.4.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.diagnostics.core_2.1.0.0.jar
ORACLE_CEP_HOME/modules/javax.xml.stream_1.1.1.0.jar
ORACLE_CEP_HOME/com.bea.core.bootbundle_8.0.0.0.jar

Where ORACLE_CEP_HOME refers to the main directory into which you installed Oracle CEP.

A.3 Running the wlevs.Admin Utility Remotely

Sometimes it is useful to run the wlevs.Admin utility on a computer different from the computer on which Oracle CEP is installed and running.

To run the wlevs.Admin utility remotely:

Copy the following JAR files from the computer on which Oracle CEP is installed to the computer on which you want to run wlevs.Admin; you can copy the JAR files to the directory name of your choice:

ORACLE_CEP_HOME/ocep_11.1/bin/wlevsadmin.jar
ORACLE_CEP_HOME/ocep_11.1/bin/wlevs.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.deployment.server_11.1.0.0.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.ede_11.1.0.0.jar
ORACLE_CEP_HOME/ocep_11.1/modules/com.bea.wlevs.management_11.1.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.jndi.context_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.jmx_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.rmi_6.0.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.i18n_1.4.0.0.jar
ORACLE_CEP_HOME/modules/com.bea.core.diagnostics.core_2.1.0.0.jar
ORACLE_CEP_HOME/modules/javax.xml.stream_1.1.1.0.jar

Where ORACLE_CEP_HOME refers to the main directory into which you installed Oracle CEP.

Set your CLASSPATH in one of the following ways:

Implicitly set your CLASSPATH by using the -jar argument when you run the utility; set the argument to the NEW_DIRECTORY/wlevsadmin.jar file, where NEW_DIRECTORY refers to the directory on the remote computer into which you copied the required JAR files. When you use the -jar argument, you do not specify the wlevs.Admin utility name at the command line.

Explicitly update your CLASSPATH by adding all the files you copied to the remote computer to your CLASSPATH environment variable:

Invoke the wlevs.Admin utility as described in the next section.

A.4 Running wlevs.Admin Utility in SSL Mode

To use SSL when using the wlevs.Admin command-line utility, you must first create a trust keystore.

For more information, see Section 10.1.4, "SSL".

To run wlevs.Admin utility in SSL mode:

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

If not already running, start the Oracle CEP server.

See Section 1.5.4, "Starting and Stopping Oracle CEP Servers".

Change to the DOMAIN_DIR/servername/ssl directory, where DOMAIN_DIR refers to the main domain directory and servername refers to the name of your server.

For example:

d:\oracle_cep\user_projects\domains\mydomain\myserver\ssl.

Generate a trust keystore by specifying the following command (in practice, the command should be on one line):

prompt> java -classpath ORACLE_CEP_HOME\ocep_11.1\common\lib\evspath.jar;ORACLE_CEP_HOME\ocep_11.1\utils\security\wlevsgrabcert.jar
com.bea.wlevs.security.util.GrabCert host:secureport
-alias=alias truststorepath

where

ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep)

host refers to the computer on which server2 is running.

secureport refers to the SSL network i/o port configured for server2. Default value is 9003.

For more information, see Example 10-5 in Section 10.5.1, "How to Configure SSL Manually."

alias refers to the alias for the certificate in the trust keystore. Default value is the hostname.

truststorepath refers to the full pathname of the generated trust keystore file; default is evstrust.jks

For example (in practice, the command should be on one line):

prompt> java -classpath C:\OracleCEP\ocep_11.1\common\lib\evspath.jar;C:\OracleCEP\ocep_11.1\utils\security\wlevsgrabcert.jar
com.bea.wlevs.security.util.GrabCert server2:9003 -alias=server2 evstrust.jks

To specify that the wlevs.Admin command-line utility use this trust keystore file, use the following properties:

-Djavax.net.ssl.trustStore—Name of the trust keystore file you created in the preceding step

-Djavax.net.ssl.trustStorePassword—Password of the trust keystore file.

Also be sure to specify the secure port in the URL. For example:

prompt> java
-Djavax.net.ssl.trustStore=clitrust.jks
-Djavax.net.ssl.trustStorePassword=secret
-jar wlevsadmin.jar
-url service:jmx:msarmis://localhost:9003/jndi/jmxconnector
-username wlevs -password wlevs
SHUTDOWN -scheduleAt 600

A.5 Syntax for Invoking the wlevs.Admin Utility

The syntax for using the wlevs.Admin utility is as follows:

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    COMMAND-NAME command-arguments

The command names and arguments are not case sensitive.

The following sections provide detailed syntax information about the arguments you can supply to the wlevs.Admin utility:

Section A.6, "Connection Arguments"

Section A.7, "User Credentials Arguments"

Section A.8, "Common Arguments"

The following sections provide detailed syntax information about the supported commands of the wlevs.Admin utility:

Section A.9, "Command for Getting Usage Help"

Section A.10, "Commands for Managing the Server Life Cycle"

Section A.11, "Commands for Managing the Oracle CQL Rules of an Application"

Section A.12, "Commands for Managing the EPL Rules of an Application"

Section A.13, "Commands for Managing Oracle CEP MBeans"

Section A.14, "Commands for Controlling Event Record and Playback"

Section A.15, "Commands for Monitoring Throughput and Latency"

A.5.1 Example Environment

In many of the examples throughout the sections that follow, it is assumed that a certain environment has been set up:

The Oracle CEP instance listens to JMX requests on port 9002.

The Oracle CEP instance is installed on a host machine named ariel and uses this host name as its listen address.

The wlevs username has system-administrator privileges and uses wlevs for a password.

Also, for clarity, all the examples are shown on multiple lines; however, when you run the command, enter all arguments and commands on a single line.

A.5.2 Exit Codes Returned by wlevs.Admin

All wlevs.Admin commands return an exit code of 0 if the command succeeds and an exit code of 1 if the command fails.

To view the exit code from a Windows command prompt, enter echo %ERRORLEVEL% after you run a wlevs.Admin command. To view the exit code in a bash shell, enter echo $?.

wlevs.Admin calls System.exit(1) if an exception is raised while processing a command, causing Ant and other Java client JVMs to exit.

A.6 Connection Arguments

java wlevs.Admin
    [ {-url URL} | {-listenAddress hostname -listenPort port} ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    COMMAND-NAME command-arguments

When you invoke most wlevs.Admin commands, you specify the arguments in Table A-1 to connect to an Oracle CEP instance.

Table A-1 Connection Arguments

Argument
Definition

-url service:jmx:msarmi://host:port/jndi/jmxconnector

Specifies the URL that establishes a JMX connection to the Oracle CEP instance you want to administer, where:

host refers to the name of the computer on which the Oracle CEP instance is running

port refers to the Oracle CEP server JNDI port

If you use this argument, do not specify -listenAddress or -listenPort.

Other than host you specify the remainder of the URL as written.

For example, if Oracle CEP is running on a computer with hostname ariel, and the JMX listening port is 9002, then the URL would be:

  -url service:jmx:msarmi://ariel:9002/jndi/jmxconnector

See Chapter 12, "Configuring JMX for Oracle CEP" for details about configuring JMX, JNDI, and RMI for Oracle CEP.

-listenAddress hostname

Specifies the name of computer on which the Oracle CEP instances is running. This argument, together with -listenPort, is used to build the URL that establishes a JMX connection to the server you want to administer.

You use this argument, together with -listenPort, instead of -url.

For example, if Oracle CEP is running on a computer with hostname ariel, then this argument would be:

  -listenAddress ariel

-listenPort port

Specifies the port configured for Oracle CEP that listens to JMX connections. This argument, together with -listenAddress, is used to build the URL that establishes a JMX connection to the server you want to administer.

You use this argument, together with -listenAddress, instead of -url.

The JMX port is configured in the config.xml file of the Oracle CEP domain you are administering. In particular, the port is the <port> child element of the <netio> element, as shown:

   <netio>
      <name>NetIO</name>
      <port>9002</port>
   </netio>

In the example, the port is 9002 and you specify as an argument as follows:

  -listenPort 9002

See Chapter 12, "Configuring JMX for Oracle CEP" for details about configuring JMX, JNDI, and RMI for Oracle CEP.

A.7 User Credentials Arguments

java wlevs.Admin
    [ Connection Arguments ]
    [ -username username [-password password] ]
    [ Common Arguments ]
    COMMAND-NAME command-arguments

When you invoke most wlevs.Admin commands, you specify the arguments in Table A-2 to provide the user credentials of an Oracle CEP user who has permission to invoke the command.

If security has not been enabled for your Oracle CEP domain, then you do not have to provide user credentials.

Table A-2 User Credentials Arguments

Argument
Definition

-username username

The name of the user who is issuing the command. This user must have appropriate permission to view or modify the target of the command.

-password password

The password that is associated with the username.

Note:

The exit code for all commands is 1 if the wlevs.Admin utility cannot connect to the server or if the Oracle CEP instance rejects the username and password.

A.8 Common Arguments

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ -verbose ]
    COMMAND-NAME command-arguments

All wlevs.Admin commands support the argument in Table A-3 to get verbose output.

Table A-3 Common Arguments

Argument
Definition

-verbose

Specifies that wlevs.Admin should output additional verbose information.

A.9 Command for Getting Usage Help

This section describes the command for getting usage help.

A.9.1 HELP

Provides syntax and usage information for all Oracle CEP commands (by default) or for a single command if a command value is specified on the HELP command line.

You can issue this command from any computer on which the Oracle CEP is installed. You do not need to start a server instance to invoke this command, nor do you need to supply user credentials, even if security is enabled for the server.

A.9.1.1 Syntax

java wlevs.Admin HELP [COMMAND]

The COMMAND argument can be:

The keyword ALL, which returns usage information about all commands.

One of the keywords MBEAN, RULES, or LIFECYCLE, which returns usage information about the three different groups of commands.

An actual command, such as UPLOAD, which returns usage information about the particular command.

A.9.1.2 Example

In the following example, information about using the UPLOAD command is requested:

prompt> java wlevs.Admin HELP UPLOAD

The command returns the following (in practice, Java commands should be on one line):

Description:
Uploads rules to be configured in the processor.

Usage:
java wlevs.Admin
        [-url | -listenAddress <host-name> -listenPort <port>]
        -username <username> -password <password>
        UPLOAD -application <application name> -processor <processor name> -sourceURL "source url"

Where:
-application = Name of the application.
-processor = Name of the processor.
-sourceURL = source URL containing the rules in an XML format.

java wlevs.Admin -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
-username wlevs -password wlevs UPLOAD -application myapplication
-processor processor -sourceURL file:/d:/test/rules.xml

A.10 Commands for Managing the Server Life Cycle

Table A-4 is an overview of commands that manage the life cycle of a server instance. Subsequent sections describe command syntax and arguments, and provide an example for each command.

Table A-4 Overview of Commands for Managing the Server Life Cycle

Command
Description

SHUTDOWN

Gracefully shuts down a WebLogic Event Server.

A.10.1 SHUTDOWN

Gracefully shuts down the specified Oracle CEP instance.

A graceful shutdown gives Oracle CEP time to complete certain application processing currently in progress.

The -url connection argument specifies the particular Oracle CEP instance that you want to shut down, based on the host and jmxport values. See Section A.6, "Connection Arguments" for details.

A.10.1.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    SHUTDOWN [-scheduleAt seconds]

Table A-5 SHUTDOWN Arguments

Argument
Definition

-scheduleAt seconds

Specifies the number of seconds after which the Oracle CEP instance shuts down.

If you do not specify this parameter, the server instance shuts down immediately.

A.10.1.2 Example

The following example instructs the specified Oracle CEP instance to shut down in ten minutes:

prompt> java wlevs.Admin
       -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
       -username wlevs -password wlevs
        SHUTDOWN -scheduleAt 600

After you issue the command, the server instance prints messages to its log file and to its standard out. The messages indicate that the server state is changing and that the shutdown sequence is starting.

A.11 Commands for Managing the Oracle CQL Rules of an Application

Table A-6 is an overview of commands that manage the Oracle CQL rules for a particular processor of an Oracle CEP application. Subsequent sections describe command syntax and arguments, and provide an example for each command.

Table A-6 Overview of Commands for Managing Application Oracle CQL Rules

Command
Description

GETRULE

Returns the text of an existing Oracle CQL rule, query, or view of the processor of an Oracle CEP application.

ADDRULE

Adds a new Oracle CQL rule, query, or view to the processor of an Oracle CEP application.

DELETERULE

Deletes an existing Oracle CQL rule, query, or view from the processor of an Oracle CEP application.

REPLACERULE

Replaces an existing Oracle CQL rule, query, or view with new Oracle CQL text.

STARTRULE

Starts a previously stopped Oracle CQL rule or query.

STOPRULE

Stops a previously started Oracle CQL rule or query.

UPLOAD

Configures a set of Oracle CQL rules, queries, or views for a processor of an Oracle CEP application by uploading the rules from a component configuration XML file.

DOWNLOAD

Downloads the set of Oracle CQL rules, queries, or views associated with a processor of an Oracle CEP application to a component configuration XML file.

A.11.1 GETRULE

Returns the full text of an Oracle CQL rule, query, or view from the specified Oracle CQL processor of an Oracle CEP application.

A.11.1.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    GETRULE -application application -processor processor -rule rulename

Table A-7 GETRULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules you want to manage.

To get the exact name of your application, you can:

Use wlevs.Admin to query for the name (see Section A.13.5.3, "Querying for Application and Processor Names").

Use the Oracle CEP Visualizer: Start the Oracle CEP Visualizer (see "Starting the Oracle CEP Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing). In the left pane, navigate to and expand the Applications node of the Oracle CEP instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular Oracle CQL processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule rulename

Specifies the name of the Oracle CQL rule, query, or view you want to see.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on querying for the rule, query, or view name if you do not know it. You can also use the DOWNLOAD command to get the list of rules for a particular processor.

A.11.1.2 Example

The following example shows how to get the full text of the Oracle CQL view called myview from the Oracle CQL helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        GETRULE -application helloworld -processor helloworldProcessor
        -rule myview

A.11.2 ADDRULE

Adds a new Oracle CQL rule, query, or view to the specified processor of an Oracle CEP application.

If a rule, query, or view with the same name (identified with the rulename, queryname, or viewname parameter) already exists, then the ADDRULE command replaces the existing rule, query, or view with the new one.

Note:

An Oracle CQL query will immediately begin outputting events if its input channels provide input events. If you plan to use a query selector on a channel with an upstream Oracle CQL processor, you may observe unwanted query results on the downstream channel between the time you add the query to the upstream Oracle CQL processor and the time you configure the query selector on the downstream channel. For more information, see "Channel Properties: Outbound Channel With Query Selector" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing.

A.11.2.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    ADDRULE -application application -processor processor
        -rule  [rulename]  rulestring  |
        -query [queryname] querystring |
        -view  [viewname]  viewstring [-schema comma-separated-names]
        [-active true | false]

Table A-8 ADDRULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules you want to manage.

To get the exact name of your application, you can:

Use wlevs.Admin to query for the name (see Section A.13.5.3, "Querying for Application and Processor Names").

Use the Oracle CEP Visualizer: Start the Oracle CEP Visualizer (see "Starting the Oracle CEP Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing). In the left pane, navigate to and expand the Applications node of the Oracle CEP instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule [rulename] rulestring

Specifies the Oracle CQL rule you want to add to the specified processor of your application. An Oracle CQL rules include:

REGISTER|CREATE FUNCTION (aggregate and single-row functions)

REGISTER|CREATE WINDOW

The rulename parameter is not required; if you do not specify it, Oracle CEP generates a name for you.

Enter the Oracle CQL rulestring using double quotes.

-query [queryname] querystring

Specifies the Oracle CQL query you want to add to the specified processor of your application.

The queryname parameter is not required; if you do not specify it, Oracle CEP generates a name for you.

Enter the Oracle CQL querystring using double quotes.

-view [viewname] viewstring [-schema comma-separated-names]

Specifies the Oracle CQL view you want to add to the specified processor of your application.

The viewname parameter is not required; if you do not specify it, Oracle CEP generates a name for you.

Enter the Oracle CQL viewstring using double quotes.

The comma-separated-names parameter is not required; if you do not specify it, Oracle CEP generates the schema based on the select statement in the viewstring.

-active true | false

Specifies if the rule should be started and ready to process events after being added.

Valid values for this argument are true (start rule after adding) or false (do not start rule after adding); default value is true. If set to false, use STARTRULE to start the rule.

A.11.2.2 Example

The following example shows how to add the Oracle CQL query SELECT * FROM Withdrawal [Rows 5], with name myquery, to the Oracle CQL processor helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        ADDRULE -application helloworld -processor helloworldProcessor
        -query myquery "SELECT * FROM Withdrawal [Rows 5]"

A.11.3 DELETERULE

Deletes an existing Oracle CQL rule from the specified processor of an Oracle CEP application.

A.11.3.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    DELETERULE -application application -processor processor -rule rulename

Table A-9 DELETERULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules you want to manage.

To get the exact name of your application, you can:

Use wlevs.Admin to query for the name (see Section A.13.5.3, "Querying for Application and Processor Names").

Use the Oracle CEP Visualizer: Start the Oracle CEP Visualizer (see "Starting the Oracle CEP Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing). In the left pane, navigate to and expand the Applications node of the Oracle CEP instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules, queries, and views you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule rulename

Specifies the name of the Oracle CQL rule, query, or view you want to delete.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on querying for the rule name if you do not know it. You can also use the DOWNLOAD command to get the list of rules, queries, or views for a particular Oracle CQL processor.

A.11.3.2 Example

The following example shows how to delete the Oracle CQL view called myview from the Oracle CQL helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        DELETERULE -application helloworld -processor helloworldProcessor -rule myview

A.11.4 REPLACERULE

Replaces an existing Oracle CQL rule, query, or view with another rule, query, or view. Oracle CEP first destroys the original rule, query, or view and then inserts the new one in its place.

A.11.4.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    REPLACERULE -application application -processor processor
        -rule rulename rulestring

Table A-10 REPLACERULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules you want to manage.

To get the exact name of your application, you can:

Use wlevs.Admin to query for the name (see Section A.13.5.3, "Querying for Application and Processor Names").

Use the Oracle CEP Visualizer: Start the Oracle CEP Visualizer (see "Starting the Oracle CEP Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing). In the left pane, navigate to and expand the Applications node of the Oracle CEP instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular Oracle CQL processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule rulename rulestring

Specifies the name of the Oracle CQL rule, query, or view you want to replace. Oracle CEP deletes the old rule, query, or view and then inserts a new one, with the same name but with the new rule text. In the case of a view, Oracle CEP generates the schema based on the select statement in the rulestring.

Enter the Oracle CQL rulestring using double quotes.

A.11.4.2 Example

The following example shows how to replace an Oracle CQL query called myquery with the Oracle CQL text SELECT * FROM Withdrawal [Rows 10] in the Oracle CQL helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        REPLACERULE -application helloworld -processor helloworldProcessor
        -rule myquery "SELECT * FROM Withdrawal [Rows 10]"

A.11.5 STARTRULE

Starts an existing Oracle CQL rule or query that was previously stopped in the specified processor of an Oracle CEP application.

A.11.5.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    STARTRULE -application application -processor processor -rule rulename

Table A-11 STARTRULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules you want to manage.

To get the exact name of your application, you can:

Use wlevs.Admin to query for the name (see Section A.13.5.3, "Querying for Application and Processor Names").

Use the Oracle CEP Visualizer: Start the Oracle CEP Visualizer (see "Starting the Oracle CEP Visualizer" in the Oracle Fusion Middleware Visualizer User's Guide for Oracle Complex Event Processing). In the left pane, navigate to and expand the Applications node of the Oracle CEP instance to which the application is deployed. Each node under the Applications node is named with the exact application name.

Look at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules, queries, and views you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule rulename

Specifies the name of the Oracle CQL rule or query you want to start.

NOTE: You cannot stop and start a view. Views are always active.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on querying for the rule name if you do not know it. You can also use the DOWNLOAD command to get the list of rules, queries, or views for a particular Oracle CQL processor.

A.11.5.2 Example

The following example shows how to start the Oracle CQL query called myquery from the Oracle CQL helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        STARTRULE -application helloworld -processor helloworldProcessor -rule myquery

A.11.6 STOPRULE

Stops an existing Oracle CQL rule or query that was previously started in the specified processor of an Oracle CEP application.

A.11.6.1 Syntax

java wlevs.Admin
    [ Connection Arguments ]
    [ User Credentials Arguments ]
    [ Common Arguments ]
    STOPRULE -application application -processor processor -rule rulename

Table A-12 STOPRULE Arguments

Argument
Definition

-application application

Specifies the name of the Oracle CEP application whose Oracle CQL rules or queries you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on using wlevs.Admin to get the exact name of your application if you do not currently know it.

You can also get the exact application name by looking at the MANIFEST.MF file of the application; the application name is specified by the Bundle-SymbolicName header.

-processor processor

Specifies the name of the particular processor, attached to the Oracle CEP application specified with the -application argument, whose Oracle CQL rules, queries, and views you want to manage.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on getting the exact name if you do not know it.

-rule rulename

Specifies the name of the Oracle CQL rule or query you want to stop.

NOTE: You cannot stop and start a view. Views are always active.

See Section A.13.5.3, "Querying for Application and Processor Names" for details on querying for the rule name if you do not know it. You can also use the DOWNLOAD command to get the list of rules, queries, or views for a particular Oracle CQL processor.

A.11.6.2 Example

The following example shows how to stop the Oracle CQL query called myquery from the Oracle CQL helloworldProcessor of the helloworld application:

prompt> java wlevs.Admin
        -url service:jmx:msarmi://localhost:9002/jndi/jmxconnector
        -username wlevs -password wlevs
        STOPRULE -application helloworld -processor helloworldProcessor -rule myquery

A.11.7 UPLOAD

Replaces the configured Oracle CQL rules for a specified processor with the Oracle CQL rules from an uploaded component configuration file.

The component configuration file that contains the list of Oracle CQL rules conforms to the component configuration file schema (see "Component Configuration XSD Schema: wlevs_application_config.xsd" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse). This file contains one or more Oracle CQL rules that will replace those currently configured for the specified processor. An example of such a component configuration file is as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<config>
  <processor>
  <name>helloworldProcessor</name>
    <rules>
      <query id="helloworldRule1">

B Deployer Command-Line Reference

This appendix provides a reference to the Oracle Complex Event Processing (Oracle CEP) Deployer command-line utility, which you can use to deploy Oracle CEP applications.

Appendix B, "Overview of Using the Deployer Command-Line Utility"

Appendix B, "Configuring the Deployer Utility Environment"

Appendix B, "Running the Deployer Utility Remotely"

Appendix B, "Syntax for Invoking the Deployer Utility"

Appendix B, "Examples of Using the Deployer Utility"

B.1 Overview of Using the Deployer Command-Line Utility

The Deployer is a Java-based deployment utility that provides administrators and developers command-line based operations for deploying Oracle CEP applications. In the context of Oracle CEP deployment, an application is defined as an OSGi bundle at http://www.osgi.org/ JAR file that contains the following artifacts:

The compiled Java class files that implement some of the components of the application, such as the adapters, adapter factory, and POJO that contains the business logic.

One or more Oracle CEP configuration XML files that configure the components of the application, such as the processor, adapter, or streams.

The configuration files must be located in the META-INF/wlevs directory of the OSGi bundle JAR file.

An EPN assembly file that describes all the components of the application and how they are connected to each other. The EPN assembly file extends the standard Spring context file.

The EPN assembly file must be located in the META-INF/spring directory of the OSGi bundle JAR file.

A MANIFEST.MF file that describes the contents of the JAR.

See "Assembling an Oracle CEP Application" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse for detailed instructions on creating this deployment bundle.

The Deployer utility uses HTTP to connect to Oracle CEP, which means that you must configure Jetty for the server instance to which you are deploying your application. For details, see "Configuring Jetty" in the Oracle Fusion Middleware Administrator's Guide for Oracle Complex Event Processing.

Oracle CEP uses the deployments.xml file to internally maintain its list of deployed application OSGi bundles. This file is located in the DOMAIN_DIR/servername directory, where DOMAIN_DIR refers to the main domain directory corresponding to the server instance to which you are deploying your application and servername refers to the server instance itself. For more information, see "Oracle CEP Schemas" in the Oracle Fusion Middleware Developer's Guide for Oracle Complex Event Processing for Eclipse.

Caution:

The XSD for the deployments.xml file is provided for your information only; Oracle does not recommend updating the deployments.xml file manually.

B.2 Configuring the Deployer Utility Environment

Before you can use the Deployer utility, you must configure your environment appropriately.

To configure the Deployer utility environment:

Install and configure the Oracle CEP software, as described in "Installing Oracle CEP" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Open a command window and set your environment as described in "Setting Your Development Environment" in the Oracle Fusion Middleware Getting Started Guide for Oracle Complex Event Processing.

Update your CLASSPATH variable to include the wlevsdeploy.jar JAR file, located in the ORACLE_CEP_HOME/ocep_11.1/bin directory where, ORACLE_CEP_HOME refers to the main Oracle CEP installation directory, such as /oracle_cep.

B.3 Running the Deployer Utility Remotely

Sometimes it is useful to run the Deployer utility on a computer different from the computer on which Oracle CEP is installed and running.

To run the Deployer utility remotely:

Copy the following JAR files from the computer on which Oracle CEP is installed to the computer on which you want to run the deployer utility; you can copy the JAR files to the directory name of your choice:

ORACLE_CEP_HOME/ocep_11.1/bin/wlevsdeploy.jar

where ORACLE_CEP_HOME refers to the main directory into which you installed Oracle CEP.

Set your CLASSPATH in one of the following ways:

Implicitly set your CLASSPATH by using the -jar argument when you run the utility; set the argument to the NEW_DIRECTORY/wlevsdeploy.jar file, where NEW_DIRECTORY refers to the directory on the remote computer into which you copied the required JAR file. When you use the -jar argument, you do not specify the Deployer utility name at the command line.

Explicitly update your CLASSPATH by adding the JAR file you copied to the remote computer to your CLASSPATH environment variable:

Invoke the Deployer utility as described in the next section.

B.4 Syntax for Invoking the Deployer Utility

The syntax for using the Deployer utility is as follows:

java -jar wlevsdeploy.jar
    [Connection Arguments]
    [User Credential Arguments]
    [Deployment Commands]

The following sections describe the various arguments and commands you can use with the Deployer utility. See Appendix B, "Examples of Using the Deployer Utility" for specific examples of using the utility.

B.4.1 Connection Arguments

Table B-1 lists the connection arguments you can specify with the Deployer utility.

Table B-1 Connection Arguments

Argument
Description

-url url

Specifies the URL of the deployer of the Oracle CEP instance to which you want to deploy the OSGI bundle.

The URL takes the following form:

http://host:port/wlevsdeployer

where:

host refers to the hostname of the computer on which Oracle CEP is running.

port refers to the port number to which Oracle CEP listens. Its value is 9002 by default. This port is specified in the config.xml file that describes your Oracle CEP domain, located in the DOMAIN_DIR/config directory, where DOMAIN_DIR refers to your domain directory.

The port number is the value of the <Port> child element of the <Netio> element:

<Netio>
   <Name>NetIO</Name>
    <Port>9002</Port>
</Netio>

If you configure the Oracle CEP server for SSL-only connections (Section 10.7, "Configuring HTTPS-Only Connections for Oracle CEP Server"), use the value of the <Port> child element of the SSL <Netio> element:

<Netio>
   <name>sslNetIo</name>
   <port>9003</port>
   <ssl-config-bean-name>sslConfig</ssl-config-bean-name>
</Netio>

For example, if Oracle CEP is running on host ariel at port 9002, then the URL would be:

http://ariel:9002/wlevsdeployer

B.4.2 User Credential Arguments

Table B-2 lists the user credential arguments you can specify with the Deployer utility.

Table B-2 User Credential Arguments

Argument
Description

-user username

Username of the Oracle CEP administrator.

If you supply the -user option but you do not supply a corresponding -password option, the Deployer utility prompts you for the password.

-password password

Password of the Oracle CEP administrator.

NOTE: this argument is deprecated and may be removed in a later release. Oracle recommends that you do not use this argument.

B.4.3 Deployment Commands

Table B-3 lists the deployment commands you can specify with the Deployer utility.

Table B-3 Deployment Commands

Command
Description

-install bundle

Installs the specified OSGi bundle to the specified Oracle CEP instance.

The bundle parameter refers to a filename that is local to the computer from which you execute the Deployer utility.

Be sure to specify the full pathname of the bundle if it is not located relative to the directory from which you are running the Deployer utility.

In particular, Oracle CEP:

Copies the specified bundle to the domain directory.

Searches the META-INF/wlevs directory in the bundle for the component configuration files and extracts them to the domain directory.

Updates the internal deployment registry.

Starts the application. The incoming adapters immediately start receiving data.

-update bundle

Updates the existing OSGi bundle with new application code.

The bundle parameter refers to a filename that is local to the computer from which you execute the Deployer utility.

Be sure to specify the full pathname of the bundle if it is not located relative to the directory from which you are running the Deployer utility.

In particular, Oracle CEP:

Copies the updated bundles to the domain directory.

Searches the META-INF/wlevs directory in the updated bundle for the updated component configuration files and extracts them to the domain directory.

Updates the internal deployment registry with the updated information.

-uninstall name

Removes the existing bundle from the specified Oracle CEP instance.

The name parameter refers to the symbolic name of the OSGi bundle that you want to remove. The symbolic name is the value of the Bundle-SymbolicName header in the bundle's MANIFEST.MF file:

Bundle-SymbolicName: myApp

In particular, Oracle CEP:

Removes the specified OSGi bundle from the domain directory.

Removes the bundles from the internal deployment registry .

-suspend name

Suspends a currently running OSGI bundle which was previously installed to the specified Oracle CEP instance.

The name parameter refers to the symbolic name of the OSGi bundle that you want to start. The symbolic name is the value of the Bundle-SymbolicName header in the bundle's MANIFEST.MF file:

Bundle-SymbolicName: myApp

-resume name

Resumes a previously suspended OSGI bundle on the specified Oracle CEP instance; the configured adapters once again start immediately receiving incoming data.

The name parameter refers to the symbolic name of the OSGi bundle that you want to stop. The symbolic name is the value of the Bundle-SymbolicName header in the bundle's MANIFEST.MF file:

Bundle-SymbolicName: myApp

-group groupname

Specifies that the deploy command (install, uninstall, update, suspend, or resume) applies to a target group, or more specifically, to the set of running servers within that group.

To specify the domain group, use the keyword all, such as:

-group all

To specify a custom group, simply specify the name of the group:

-group my_group

Note: You may only deploy to a group if the server is part of a multi-server domain (that is, if clustering is enabled). You may not deploy to a group if the server is part of a standalone-server domain (that is, if clustering is disabled). For more information, see Section 5.1, "Overview of Oracle CEP Multi-Server Domain Administration".

-status name

Returns status information about a currently installed OSGi bundle.

The name parameter refers to the symbolic name of the OSGi bundle for which you want status information. The symbolic name is the value of the Bundle-SymbolicName header in the bundle's MANIFEST.MF file:

Bundle-SymbolicName: myApp

-startLevel startLevel

Specifies the level at which the OSGi bundle is started. Bundles with smaller numbers are started first.

System bundles have start levels of under 7.

B.5 Examples of Using the Deployer Utility

The following examples show how to use the Deployer utility. In all the examples, Oracle CEP is running on host ariel, listening at port 9002, and the username/password of the server administrator is wlevs/wlevs, respectively. For clarity, the examples are shown on multiple lines; however, when you run the command, enter all arguments and commands on a single line.

prompt> java -jar wlevsdeploy.jar
        -url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
        -install /application/bundles/com.my.exampleApp_1.0.0.0.jar

The preceding example shows how to install an OSGi bundle called com.my.exampleApp_1.0.0.0.jar, located in the /application/bundles directory.

The next command shows how to resume this application after it has been suspended:

prompt> java com.bea.wlevs.deployment.Deployer
        -url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
        -resume exampleApp

The next example shows how to uninstall the application, which removes all traces of it from the domain directory:

prompt> java com.bea.wlevs.deployment.Deployer
        -url http://ariel:9002/wlevsdeployer -user wlevs -password wlevs
        -uninstall exampleApp

The following example shows how to install an application called strategies_1.0.jar to the strategygroup; this example also shows how to use the -jar command of the java utility:

prompt> java -jar wlevsdeploy.jar
        -url http://ariel:9002/wlevsdeployer -install strategies_1.0.jar
        -group strategygroup

C Security Utilities Command-Line Reference

This appendix provides a reference to the Oracle Complex Event Processing (Oracle CEP) security utilities, including cssconfig, encryptMSAConfig, and GrabCert -- utilities for generating security configuration files, encrypting cleartext passwords, and generating a trust keystore.

Section C.1, "The cssconfig Command-Line Utility"

Section C.2, "The encryptMSAConfig Command-Line Utility"

Section C.3, "The GrabCert Command-Line Utility"

Section C.4, "The passgen Command-Line Utility" (Deprecated)

Section C.5, "The secgen Command-Line Utility" (Deprecated)

C.1 The cssconfig Command-Line Utility

Use the cssconfig command-line utility to generate a security configuration file (security.xml) that uses a password policy.

The cssconfig utility is located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep. The utility comes in two flavors:

cssconfig.cmd (Windows)

cssconfig.sh (UNIX)

The Unix version of this utility starts with the #!/bin/ksh directive. On most Unix systems, this forces the Korn Shell program to be used when using the utility. If the ksh program is not present in the bin directory or if the shell language used cannot properly execute the utility, run the utility as shown below:

prompt> $PATH_TO_KSH_BIN/ksh -c cssconfig.sh

where PATH_TO_KSH_BIN is the fully qualified path to the ksh program.

C.1.1 cssconfig Syntax

cssconfig -p propertyfile [-c configfile] -i inputkeyfile [-d]

where:

propertyfile is a file that contains security configuration properties provided by the user to define the required configuration. This option is required. See Example 10-1 for an example.

configfile is the name of the generated file. This property is optional; default value is security.xml.

inputkeyfile is the fully qualified name of the input key file used to generate the security configuration file. Set this option to the security-key.dat file in the config directory.

-d enables debugging.

C.2 The encryptMSAConfig Command-Line Utility

Use the encryptMSAConfig encryption command-line utility to encrypt cleartext passwords, specified by the <password> element, in XML files. Examples of XML files that can contain the <password> elements include:

config.xml

security-config.xml

Component configuration files

The encryptMSAConfig utility is located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep. The utility comes in two flavors:

encryptMSAConfig.cmd (Windows)

encryptMSAConfig.sh (UNIX)

C.2.1 encryptMSAConfig Syntax

encryptMSAConfig directory XML_file aesinternal.dat_file

where:

directory refers to the directory that contains the XML file which in turn contains a cleartext <password> element.

XML_file refers to the name of your XML file.

aesinternal.dat_file parameter refers to the location of the .aesinternal.dat file associated with your domain; this file is located in the ORACLE_CEP_HOME/user_projects/domains/DOMAIN/SERVER directory, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep, DOMAIN refers to the domain directory (such as myDomain), and SERVER refers to the server instance (such as myServer).

For example:

prompt> pwd
C:\OracleCEP\user_projects\domains\ocep_domain\defaultserver
prompt> C:\OracleCEP\ocep_11.1\bin\encryptMSAConfig.cmd . config\config.xml .aesinternal.dat

After you run the command, the value of the password element in XML_file will be encrypted.

C.3 The GrabCert Command-Line Utility

Use the GrabCert command-line utility to generate a trust keystore that includes the certificate from an existing trust keystore.

The GrabCert utility is located in the ORACLE_CEP_HOME/ocep_11.1/utils/security/wlevsgrabcert.jar file, where ORACLE_CEP_HOME refers to the Oracle CEP installation directory (such as d:/oracle_cep).

C.3.1 GrabCert Syntax

java GrabCert host:secureport [-alias=alias] [-noinput] [truststorepath]

where:

Table C-1 GrabCert Arguments

Option
Description
Default Value

host

The host name of the Oracle CEP server from which to copy the certificate.

secureport

The SSL port on host.

For more information, see Example 10-5 in Section 10.5.1, "How to Configure SSL Manually."

9003

alias

The alias for the certificate in the trust keystore.

host

-noinput

Use the -noinput option to instruct GrabCert to copy all certificates from host.

Omit the -noinput option to instruct GrabCert to list all available certificates from host and prompt you to select one.

truststorepath

The full pathname of the generated trust keystore file on host.

evstrust.jks

C.3.2 Examples of Using GrabCert

For example:

prompt> java GrabCert ariel:9003 -alias=ariel evstrust.jks

For other examples, see Section 10.5.3, "How to Configure SSL in a Multi-Server Domain for Oracle CEP Visualizer".

C.4 The passgen Command-Line Utility

Use the passgen command-line utility to hash user passwords for addition to a security database.

Note:

The passgen command line utility has been deprecated as of Version 10.3 of Oracle CEP. This is because the Configuration Wizard automatically performs the required task for you.

The passgen utility is located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep. The utility comes in two flavors:

passgen.cmd (Windows)

passgen.sh (UNIX)

C.4.1 passgen Syntax

passgen [-a algorithm] [-s saltsize] [-h] [-?] [password]*

where:

Table C-2 passgen Arguments

Option
Description
Default Value

-a

algorithm specifies the hash algorithm to use:

SHA-1

MD2

MD5

SSHA

SHA-256

The actual list of algorithms that can be set depends on the security providers plugged into the JDK.

If not specified, the default is SHA-1.

-s

saltsize is the number of salt characters added to ensure a unique hash string.

If not specified, the default is 4.

-h, -?

Displays command line options and exits.

password

If passwords are specified on the command line they shall be hashed and printed out one per line in order from left to right. If no passwords are specified on the command line, then the tool shall prompt for passwords to hash interactively.

Note:

Windows operating systems must use the .cmd version of this utility, Unix platforms must use the .sh version.

The Unix version of this utility starts with the #!/bin/ksh directive. On most Unix systems, this forces the Korn Shell program to be used when using the utility. If the ksh program is not present in the bin directory or if the shell language used cannot properly execute the utility, run the utility as shown below:

$PATH_TO_KSH_BIN/ksh -c passgen.sh

where PATH_TO_KSH_BIN is the fully qualified path to the ksh program.

C.4.2 Examples of Using passgen

The following sections provide examples that use the passgen utility:

Section C.4.2.1, "Using passgen interactively"

Section C.4.2.2, "Providing a Password on the Command Line"

C.4.2.1 Using passgen interactively

The following is an example of using the passgen utility interactively:

$ passgen
Password ("quit" to end): maltese
{SHA-1}LOtYvfQZj++4rV50AKpAvwMlQjqVd7ge
Password ("quit" to end): falcon
{SHA-1}u7NPQfgkHISr0tZUsmPrPmr3U1LKcAdP
Password ("quit" to end): quit
{SHA-1}2pPo4ViKsoNct3lTDoLeg9gHYZwQ47sV

In this mode, a password is entered and the resulting hashed version of the password is displayed. The hashed version of the password can then be entered into the password field of a security database.

Note:

In example, the passwords are shown to be echoed to the screen for demonstration purposes. In most situations, the password would not be displayed unless your platform does not support invisible passwords.

C.4.2.2 Providing a Password on the Command Line

The following is an example using the passgen utility when providing the passwords to be hashed on the command line:

$ passgen maltese falcon
{SHA-1}g0PNXmJW0OBtp/GkHrhNAhpbjM+capNe
{SHA-1}2ivZnjnKD9fordC1YFkrVGf0DHL6SVP1

When multiple passwords are provided, they are hashed from left to right:

{SHA-1}g0PNXmJW0OBtp/GkHrhNAhpbjM+capNe is hashed from maltese

{SHA-1}2ivZnjnKD9fordC1YFkrVGf0DHL6SVP1 is hashed from falcon.

C.5 The secgen Command-Line Utility

Use the secgen command-line utility to generate a security key or a security configuration file that uses encrypted passwords.

Caution:

The secgen command line utility has been deprecated as of Version 10.3 of Oracle CEP. This is because the Configuration Wizard automatically performs the required task for you.

Note:

This utility creates a security file that does not use a password policy; if you require a password policy, use the cssconfig command-line utility instead. See Section C.1, "The cssconfig Command-Line Utility."

The secgen utility is located in the ORACLE_CEP_HOME/ocep_11.1/bin directory, where ORACLE_CEP_HOME is the main Oracle CEP installation directory, such as d:\oracle_cep. The utility comes in two flavors:

secgen.cmd (Windows)

secgen.sh (UNIX)

C.5.1 Generating a File-Based Provider Configuration File

Use the following command line options to generate a file-based security provider configuration file.

secgen -F [-o outputfile] [-i inputkeyfile] [-e] [-P PropertyFilePath]

where:

Table C-3 secgen Arguments for a File-Based Provider Configuration File

Option
Description
Comments

-F

Generate a file-based security provider file; mutually exclusive with the -k option.

If not present, -k is assumed.

-o

outputfile is the name for the generated file.

Default output file name is security.xml.

-i

inputkeyfile is the fully qualified name of the input key file.

If not present, a default input key file named security-key.dat is expected.

-e

Enables unanimous adjudication during authorization.

-P

PropertyFilePath is the fully qualified path to a secgen property file which you can use to customize provider configurations.

See Section C.5.3, "Using the secgen Properties File" for details.

A SecGenTemplate.properties template file is located at ORACLE_CEP_HOME/ocep_11.1/bin where ORACLE_CEP_HOME is the main installation directory of Oracle CEP, such as /oracle_cep.

C.5.2 Generating a Key File

Use the following command line options to generate a security key file.

 secgen [-k] [-o outputfile]

where:

Table C-4 secgen Arguments for a Key File

Option
Description
Comments

-k

Generate a key file; mutually exclusive with the -F option.

If not present, -k is assumed.

-o

outputfile is the name for the generated file.

Default output file name is security-key.dat.

C.5.3 Using the secgen Properties File

When running secgen, you can use the -P option to specify a property file to customize provider configurations. A SecGenTemplate.properties template file is located in ORACLE_CEP_HOME/ocep_11.1/bin where ORACLE_CEP_HOME is the main installation directory of Oracle CEP, such as /oracle_cep.

You specify cleartext passwords the property file; however, these passwords will be stored encrypted in the generated configuration file.

The following example shows a property file used for file based provider customization:

#File based provider related
file.atn.file.store.path=myfileatnstore.txt
file.atn.file.store.password=firewall
file.atn.user.password.style=HASHED
file.atn.file.store.encrypted=true
file.atz.file.store.path=filatz
file.atz.file.store.password=firewall
file.rm.file.store.path=filerm
file.rm.file.store.password=firewall
file.cm.file.store.path=filecm
file.cm.file.store.password=firewall

The legal values for file.atn.user.password.style are:

HASHED

REVERSIBLEENCRYPTED

C.5.4 Examples of Using secgen

The following example shows how to use the secgen utility to generate a key file with the name myKeyFile.dat:

prompt> secgen -k -o myKeyFile.dat

The following example shows how to use the secgen utility to generate a file-based security provider configuration file named myConfigFile.xml which also uses the previously generated key file, myKeyFile.dat, and a properties file named mySecGen.properties:

prompt> secgen -F -i myKeyFile.dat -o myConfigFile.xml -P  c:\msa\myMSAConfig\mySecGen.properties

C.5.5 Limitations of secgen

Windows operating systems must use the .cmd version of this utility, Unix platforms should use the .sh version.

The Unix version of this utility starts with the #!/bin/ksh directive. On most Unix systems, this forces the Korn Shell program to be used when using the utility. If the ksh program is not present in the bin directory or if the shell language used cannot properly execute the utility, run the utility as shown below:

prompt> $PATH_TO_KSH_BIN/ksh -c secgen.sh

where PATH_TO_KSH_BIN is the fully qualified path to the ksh program.

Index

A  B  C  D  E  F  G  H  I  J  L  M  N  O  P  R  S  T  U  W 

A

adapters

HTTP pub-sub server, 14.1.2

all group, 5.2.2

Apache logging framework

about, 15.1.1

API, 15.4

log factory, 15.1.1.1

log files, 15.1.1.3

log format, 15.1.1.4

log severity, 15.1.1.2

application library

directories, 13.5.1, 13.5.2

library extensions directory, 13.5.1, 13.5.2

application roles, 10.1.3

applications

dependencies

about, 1.3.4

native code, 1.3.4

auditor, 10.10

B

bootclasspath

JDBC drivers, 13.5.3

native code dependencies, 1.3.4

bundler.sh, 13.5.1

C

configuration history management, 1.3.3

configuration MBean, 12.1.3

configuration MBeans

about, 12.1.2.2

naming, 12.1.3.1.1

Oracle CEP applications, 12.1.3.1

connection-creation-retry-frequency-seconds, 13.2.1, 13.2.2

cssconfig, C.1

D

Database Management System. See DBMS

DBMS security providers, 10.1.2

Debugging

configuring, 15.5

flags, 15.5

Log4j logging framework, 15.3.4

default data source, 13.2.1

default group, 5.2.2

default transaction manager, 13.2.1

DefaultAuditRecorder.log, 10.10

Deployer

about, B.1

arguments

connection, B.4.1

user credentials, B.4.2

commands, B.4.3

connection arguments, B.4.1

environment configuration, B.2

invoking, B.4

remote execution, B.3

user credentials arguments, B.4.2

deploying

multi-server domain, 8.1

standalone-server domain, 4.1

deployment groups

custom, 5.2.3

domain, 5.2.2

singleton, 5.2.1

domain deployment group, 5.2.2

domains

multi-server

about, 5.1

all group, 5.2.2

API, 6.4, 7.4

creating, 6.1, 7.1

custom deployment groups, 5.2.3

default group, 5.2.2

deploying, 8.1

directory structure, 5.4

domain deployment group, 5.2.2

group membership changes, 6.4, 7.4

groups, 5.2

high availability notifications, 5.3

messaging, 5.3, 5.3

notifications, 5.3

Oracle CEP native clustering, 5.1.2

Oracle Coherence, 5.1.1

security, 6.3, 7.3

singleton deployment groups, 5.2.1

starting, 6.5, 7.5

stopping, 6.5, 7.5

updating, 6.2, 7.2

standalone-server

about, 2.1

creating, 3.1

deploying, 4.1

starting, 3.3

stopping, 3.3

updating, 3.2

E

encryptMSAConfig, C.2

F

Federal Information Processing Standards. See FIPS

file-based security providers, 10.1.2

FIPS, 10.1.5

G

GrabCert, C.3

groups, 6.1.2, 7.1.2

multi-server domains, 5.2

security, 10.1.3

H

HTTP pub-sub server

about, 14.1

adapters, 14.1.2

channels, 14.1.2

configuring, 14.3

creating, 14.2

default properties, 14.1.2

properties, 14.1.2

security, 10.8.4

transport, 14.1.2

URL, 14.1.2

HTTPS, 10.7

I

identity, 7.1.1

IPv4, 9.1.2

IPv6, 9.1.2

J

Java Database Connectivity. See JDBC

Java Management Extensions. See JMX

Java SE security

about, 10.1.1

configuring, 10.2

policy.xml, 10.2

security.xml, 10.2

JConsole, 12.3.5, 12.3.6

JDBC

about, 13.1

configuring

application library, 13.5.1, 13.5.2

bootclasspath, 13.5.3

Oracle, 13.3

OSGi bundle, 13.5.1, 13.5.2

other drivers, 13.5

SQL Server, 13.4

data sources

about, 13.2

automatic retry, 13.2.1, 13.2.2

connection-creation-retry-frequency-seconds, 13.2.1, 13.2.1, 13.2.2, 13.2.2

custom configuration, 13.2.2

default configuration, 13.2.1

default transaction manager, 13.2.1

retry, 13.2.1, 13.2.2

where used, 13.2

drivers

Oracle, 13.1.1

SQL Server, 13.1.2

security, 10.8.3

supported databases, 13.1.3.1

Jetty

about, 11.1

security, 10.8.1

JMX

about, 12.1

configuring, 12.1.1, 12.2

management, 12.1.2, 12.3

configuring Oracle CEP components, 12.3.1, 12.3.2, 12.3.3

JConsole, 12.3.5, 12.3.6

JRMP, 12.1.2.1

monitoring throughput and latency, 12.3.4

MSA, 12.1.2.1

MBeans

about, 12.1.2

API, 12.1.3

configuration MBean, 12.1.2.2, 12.1.3, 12.1.3.1

configuration MBean naming, 12.1.3.1.1

hierarchy, 12.1.3.3

runtime MBean, 12.1.2.3, 12.1.3, 12.1.3.2

runtime MBean naming, 12.1.3.2.1

security, 10.8.2

JRMP protocol, 12.1.2.1

JsafeJCE, 10.1.5

L

LDAP security providers, 10.1.2

Lightweight Data Access Protocol. See LDAP

Log4j logging framework

about, 15.1.3

appenders, 15.1.3.2

configuring, 15.3, 15.3.1

debugging, 15.3.4

enabling, 15.3.3

layouts, 15.1.3.3

loggers, 15.1.3.1

Logging

about, 15.1

Apache logging framework

about, 15.1.1

API, 15.4

log factory, 15.1.1.1

log files, 15.1.1.3

log format, 15.1.1.4

log severity, 15.1.1.2

configuring

Log4j, 15.3

logging service, 15.2

severity, 15.2.4

files, 15.1.1.3

format, 15.1.1.4

log files, 15.1.1.3

log format, 15.1.1.4

Log4j logging framework

about, 15.1.3

appenders, 15.1.3.2

layouts, 15.1.3.3

loggers, 15.1.3.1

OSGi logging framework, 15.1.2

severity, 15.1.1.2

M

MBean

about, 12.1.2

API, 12.1.3

hierarchy, 12.1.3.3

naming, 12.1.3.1.1, 12.1.3.2.1

MSA protocol, 12.1.2.1

multicast-address, 6.1.1, 7.1.1

multi-server domain

about, 5.1

all group, 5.2.2

API, 6.4, 7.4

creating, 6.1, 7.1

custom deployment groups, 5.2.3

default group, 5.2.2

deploying, 8.1

directory structure, 5.4

domain deployment group, 5.2.2

group membership changes, 6.4, 7.4

groups, 5.2

high availability notifications, 5.3

messaging, 5.3, 5.3

notifications, 5.3

Oracle CEP native clustering, 5.1.2

Oracle Coherence, 5.1.1

security, 6.3, 7.3

singleton deployment groups, 5.2.1

starting, 6.5, 7.5

stopping, 6.5, 7.5

updating, 6.2, 7.2

N

Network Input/Output. See Network I/O

Network I/O

about, 9.1

client

about, 9.3

configuring, 9.3.1

internet protocol

IPv4, 9.1.2

IPv6, 9.1.2

IPv4, 9.1.2

IPv6, 9.1.2

providers, 9.1.1

provider-type, 9.1.1

server

about, 9.2

configuring, 9.2.1

O

Oracle CEP native clustering

about, 5.1.2

creating a multi-server domain, 7.1

Oracle Coherence

about, 5.1.1

configuring

caches, 6.1.3

caching system, 6.1.3

multi-server domains, 5.1.1

OSGi

HTTP Service, 11.1

logging framework, 15.1.2

P

passgen, C.4

password strength, 10.4

policy.xml, 10.2

provider-type, 9.1.1

R

retries, 13.2.1, 13.2.2

roles

about, 10.1.3

application, 10.1.3

task, 10.1.3

runtime MBean, 12.1.2.3, 12.1.3, 12.1.3.2

runtime MBean naming, 12.1.3.2.1

S

secgen, C.5

Secure Sockets Layer. See SSL

security

about, 10.1

auditor

about, 10.10

DefaultAuditRecorder.log, 10.10

log file, 10.10

cssconfig, C.1

disabling, 10.1.6

enabling, 10.1.6

encryptMSAConfig, C.2

FIPS, 10.1.5

GrabCert, C.3

groups, 10.1.3

HTTP publish-subscribe server, 14.2, 14.3

HTTPS, 10.7

Java SE

about, 10.1.1

configuring, 10.2

policy.xml, 10.2

security.xml, 10.2

JDBC, 13.2.2

Jetty, 11.2

JMX, 12.2

multi-server domains, 6.3, 7.3, 10.5.3

Oracle CEP services

about, 10.8

HTTP pub-sub server, 10.8.4

JDBC, 10.8.3

Jetty, 10.8.1

JMX, 10.8.2

passgen, C.4

password strength, 10.4

providers

about, 10.1.2

configuring, 10.3

DBMS, 10.1.2

file-based, 10.1.2

FIPS, 10.1.5

JsafeJCE, 10.1.5

LDAP, 10.1.2

roles

about, 10.1.3

application, 10.1.3

task, 10.1.3

secgen, C.5

SSL

about, 10.1.4

configuring, 10.5

multi-server domains, 6.3, 7.3

wlevs.Admin utility, A.4

users, 10.1.3

utilities

cssconfig, C.1

encryptMSAConfig, C.2

GrabCert, C.3

passgen, C.4

secgen, C.5

security.xml, 10.2

server-host-name, 6.1.1, 7.1.1

server-name, 6.1.1, 7.1.1

servlets, 11.1

SSL

about, 10.1.4

configuring, 10.5

multi-server domains, 6.3, 7.3

wlevs.Admin utility, A.4

standalone-server domain

about, 2.1

creating, 3.1

deploying, 4.1

starting, 3.3

stopping, 3.3

updating, 3.2

T

task roles, 10.1.3

transaction manager

default, 13.2.1

U

users, 10.1.3

utilities

Deployer, B.1

security

cssconfig, C.1

encryptMSAConfig, C.2

GrabCert, C.3

passgen, C.4

secgen, C.5

wlevs.Admin, A.1

W

wlevs.Admin

about, A.1

arguments

common, A.8

connection, A.6

user credentials, A.7

commands

configuration history, A.16

event record and playback, A.14

MBean types, A.13.1

MBeans, A.13.2

monitoring throughput and latency, A.15

rules, EPL, A.12

rules, Oracle CQL, A.11

server lifecycle, A.10

common arguments, A.8

connection arguments, A.6

environment configuration, A.2

exit codes, A.5.2

help, A.9

invoking, A.5

remote execution, A.3

SSL, A.4

user credentials arguments, A.7

wlevs.Admin commands

ADDPARAMS, A.12.5

ADDRULE, A.11.2, A.12.1

CONFIGHISTORY, A.16.1

CONFIGUREPLAYBACK, A.14.8

CONFIGURERECORD, A.14.3

DELETECONFIGCHANGEHISTORY, A.16.2

DELETEPARAMS, A.12.6

DELETERULE, A.11.3, A.12.2

DOWNLOAD, A.11.8, A.12.9

GET, A.13.3

GETPARAMS, A.12.7

GETRULE, A.11.1, A.12.4

INVOKE, A.13.4

LISTCHANGERECORDS, A.16.3

LISTPLAYBACK, A.14.10

LISTRECORD, A.14.5

LISTRESOURCEREVISIONS, A.16.4

MONITORAVGLATENCY, A.15.1

MONITORAVGLATENCYTHRESHOLD, A.15.2

MONITORAVGTHROUGHPUT, A.15.4

MONITORMAXLATENCY, A.15.3

QUERY, A.13.5

REPLACERULE, A.11.4, A.12.3

SCHEDULEPLAYBACK, A.14.9

SCHEDULERECORD, A.14.4

SET, A.13.6

SHUTDOWN, A.10.1

STARTPLAYBACK, A.14.6

STARTRECORD, A.14.1

STARTRULE, A.11.5

STOPPLAYBACK, A.14.7

STOPRECORD, A.14.2

STOPRULE, A.11.6

UNDOCONFIGCHANGE, A.16.5

UPLOAD, A.11.7, A.12.8

This figure shows the Oracle CEP IDE for Eclipse Manifest Editor. It contains tabs Overview, Dependencies, Runtime, Build, MANIFEST.MF, and build.properties. The MANIFEST.MF tab is selected.

This graphic shows the Oracle CEP server hosting the Http Pub/Sub Server. The Http Pub/Sub Server communicates with the Oracle CEP server using its communication infrastructure. A non-browser client is shown publishing to the Http Pub/Sub Server. A browser is shown with two clients: Client A is subscribing from the Http Pub/Sub Server and Client B is publishing to the Http Pub/Sub Server.

This figure shows the jconsole login screen after connection failure. The dialog box reads Connection failed: Retry? There is a Reconnect and Cancel button.

This figure shows the JConsole Browser. It contains menu items Connection, Window, and Help. There are tabs: Overview, Memory, Threads, Classes, VM Summary, and MBeans. The MBean tab is selected. On the left, there is a hierarchical list with item AppDeployment expanded to show the WLEventServerDomain item, which is selected. On the right is a properties page with two areas: MBeanInfo and Descriptor.

This figure shows an Oracle CEP data source. It contains a Pool that contains multiple Connection instances, each connected to a database. The data source is accessed using the javax.sqlDataSource API.

This figure shows the Oracle CEP IDE for Eclipse Manifest Editor. It contains tabs Overview, Dependencies, Runtime, Build, MANIFEST.MF, and build.properties. The Runtime tab is selected. It contains two panes: Exported Packages and Classpath. The Exported Packages pane includes a list box and buttons Add, Remove, Properties, and Calculate Uses. All buttons are greyed out except Add. The list box is empty. The Classpath pane includes a list box and buttons New, Add, Remove, Up, and Down. All buttons are greyed out except New and Add. The list box contains one library: . (dot).

This figure shows the JConsole New Connection dialog. It contains a Remote Process text field with value service:jmx:msarmi://localhost:9002/jndi/jmxconnector. There is a Username field with value wlevs and a Password field with value wlevs. There is a Connect and Cancel button.

This figure shows the Oracle CEP IDE for Eclipse Manifest Editor. It contains tabs Overview, Dependencies, Runtime, Build, MANIFEST.MF, and build.properties. The Overview tab is selected.

This figure shows the JAR Selection dialog. It contains a hierarchical list of folders including: .settings, build, dist, lib, META-INF, and src. The lib directory is expanded to show the file com.bea.oracle.ojdbc5_1.0.0.0_11-2-0-0.jar, which is selected. Below the list is check box Update the build path, which is checked. There is an OK and Cancel button.

This graphic shows the Oracle CEP MBean object model. The following classes extend WebLogicMBean: DomainRuntime, ServerRuntime, DomainMBean, ApplicationMBean, and StageMBean. The following classes also extend NotificationEmitter: ServerRuntime, StageMBean, DomainMBean, and ApplicationMBean. The following classes extend StageMBean: StreamMBean and ProcessorMBean.

This figure shows the New Java Class dialog. It contains text field Source folder with value JDBCDriver/src. There is a Browse button next to this field. It contains text field Package with no value. There is a Browse button next to this. It contains check box Enclosing Type, which is unchecked. The text field and Browse button next to this text field is greyed out. It contains text field Name with no value. It contains radio button group Modifiers composed of radio buttons public (selected), default, private (greyed out), and protected (greyed out). Below this radio button group are check boxes abstract (unchecked), final (unchecked), and static (greyed out). It contains text field Superclass with value java.lang.Object. There is a Browse button next to this text field. It contains text field Interfaces with no value. There is an Add and Remove button next to this text field. The Remove button is greyed out. Under the heading "Which method stubs would you like to create?" are check boxes public static void main(String[] args), Constructors from superclass, and Inherited abstract methods. Only the Inherited abstract methods check box is checked. Under the heading Do you want to add comments? there is check box Generate comments, which is unchecked.

This figure shows the Package Selection dialog. It contains text field Exported Packages with value org.osgi.framework and a list box that contains org.osgi.framework(1.5.0), org.osgi.framework.hooks.service(1.0.0), and org.osgi.framework.launch(1.0.0). The org.osgi.framework(1.5.0) item is selected. Below the list box is check box Show non-exported packages, which is unchecked. There is an OK and Cancel button.

This figure shows the Oracle CEP server lifecycle. The initial event is to start the server, startup core engine bundles, startup Oracle CEP bundles, register MBeans, and startup application bundles. This leads to the initial state: STARTING. After all application bundles are deployed, the Oracle CEP server transitions to the RUNNING state. When you shutdown the server, after all application bundles are shutdown, the Oracle CEP server transitions to the SHUTTING_DOWN state. Then MBeans are unregistered, Oracle CEP bundles shutdown, and core engine bundles shutdown.

This graphic shows the domain directory structure in a multi-server domain. The ORACLE_CEP_HOME directory contains a user_projects directory which contains a domains directory which contains a myDomain directory. The myDomain directory contains directories: myServer1, myServer2, and myServer3. The config.xml file for myServer1 contains a domain element with name child element myDomain. It also contains a cluster element with a server-name child element with value myServer1.

This figure shows the Oracle CEP IDE for Eclipse Package Explorer. It contains a directory named JDBCDriver that contains .settings directory, build directory, dist directory, lib directory, META-INF directory, and src directory. The lib directory is expanded to show a com.bea.oracle.ojdbc5_1.0.0.0_11-2-0-0.jar file.

This graphic shows the Oracle CEP MBean hierarchy for the Domain MBean and DomainRuntime MBean. The Domain MBean has one AppDeployment MBean, one Application MBean, and one or more Server MBeans. The Application MBean has one or more Adapter MBeans, one or more Stream MBeans, one or more Processor MBeans and one or more Stage MBeans. The DomainRuntime MBean has one ServerRuntime MBean. The ServerRuntime MBean has one MonitorRuntime MBean and one ProbeRuntime MBean.

This figure shows the Oracle CEP IDE for Eclipse Manifest Editor. It contains tabs Overview, Dependencies, Runtime, Build, MANIFEST.MF, and build.properties. The Dependencies tab is selected. It contains two panes: Required Plug-ins and Imported Packages. The Required Plug-ins pane includes a list box and buttons Add, Remove, Up, Down, and Properties. All buttons are greyed out except Add. The list box is empty. The Imported Packages pane includes a list box and buttons Add, Remove, and Properties. All buttons are greyed out except Add. The list box contains many packages.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2010, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Third-Party Content, Products, and Services Disclaimer

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.