Typical Server and Domain Tasks

This section contains the typical server and domain tasks you can perform with Oracle CEP Visualizer.

Visualizer is fairly self-explanatory and intuitive, so not all tasks are discussed here, but rather, just those that are most common and typical and from which other similar tasks can be deduced.

Viewing the JMX Configuration

Oracle CEP provides standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification. Software vendors can use these interfaces to monitor Oracle CEP MBeans, to change the configuration of an Oracle CEP domain, and to monitor the distribution (activation) of those changes to all server instances in the domain.

Visualizer and the wlevs.Admin command line tool both use JMX to connect to a server. However, to use these tools, and the JMX interfaces in general, you must configure Oracle CEP with the JMX configuration information in the config.xml file.

You can only view the JMX configuration of your Oracle CEP server using Visualizer. To change the configuration, you must manually update the server’s config.xml file. For details, see Configuring JMX for Oracle CEP.

In the left pane, click the Domain > Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
In the right pane, click the JMX tab.
The JMX properties are displayed in the table:

jndi-service-name—The name of the JNDI service to which the jmx server will bind its object.
rmi-service-name—The name of the RMI service with which the jmx server will register to receive calls.
rmi-jrmp-port—The port on which to listen for RMI JRMP JMX requests.
rmi-registry-port—The port on which to start the RMIRegistry.

Viewing the Configured Data Sources

Oracle CEP supports Java Database Connectivity (JDBC) 3.0 for relational database access.

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

You can only view the data source configuration of your Oracle CEP server using Visualizer. To change the configuration, you must manually update the server’s config.xml file. For details, see Configuring Access to a Relational Database.

In the left pane, click the Domain > Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
In the right pane, click the DataSource tab.
In the Data Sources table, select the data source you want to view by clicking on its name.
Click the Data Source option to view basic configuration about the data source, such as:

Name—The name of the data source.
JNDI name—The JNDI path to where this data source will be bound.
Global Tx Protocol—The protocol for Oracle CEP to use for the transaction branch when processing a global transaction, such as one-phase commit, emulate two-phase commit, and so on.

Click the Driver option to view information about the database to which this data source connects, such as:

URL—The database URL used to connect to a database. This URL includes the name of the database, the host and port of the computer on which the database server is running, and so on.
Driver Name—The name of the database driver that Oracle CEP uses to connect to a database. Drivers are specific to the database server, such as Oracle, Derby, and so on.
User Name—The database user account name that you want to use for each connection in the data source.
Password—The password for the database user acccount.
Use XA—Whether to use an XA driver.

Click the Connection Pool option to view the connection pool properties of the data source, such as:

Initial Capacity—The number of physical connections to create when creating the connection pool.
Max Capacity—The maximum number of physical connections that this connection pool can contain.
Capacity Increment—The increment with which to increase capacity, if required.

Viewing the Configuration of the Jetty Servers

Oracle CEP supports Jetty as the 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 the ability to dynamically register and unregister javax.servlet.Servlet objects with the run time and static resources.

You can only view the configuration of the Jetty servers configured in your Oracle CEP server using Visualizer. To change the configuration, you must manually update the server’s config.xml file. For details, see Configuring Jetty for Oracle CEP.

In the left pane, click the Domain > Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
In the right pane, click the HTTP Server tab.
In the right pane, the properties of the Jetty server are displayed:

The name of the Jetty server.
The network I/O object to which the Jetty server is bound.
The work manager name to which the Jetty server is bound.
The list of Web applications that are deployed to this Jetty server, along with the path of the application and its context path.

Configuring Work Managers

You can configure only existing work managers using Visualizer. You cannot delete old work managers or create new ones using Visualizer; rather, you must manually update the server’s config.xml file. For details, see Work Managers.

In the left pane, click the Domain > Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
In the right pane, click the Work Manager tab.
In the Work Manager table, select the work manager you want to configure by clicking on its name.
Click the Change button at the bottom of the page.
Update the work manager configuration properties:

Min threads—The minimum number of threads that the server allocates so as to reduce the intial time it takes to perform a task.
Max threads—The maximum number of concurrent threads that execute requests from the constrained work set.
Fair Share—The average thread-use time required to process requests.

