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.
This section describes the following topics:
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.
To view the JMX configuration of your Oracle CEP server:
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.
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.
To view the data sources configured for your Oracle CEP server:
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.
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.
To view the data sources configured for your Oracle CEP server:
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.
To configure an existing work manager using Visualizer:
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.
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.
To view the event store configured for an Oracle CEP server:
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.
To view the event store configured for an Oracle CEP server:
The right pane displays the Event Name table that lists all the event types used by the applications of the server.
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}
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:
See Configuring Security for the HTTP Publish-Subscribe Channels for information on securing the channels.
A table appears in the right pane with the list of HTTP pub-sub servers configured for Oracle CEP.
pubsub
./
, such as /mychannel
.A table appears in the right pane with the list of HTTP pub-sub servers configured for Oracle CEP.
pubsub
.
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 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.
See the Event Record and Playback example for an example of this feature.
/playbackchannel
.The Received Messages text box displays events being published to the channel.
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.
See Configuring Logging and Debugging for details about what the properties in the Visualizer logging page mean.
To configure the logging system for Oracle CEP using Visualizer: