This chapter provides a reference to elements of the wlevs_server_config.xsd schema, the schema behind XML you use to configure Oracle Event Processing server attributes and services such as logging, Oracle Continuous Query Language (CQL), Secure Sockets Layer (SSL), Java Management Extensions (JMX), HTTP Publish-Subscribe, and more.
This chapter includes the following sections:
Oracle Event Processing provides a number of server configuration elements that you use to configure Oracle Event Processing server-specific attributes and services.
The top-level Oracle Event Processing server configuration elements are organized into the following hierarchy:
config domain rmi jndi-context exported-jndi-context jmx transaction-manager work-manager logging-service log-stdout log-file jetty-web-app netio jetty glassfish-ws netio-client debug data-source http-pubsub event-store cluster bdb-config rdbms-event-store-provider user-event-store-provider ssl weblogic-rmi-client weblogic-jta-gateway use-secure-connections show-detail-error-message cql event-inspector
Use the auth-constraint element to configure an authorization constraint for a channel-constraints element. This element has the following child elements and no attributes.
|
Table 7-1 Child Elements of: auth-constraint
|
For more information on channels, see channels.
The following example shows how to use the auth-constraint element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</name>
<path>/pubsub</path>
<pub-sub-bean>
...
<channel-constraints>
<element>
...
<auth-constraint>
<description>Administrators</description>
<role-name>admin</role-name>
</auth-constraint>
</element>
</channel-constraints>
</pub-sub-bean>
</http-pubsub>
Use the bdb-config element to configure the default event store provider that uses a Berkeley database instance.
Optionally, you can configure the Oracle Event Processing server to use a relational database instance as the event store provider as rdbms-event-store-provider describes.
This element has the following child elements and no attributes.
|
Table 7-2 Child Elements of: bdb-config
|
The following example shows how to use the bdb-config element in the Oracle Event Processing server configuration file:
<bdb-config>
<db-env-path>bdb</db-env-path>
<cache-size>1000</cache-size>
</bdb-config>
Use the calendar element to configure cql calendar options in the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-3 Child Elements of: calendar
|
The following example shows how to use the calendar element in the Oracle Event Processing server configuration file. In the example, the cql element's unique identifier is myCQL.
<cql>
<name>myCQL</name>
<storage>
<folder>myfolder</folder>
<metadata-name>myname</metadata-name>
</storage>
<calendar>
<date-format>myclass</date-format>
<timezone>10</timezone>
</calendar>
<scheduler>
<class-name>myclass</class-name>
<threads>10</threads>
<direct-interop>false</direct-interop>
</scheduler>
</cql>
Use the channels element to configure one or more channels for a pubsub-bean element. Channel patterns always begin with a forward slash (/). Clients subscribe to these channels to either publish or receive messages.
This element has one or more element child elements that each contain a channel-pattern child element and zero or more message-filters child elements. Each message-filters child element contains an element child element with the string value of a message-filter-name that corresponds to a message-filters element.
This element has no attributes.
The following example shows how to use the channels element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</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>
Use the channel-constraints element to configure one or more channel constraints for a pubsub-bean element. This element has the following child elements and no attributes.
For more information on channels, see channels.
The following example shows how to use the channel-constraints element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</name>
<path>/pubsub</path>
<pub-sub-bean>
...
<channel-constraints>
<element>
<channel-resource-collection>
<element>
<channel-resource-name>Foo</channel-resource-name>
<descriptions>
<element>Foo</element>
</descriptions>
<channel-patterns>
<element>Foo</element>
</channel-patterns>
<channel-operations>
<element>Foo</element>
</channel-operations>
</element>
</channel-resource-collection>
<auth-constraint>
<description>Foo</description>
<role-name>Foo</role-name>
</auth-constraint>
</element>
</channel-constraints>
</pub-sub-bean>
</http-pubsub>
Use the channel-resource-collection element to configure one or more channel resource collections for a channel-constraints element. This element has the following child elements and no attributes.
|
Table 7-4 Child Elements of: channel-resource-collection
|
For more information on channels, see channels.
The following example shows how to use the channel-resource-collection element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</name>
<path>/pubsub</path>
<pub-sub-bean>
...
<channel-constraints>
<element>
<channel-resource-collection>
<element>
<channel-resource-name>Foo</channel-resource-name>
<descriptions>
<element>Foo</element>
</descriptions>
<channel-patterns>
<element>Foo</element>
</channel-patterns>
<channel-operations>
<element>Foo</element>
</channel-operations>
</element>
</channel-resource-collection>
<auth-constraint>
<description>Foo</description>
<role-name>Foo</role-name>
</auth-constraint>
</element>
</channel-constraints>
</pub-sub-bean>
</http-pubsub>
Use the cluster element to configure a cluster component in the Oracle Event Processing server. This element has the following child elements and no attributes.
Table 7-5 Child Elements of: cluster
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this cluster. For more information, see name. |
|
|
|
Specifies a unique name for the server. Oracle Event Processing Visualizer uses the value of this element when it displays the server in its console. Default value:
|
|
|
|
Specifies the host address or IP used for point-to-point HTTP multiserver communication. Default value is the IP address associated with the default NIC for the machine. |
|
|
|
This child element is required unless all servers of the multiserver domain are hosted on the same computer; in that case you can omit the 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 All the Oracle Event Processing servers using this Using Oracle Coherence, there is also an extension: if you use a unicast address then Oracle Coherence will be configured in Well Known Address (WKA) mode. This is necessary in environments that do not support multicast. |
|
|
|
The name of the interface that the multicast address should be bound to. This can be one of:
|
|
|
|
Specifies the port used for multicast traffic. Default value is |
|
|
|
Applicable only to Oracle Event Processing native clustering: specifies the server's identity and must be an integer between 1 and Not applicable to Oracle Coherence. |
|
|
See Description |
Specifies whether or not the cluster is enabled. Valid values:
|
|
|
See Description |
Specifies the type of security for this cluster. Valid values:
|
|
|
|
Specifies a comma-separated list of the names of the groups this cluster belongs to. |
|
|
|
Specifies, in milliseconds, the time out for point-to-point HTTP multiserver requests. Default value is |
The following example shows how to use the cluster element in the Oracle Event Processing server configuration file:
<cluster>
<name>MyCluster</name>
<server-name>myServer1</server-name>
<multicast-address>239.255.0.1</multicast-address>
<identity>1</identity>
<enabled>true</enabled>
</cluster>
Use the connection-pool-params element to specify connection pool-related data-source parameters. This element has the following child elements and no attributes.
|
Table 7-6 Child Elements of: connection-pool-params
|
The following example shows how to use the connection-pool-params element in the Oracle Event Processing server configuration file:
<data-source>
<name>orads</name>
<xa-params>
<keep-xa-conn-till-tx-complete>true</keep-xa-conn-till-tx-complete>
</xa-params>
<driver-params>
<url>jdbc:oracle:thin:@localhost:1521:ce102</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<element>
<name>user</name>
<value>wlevs</value>
</element>
<element>
<name>password</name>
<value>wlevs</value>
</element>
</properties>
</driver-params>
<connection-pool-params>
<initial-capacity>5</initial-capacity>
<max-capacity>10</max-capacity>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<test-frequency-seconds>5</test-frequency-seconds>
</connection-pool-params>
<data-source-params>
<jndi-names>
<element>orads</element>
</jndi-names>
<global-transactions-protocol>None</global-transactions-protocol>
</data-source-params>
</data-source>
Use the cql element to configure Oracle CQL-specific options in the Oracle Event Processing server. This element has the following child elements and no attributes.
The following example shows how to use the cql element in the Oracle Event Processing server configuration file:
<cql>
<name>myCQL</name>
<storage>
<folder>myfolder</folder>
<metadata-name>myname</metadata-name>
</storage>
<scheduler>
<class-name>myclass</class-name>
<threads>10</threads>
<direct-interop>false</direct-interop>
</scheduler>
</cql>
This data-source element defines configuration for a data source service.
The following example shows how to use the data-source element in the Oracle Event Processing server configuration file. In the example, the data-source element's unique identifier is orads.
<data-source>
<name>orads</name>
<driver-params>
<url>jdbc:oracle:thin:@localhost:1521:ce102</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<element>
<name>user</name>
<value>wlevs</value>
</element>
<element>
<name>password</name>
<value>wlevs</value>
</element>
</properties>
</driver-params>
<connection-pool-params>
<initial-capacity>5</initial-capacity>
<max-capacity>10</max-capacity>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<test-frequency-seconds>5</test-frequency-seconds>
</connection-pool-params>
<data-source-params>
<jndi-names>
<element>orads</element>
</jndi-names>
<global-transactions-protocol>None</global-transactions-protocol>
</data-source-params>
</data-source>
Use the data-source-params element to specify data source-related data-source parameters. This element has the following child elements and no attributes.
|
Table 7-7 Child Elements of: data-source-params
|
The following example shows how to use the data-source-params element in the Oracle Event Processing server configuration file:
<data-source>
<name>orads</name>
<xa-params>
<keep-xa-conn-till-tx-complete>true</keep-xa-conn-till-tx-complete>
</xa-params>
<driver-params>
<url>jdbc:oracle:thin:@localhost:1521:ce102</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<element>
<name>user</name>
<value>wlevs</value>
</element>
<element>
<name>password</name>
<value>wlevs</value>
</element>
</properties>
</driver-params>
<connection-pool-params>
<initial-capacity>5</initial-capacity>
<max-capacity>10</max-capacity>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<test-frequency-seconds>5</test-frequency-seconds>
</connection-pool-params>
<data-source-params>
<jndi-names>
<element>orads</element>
</jndi-names>
<global-transactions-protocol>None</global-transactions-protocol>
</data-source-params>
</data-source>
Use the driver-params element to specify JDBC driver-related data-source parameters. This element has the following child elements and no attributes.
|
Table 7-8 Child Elements of: driver-params
|
The following example shows how to use the driver-params element in the Oracle Event Processing server configuration file:
<data-source>
<name>orads</name>
<xa-params>
<keep-xa-conn-till-tx-complete>true</keep-xa-conn-till-tx-complete>
</xa-params>
<driver-params>
<url>jdbc:oracle:thin:@localhost:1521:ce102</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<element>
<name>user</name>
<value>wlevs</value>
</element>
<element>
<name>password</name>
<value>wlevs</value>
</element>
</properties>
</driver-params>
<connection-pool-params>
<initial-capacity>5</initial-capacity>
<max-capacity>10</max-capacity>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<test-frequency-seconds>5</test-frequency-seconds>
</connection-pool-params>
<data-source-params>
<jndi-names>
<element>orads</element>
</jndi-names>
<global-transactions-protocol>None</global-transactions-protocol>
</data-source-params>
</data-source>
Use the domain element to configure a domain name in the Oracle Event Processing server. This element has the name child element and no attributes.
The following example shows how to use the domain element in the Oracle Event Processing server configuration file. In the example, the domain's unique identifier is WLEventServerDomain.
<domain>
<name>WLEventServerDomain</name>
</domain>
Use the debug element to configure one or more debug properties for the Oracle Event Processing server. This element has the following child elements and no attributes.
Table 7-9 Child Elements of: debug
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
One or more child elements formed by taking a debug flag name (without its package name) and specifying a value of |
The following example shows how to use the debug element to turn on Simple Declarative Services (SDS) debugging using debug flag com.bea.core.debug.DebugSDS in the Oracle Event Processing server configuration file.
<debug>
<name>myDebug</name>
<debug-properties>
<DebugSDS>true</DebugSDS>
...
</debug-properties>
</debug>
Use the event-inspector element to test a component. This element has the pubsub-server-name child element and no attributes.
The pubsub-server-name value is the value of the http-pubsub element name child element as defined in the local Oracle Event Processing server file.
The following example shows how to use the event-inspector element in a configuration file.
<event-inspector>
<name>myEventInspectorConfig</name>
<pubsub-server-name>myPubSub</pubsub-server-name>
</event-inspector>
The following example shows the corresponding local Oracle Event Processing server file entry:
<http-pubsub>
<name>myPubSub</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>
...
</channels>
</pub-sub-bean>
</http-pubsub>
Use the event-store element to configure an event store for the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-10 Child Elements of: event-store
|
The following example shows how to use the event-store element in the Oracle Event Processing server configuration file. In the example, the adapter's unique identifier is myEventStore.
<config>
<event-store>
<name>myEventStore</name>
<provider-order>
<provider>provider1</provider>
<provider>provider2</provider>
</provider-order>
</event-store>
</config>
Use the exported-jndi-context element to export a remote JNDI service that may be accessed via clients using RMI. It registers the JNDI context with the RMI service, so that it may be accessed remotely by clients that pass a provider URL parameter when they create their InitialContext object. This service requires that a jndi-context configuration object also be specified. If it is not, then this service will not be able to start.
This element has the following child elements and no attributes.
|
Table 7-11 Child Elements of: exported-jndi-context
|
The following example shows how to use the exported-jndi-context element in the Oracle Event Processing server configuration file. In the example, the adapter's unique identifier is RemoteJNDI.
<rmi>
<name>myRMI</name>
<http-service-name>TestJetty</http-service-name>
</rmi>
<exported-jndi-context>
<name>RemoteJNDI</name>
<rmi-service-name>myRMI</rmi-service-name>
</exported-jndi-context>
Use the glassfish-ws element to configure web services in Oracle Event Processing. This element has the http_service_name element and no attributes.
Use the http_service_name element to specify the name of the HTTP service to use to register web service end points in Oracle Event Processing. The service is provided by a Jetty instance of the same name.
The following example shows how to use the glassfish-ws element in the Oracle Event Processing server configuration file. In the example, the glassfish-ws element's unique identifier is myWS.
<glassfish-ws>
<name>myWS</name>
<http-service-name>TestJetty</http-service-name>
</glassfish-ws>
Use the http-pubsub element to configure an HTTP publish-subscribe service. This element has the following child elements and no attributes.
The following example shows how to use the http-pubsub element in the Oracle Event Processing server configuration file. In the example, the http-pubsub element's unique identifier is myPubsub.
<http-pubsub>
<name>myPubsub</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>
Use the jetty element to configure an instance of the Jetty HTTP server. This element has the following child elements and no attributes.
|
Table 7-12 Child Elements of: jetty
|
The following example shows how to use the jetty element in the Oracle Event Processing server configuration file. In the example, the jetty element's unique identifier is TestJetty.
<jetty>
<name>TestJetty</name>
<work-manager-name>WM</work-manager-name>
<network-io-name>Netio</network-io-name>
<secure-network-io-name>SecureNetio</secure-network-io-name>
<debug-enabled>false</debug-enabled>
<scratch-directory>JettyWork</scratch-directory>
</jetty>
Use the jetty-web-app element to represent a Web application for use by Jetty. Each instance of this object represents a Web application which must be deployed using the Jetty service.
This element has the following child elements and no attributes.
|
Table 7-13 Child Elements of: jetty-web-app
|
The following example shows how to use the jetty-web-app element in the Oracle Event Processing server configuration file. In the example, the jetty-web-app element's unique identifier is financial.
<jetty-web-app>
<name>financial</name>
<context-path>/financial</context-path>
<path>../testws2/financialWS.war</path>
<jetty-name>TestJetty</jetty-name>
</jetty-web-app>
Use the jmx element to configure Java Management Extension (JMX) properties in the Oracle Event Processing server.
|
Table 7-14 Child Elements of: jmx
|
The following example shows how to use the jmx element in the Oracle Event Processing server configuration file. In the example, the jmx element's unique identifier is myJMX.
<jmx>
<name>myJMX</name>
<jndi-service-name>JNDI</jndi-service-name>
<rmi-service-name>RMI</rmi-service-name>
</jmx>
Use the jndi-context element to configure the JNDI provider. When it is placed in the configuration, the MSA JNDI Context is initialized. One instance of this configuration type must be placed in the configuration if the JNDI service is to be used, either locally, or remotely through the exported-jndi-context configuration type.
This element has the following child elements and no attributes.
|
Table 7-15 Child Elements of: jndi-context
|
The following example shows how to use the jndi-context element in the Oracle Event Processing server configuration file. In the example, the adapter's unique identifier is myJNDI.
<jndi-context>
<name>myJNDI</name>
<default-provider>true</default-provider>
</jndi-context>
Use the log-file element to configure logging to a file on the Oracle Event Processing server.
|
Table 7-16 Child Elements of: log-file
|
The following example shows how to use the log-file element in the Oracle Event Processing server configuration file. In the example, the log-file element's unique identifier is logFile.
<log-file>
<name>logFile</name>
<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>
Use the log-stdout element to configure logging to standard out (console) on the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-17 Child Elements of: log-stdout
|
The following example shows how to use the log-stdout element in the Oracle Event Processing server configuration file. In the example, the log-stdout element's unique identifier is logStdout.
<log-stdout>
<name>logStdout</name>
<stdout-severity>Debug</stdout-severity>
</log-stdout>
Use the logging-service element to configure a logging service on the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-18 Child Elements of: logging-service
|
The following example shows how to use the logging-service element in the Oracle Event Processing server configuration file. In the example, the logging-service element's unique identifier is myLogService.
<logging-service>
<name>myLogService</name>
<stdout-config>myStdoutConfig</stdout-config>
<logger-severity>Notice</logger-severity>
<logger-severity-properties>
<entry>
<key>FileAdapter</key>
<value>Debug</value>
</entry>
<entry>
<key>CQLProcessor</key>
<value>Debug</value>
</entry>
</logger-severity-properties>
</logging-service>
Use the message-filters element to configure one or more message filters for a pubsub-bean element.
This element has one or more element child elements that each contain a message-filter-name and message-filter-class child element.
This element has no attributes.
The following example shows how to use the message-filters element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>pubsub</name>
<path>/pubsub</path>
<pub-sub-bean>
...
<message-fitlers>
<element>
<message-filter-name>Foo</message-filter-name>
<message-filter-class>Foo</message-filter-class>
</element>
<element>
<message-filter-name>Foo</message-filter-name>
<message-filter-class>Foo</message-filter-class>
</element>
</message-filters>
...
</pub-sub-bean>
</http-pubsub>
Use the name element to declare a unique identifier for an Oracle Event Processing server configuration element. This element has no child elements and no attributes.
The following example shows how to use the name element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>pubsub</name>
<path>/pubsub</path>
...
</http-pubsub>
Use the netio element to represent a network input and output (IO) service, that can be used by other services to act as the server for network IO. This element has the following child elements and no attributes.
Table 7-19 Child Elements of: netio
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The name of the SSL configuration object to use. If not null, then this client will create secure sockets using the specified SSL configuration. If not set, then no SSL will be supported. |
|
|
|
Specify which provider to use for the underlying socket implementation. |
|
|
|
A hint to the provider as to the number of threads to use for processing sockets. A value of zero will result in the provider choosing based on its own default.Default: 0. |
|
|
|
The port to listen on. The server will immediately start to listen for incoming connections on this port. |
|
|
|
The address on which this instance of Netio should listen for incoming connections. It may be set to a numeric IP address in the |
The following example shows how to use the netio element in the Oracle Event Processing server configuration file. In the example, the netio element's unique identifier is myNetio.
<netio>
<name>myNetio</name>
<port>12345</port>
</netio>
Use the netio-client element to register a network input/output (IO) service that may be used to perform non-blocking network IO, but which will not act as a server and listen for incoming connections. This element has the following child elements and no attributes.
Table 7-20 Child Elements of: netio-client
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The name of the SSL configuration object to use. If not null, then this client will create secure sockets using the specified SSL configuration. If not set, then no SSL will be supported. |
|
|
|
Specify which provider to use for the underlying socket implementation. |
The following example shows how to use the netio-client element in the Oracle Event Processing server configuration file. In the example, the netio-client element's unique identifier is netiossl.
<netio-client>
<name>netiossl</name>
<ssl-config-bean-name>sslConfig</ssl-config-bean-name>
<provider-type>NIO</provider-type>
</netio-client>
Use the partition-order-capacity element to define the maximum capacity of a query partition when the ordering-constraint attribute is set to PARTITION_ORDERED. Set this element on a cql component. Consider setting this element's value when you've configured a query processor for parallel execution, and when the query's ordering-constraint attribute is set to PARTITION_ORDERED. The default value is 4.
This element has no child elements and no attributes.
The following example shows how to use the partition-order-capacity element in the Oracle Event Processing server configuration file:
<cql>
<name>myCQL</name>
<partition-order-capacity>20</partition-order-capacity>
</cql>
Use the path element to configure the path for an http-pubsub element. This element has no child elements or attributes.
The following example shows how to use the path element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</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>
Use the pubsub-bean element to configure a publish-subscribe bean for an http-pubsub element. This element has the following child elements and no attributes.
See http://www.oracle.com/webfolder/technetwork/weblogic/weblogic-pubsub/1.0/weblogic-pubsub.xsd.
The following example shows how to use the pubsub-bean element in the Oracle Event Processing server configuration file:
<http-pubsub>
<name>myPubsub</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>
Use the rdbms-event-store-provider element to configure an event store provider that uses a relational database management system in the Oracle Event Processing server. By default, Oracle Event Processing server uses a Berkeley database instance as the event store provider as bdb-config describes.
This element has the following child elements and no attributes.
|
Table 7-21 Child Elements of: rdbms-event-store-provider
|
The following example shows how to use the rdbms-event-store-provider element in the Oracle Event Processing server configuration file:
<rdbms-event-store-provider>
<name>test-rdbms-provider</name>
<init-timeout>10000</init-timeout>
<data-source-name>derby1</data-source-name>
<user-policy-attributes>
<entry>
<key>key1</key>
<value>value1</value>
</entry>
<key>key1</key>
<value>value1</value>
<entry>
</entry>
</user-policy-attributes>
</rdbms-event-store-provider>
Use the rmi element to configure an RMI service, which allows server- side objects to be exported to remote clients. This element has the following child elements and no attributes.
|
Table 7-22 Child Elements of: rmi
|
The following example shows how to use the rmi element in the Oracle Event Processing server configuration file. In the example, the rmi element's unique identifier is myRMI.
<rmi>
<name>myRMI</name>
<http-service-name>TestJetty</http-service-name>
</rmi>
Use the scheduler element to configure cql scheduler options in the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-23 Child Elements of: scheduler
|
The following example shows how to use the scheduler element in the Oracle Event Processing server configuration file:
<cql>
<name>myCQL</name>
<calendar>
<date-format>myclass</date-format>
<timezone>10</timezone>
</calendar>
<scheduler>
<class-name>oracle.cep.execution.scheduler.FIFOScheduler</class-name>
<threads>10</threads>
<direct-interop>false</direct-interop>
</scheduler>
</cql>
Use the server-config element to configure the server-specific properties of a pubsub-bean element. This element has the following child elements and no attributes.
Table 7-24 Child Elements of: server-config
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
See Description |
This element contains one or more
|
|
|
|
Specifies 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. Default: 60. |
|
|
|
Specifies the number of seconds after which persistent clients are disconnected and deleted by the pub-sub server, if during that time the persistent client does not send a connect or re-connect message. This value must be larger than client-timeout-secs. If the persistent client reconnects before the persistent timeout is reached, the client receives all messages that have been published to the persistent channel during that time; if the client reconnects after the timeout, then it does not get the messages. Default: 600 seconds. |
|
|
|
Specifies how long (in milliseconds) the client can delay subsequent requests to the Default: 500 ms. |
|
|
|
Specifies the name of the work manager that delivers messages to clients. The value of this element corresponds to the value of the For more information, see |
|
|
|
Specifies whether clients can publish messages without having explicitly connected to the HTTP pub-sub server. Valid values:
|
The following example shows how to use the server-config element in the Oracle Event Processing server configuration file:
<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>
Use the services element to configure the service properties of a pubsub-bean element. This element has the following child elements and no attributes.
|
Table 7-25 Child Elements of: services
|
The following example shows how to use the services element in the Oracle Event Processing server configuration file:
<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>
<services>
<element>
<service-channel>Foo</service-channel>
<service-class>Foo</service-class>
<service-method>Foo</service-method>
</element>
</services>
</pub-sub-bean>
</http-pubsub>
Use the show-detail-error-message element to configure whether or not the Oracle Event Processing server uses secure connections. This element has the following child elements and no attributes.
|
Table 7-26 Child Elements of: show-detail-error-message
|
The following example shows how to use the show-detail-error-message element in the Oracle Event Processing server configuration file. In the example, the show-detail-error-message element's unique identifier is myShowDetail.
<show-detail-error-message>
<name>myShowDetail</name>
<value>true</value>
</show-detail-error-message>
Use the ssl element to configure Secure Sockets Layer-specific properties on the Oracle Event Processing server. This element has the following child elements and no attributes.
Table 7-27 Child Elements of: ssl
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this cluster. For more information, see |
|
|
|
Specifies the file path to the key store such as |
|
|
See Description |
This element contains a |
|
|
|
Specifies the alias for the key store. |
|
|
|
Specifies the key manager algorithm such as |
|
|
|
Specifies the SSL protocol such as |
|
|
|
Specifies the file path to the trust store such as |
|
|
See Description |
This element contains a |
|
|
|
Specifies the alias for the trust store. |
|
|
|
Specifies the trust store type such as |
|
|
|
Specifies the trust manager algorithm such as |
|
|
|
Specifies whether or not Oracle Event Processing server uses a Federal Information Processing Standards (FIPS)-certified pseudo-random number generator. |
|
|
|
Specifies whether or not client certificate authentication is required. |
|
|
See Description |
This element contains one or more |
|
|
|
When
|
|
|
|
When
|
The following example shows how to use the ssl element in the Oracle Event Processing server configuration file:
In the example, the ssl element's unique identifier is sslConfig.
<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>
<enforce-fips>false</enforce-fips>
<need-client-auth>false</need-client-auth>
</ssl>
Use the timeout-seconds element to configure weblogic-jta-gateway default transaction time out in seconds in the Oracle Event Processing server. The default: 60. this element has no child elements and no attributes.
The following example shows how to use the timeout-seconds element in the Oracle Event Processing server configuration file:
<weblogic-jta-gateway>
<name>myJTAGateway</name>
<timeout-seconds>90</timeout-seconds>
<weblogic-instances>
<weblogic-instance>
<domain-name>ocep_domain</domain-name>
<server-name>fxserver</server-name>
<protocol>t3</protocol>
<host-address>ariel</host-address>
<port>9002</port>
</weblogic-instance>
</weblogic-instances>
</weblogic-jta-gateway>
Use the transaction-manager element to configure transaction manager properties in the Oracle Event Processing server. This element has the following child elements and no attributes.
|
Table 7-28 Child Elements of: transaction-manager
|
The following example shows how to use the transaction-manager element in the Oracle Event Processing server configuration file. In the example, the transaction-manager element's unique identifier is My_tm.
<transaction-manager>
<name>My_tm</name>
<timeout-seconds>30</timeout-seconds>
<abandon-timeout-seconds>86400</abandon-timeout-seconds>
<forget-heuristics>true</forget-heuristics>
<before-completion-iteration-limit>12</before-completion-iteration-limit>
<max-transactions>10100</max-transactions>
<max-unique-name-statistics>500</max-unique-name-statistics>
<max-resource-requests-on-server>50</max-resource-requests-on-server>
<max-resource-unavailable-millis>1800000</max-resource-unavailable-millis>
<recovery-threshold-millis>300000</recovery-threshold-millis>
<max-transactions-health-interval-millis>
60000
</max-transactions-health-interval-millis>
<purge-resource-from-checkpoint-interval-seconds>
86400
</purge-resource-from-checkpoint-interval-seconds>
<checkpoint-interval-seconds>300</checkpoint-interval-seconds>
<parallel-xa-enabled>true</parallel-xa-enabled>
<unregister-resource-grace-period>30</unregister-resource-grace-period>
<security-interop-mode>default</security-interop-mode>
<rmi-service-name>RMI_ce1</rmi-service-name>
</transaction-manager>
Use the use-secure-conditions element to configure whether or not the Oracle Event Processing server uses secure connections. This element has the following child elements and no attributes.
Table 7-29 Child Elements of: use-secure-connections
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Whether or not to use secure connections. Valid values:
|
The following example shows how to use the use-secure-connections element in the Oracle Event Processing server configuration file:
<use-secure-connections>
<name>myUseSecConn</name>
<value>true</value>
</use-secure-connections>
Use the weblogic-instances element to configure Oracle Event Processing server instances for a weblogic-jta-gateway element. This element has the following child elements and no attributes.
|
Table 7-30 Child Elements of: weblogic-instances
|
The following example shows how to use the weblogic-instances element in the Oracle Event Processing server configuration file:
<weblogic-jta-gateway>
<name>myJTAGateway</name>
<timeout-seconds>90</timeout-seconds>
<weblogic-instances>
<weblogic-instance>
<domain-name>ocep_domain</domain-name>
<server-name>fxserver</server-name>
<protocol>t3</protocol>
<host-address>ariel</host-address>
<port>9002</port>
</weblogic-instance>
</weblogic-instances>
</weblogic-jta-gateway>
Use the weblogic-jta-gateway element to configure the attributes for the singleton Oracle Event Processing server client JTA gateway service. This element has the following child elements and no attributes.
The following example shows how to use the weblogic-jta-gateway element in the Oracle Event Processing server configuration file. In the example, the weblogic-jta-gateway element's unique identifier is myJTAGateway.
<weblogic-jta-gateway>
<name>myJTAGateway</name>
<timeout-seconds>90</timeout-seconds>
<weblogic-instances>
<weblogic-instance>
<domain-name>ocep_domain</domain-name>
<server-name>fxserver</server-name>
<protocol>t3</protocol>
<host-address>ariel</host-address>
<port>9002</port>
</weblogic-instance>
</weblogic-instances>
</weblogic-jta-gateway>
Use the weblogic-rmi-client element to configure the attributes for the singleton Oracle Event Processing server RMI client. This element has the following child elements and no attributes.
|
Table 7-31 Child Elements of: weblogic-rmi-client
|
The following example shows how to use the weblogic-rmi-client element in the Oracle Event Processing server configuration file. In the example, the weblogic-rmi-client element's unique identifier is wlclient.
<netio-client>
<name>netio</name>
<provider-type>NIO</provider-type>
</netio-client>
<netio-client>
<name>netiossl</name>
<provider-type>NIO</provider-type>
<ssl-config-bean-name>sslConfig</ssl-config-bean-name>
</netio-client>
<weblogic-rmi-client>
<name>wlclient</name>
<netio-name>netio</netio-name>
<secure-netio-name>netiossl</secure-netio-name>
</weblogic-rmi-client>
Use the work-manager element to configure a work manager on the Oracle Event Processing server.
|
Table 7-32 Child Elements of: work-manager
|
The following example shows how to use the work-manager element in the Oracle Event Processing server configuration file. In the example, the work-manager element's unique identifier is WM.
<work-manager>
<name>WM</name>
<fairshare>5</fairshare>
<min-threads-constraint>1</min-threads-constraint>
<max-threads-constraint>4</max-threads-constraint>
</work-manager>
Use the xa-params element to specify distributed transaction-related data-source parameters. This element has the following child elements and no attributes.
Table 7-33 Child Elements of: xa-params
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Enables the server to associate the same XA database connection from the connection pool with a global transaction until the transaction completes. Only applies to connection pools that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers. Default: |
|
|
|
The number of seconds to set as the transaction branch timeout. If set, this value is passed as the transaction timeout value in the Default: 0. |
|
|
|
Enables the server to call Default: |
|
|
|
Determines the duration in seconds for which the transaction manager will perform recover operations on the resource. A value of zero indicates that no retries will be performed. Default: 60. |
|
|
|
Enables the server to set a transaction branch timeout based on the value for Default: |
|
|
|
Enables the server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool. Select this option if the XA driver used to create database connections or the DBMS requires that a logical JDBC connection be kept open while transaction processing continues (although the physical XA connection can be returned to the connection pool). Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers. Default: |
|
|
|
Enables JTA resource health monitoring for an XA data source. When enabled, if an XA resource fails to respond to an XA call within the period specified in MaxXACallMillis, the server marks the data source as unhealthy and blocks any further calls to the resource. This property applies to XA data sources only, and is ignored for data sources that use a non-XA driver. Default: |
|
|
|
Specifies that a dedicated XA connection is used for commit and rollback processing for a global transaction. Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers. Default: |
|
|
|
Specifies that Default: |
|
|
|
The number of seconds between XA retry operations if XARetryDurationSeconds is set to a positive value. Default: 60. |
|
|
|
Specifies that the transaction manager calls recover on the resource only once. Only applies to data sources that use an XA driver. Use this setting to work around specific problems with JDBC XA drivers. Default: |
|
|
|
Specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so forth). Only applies to connection pools that use an XA driver. When enabled, SQL exceptions that are thrown while closing the JDBC objects without a transaction context will be suppressed. Use this setting to work around specific problems with JDBC XA drivers. Default: |
The following example shows how to use the xa-params element in the Oracle Event Processing server configuration file:
<data-source>
<name>orads</name>
<xa-params>
<keep-xa-conn-till-tx-complete>true</keep-xa-conn-till-tx-complete>
</xa-params>
<driver-params>
<url>jdbc:oracle:thin:@localhost:1521:ce102</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<element>
<name>user</name>
<value>wlevs</value>
</element>
<element>
<name>password</name>
<value>wlevs</value>
</element>
</properties>
</driver-params>
<connection-pool-params>
<initial-capacity>5</initial-capacity>
<max-capacity>10</max-capacity>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
<test-frequency-seconds>5</test-frequency-seconds>
</connection-pool-params>
<data-source-params>
<jndi-names>
<element>orads</element>
</jndi-names>
<global-transactions-protocol>None</global-transactions-protocol>
</data-source-params>
</data-source>