Click Save to save your changes or Cancel to cancel the update.

Viewing the Persistent Event Store

The Oracle CEP event repository feature allows you to persist the events that flow out of a component of the event processing network (EPN) to a store, such as a database table, and then play them back at a later stage or explicitly query the events from a component such as an event bean. By default, Oracle CEP stores recorded events in a database, which means that before you can start using the record and playback feature in your own application, you must specify where the database server is located along with the name of the database server that will contain the recorded events.

You can only view the event store configured for an Oracle CEP server using Visualizer. To change the configuration, you must manually update the server’s config.xml file. For details, see Configuring an Event Store for Oracle CEP Server.

In the left pane, click Domain > Server > Services > Event Repository, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.
The right pane shows the event stores that have been configured. In particular:

RDBMS Provider Name displays the name of the store provider
Data Source displays the JDBC data source associated with the provider.

Viewing the Event Type Repository

Event types define the properties of the events that are handled by Oracle CEP applications. All the event types used by the applications of a server make up the event type repository.

You can only view the event type repository, along with the its event types, configured for an Oracle CEP server using Visualizer. To create new event types, see Creating the Event Types.

In the left pane, click Domain > Server > Services > Event Type Repository, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.

The right pane displays the Event Name table that lists all the event types used by the applications of the server.

In the right pane, click the name of an event in the Event Name table. The text box at the bottom displays the properties of the event type. For example, a simple Name event type that has three properties, first and last which are Strings and age which is an integer, might look like:

{first=java.lang.String, last=java.lang.String, age=int}

Configuring HTTP Publish-Subscribe Server Channels

Oracle CEP includes an HTTP publish-subscribe server to which applications can publish messages. Applications publish messages to a particular channel; other applications can then subscribe to this channel to receive these published messages.

You can use Visualizer to modify existing channels, as well as create new ones and delete existing ones. When you configure channels with Visualizer, they are permanent and survive server restart. Channels configured using APIs from a custom http pub-sub adapter are dynamic and do not survive server restart.

Visualizer includes the following preconfigured channels that are used by Visualizer itself; they cannot be deleted or modified:

Adding a Channel

Be sure you log on to Visualizer using an administration user.
In the left pane, click the Domain > Server > Services > Http Pub/Sub Server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.

A table appears in the right pane with the list of HTTP pub-sub servers configured for Oracle CEP.

In the right pane, click the name of the HTTP pub-sub server in the table. The default server is called pubsub.
In the working area towards the bottom of the right pane, enter the name of the new channel in the Channel Pattern text box. The channel must start with a /, such as /mychannel.
If you have security enabled, select the security roles that are allowed to publish and subscribe to the channel. Select more than one by holding down the Ctrl key.
Click the Add Channel. The new channel appears in the Channels table at the top right of the pane.

Deleting an Existing Channel

Be sure you log on to Visualizer using an administration user.
In the left pane, click the Domain > Server > Services > Http Pub/Sub server node, where Domain refers to the name of your Oracle CEP domain and Server refers to the name of the server instance.

A table appears in the right pane with the list of HTTP pub-sub servers configured for Oracle CEP.

In the right pane, click the name of the HTTP pub-sub server in the table. The default server is called pubsub.
In the Channels table, click the name of the channel you want to delete.
Click Delete Channel at the bottom of the pane.

Viewing Messages Published to HTTP Publish-Subscribe Channels

You can use Visualizer to view the messages that are currently being published to a channel, both the preconfigured channels used by Visualizer itself as well as user-defined channels.

In the top pane, click the Viewstream button.
In the right pane, click Initialize Client.
In the Subscribe Channel text box, enter the name of the channel to which the Oracle CEP server is publishing messages. For example, in the Record and Playback example, included in the Oracle CEP installation, the HTTP pub-sub adapter publishes to a channel called /playbackchannel.
Click Subscribe.

The Received Messages text box displays events being published to the channel.

To unsubscribe to the channel, click Unsubscribe.

Configuring Logging

Visualizer allows you to change the server-wide logging configuration, such as the severity of log messages you want the server to print out, the name of the log file, and so on. You can also view logging information for a particular module, but you cannot change it.

Visualizer Help