This appendix provides a reference to elements of the welvs_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 appendix 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
The following sample Oracle Event Processing server configuration file from the HelloWorld application shows how to use many of the Oracle Event Processing elements:
<?xml version="1.0" encoding="UTF-8"?>
<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">
<domain>
<name>WLEventServerDomain</name>
</domain>
<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>
<rmi-jrmp-port>9999</rmi-jrmp-port>
<jndi-service-name>JNDI</jndi-service-name>
<rmi-registry-port>9004</rmi-registry-port>
</jmx>
<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>
<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>
<!-- Sample cluster configuration -->
<!--
<cluster>
<server-name>myServer</server-name>
<multicast-address>239.255.0.1</multicast-address>
<enabled>coherence</enabled>
<security>none</security>
<groups></groups>
</cluster>
-->
<logging-service>
<name>myLogService</name>
<log-file-config>myFileConfig</log-file-config>
<stdout-config>myStdoutConfig</stdout-config>
<logger-severity>Notice</logger-severity>
<!-- logger-severity-properties is used to selectively enable logging for
individual categories -->
<!--logger-severity-properties>
<entry>
<key>org.springframework.osgi.extender.internal.dependencies.startup</key>
<value>Debug</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>
Use this element to configure an authorization constraint for a channel-constraints element.
For more information on channels, see channels.
The auth-constraint server configuration element supports the child elements that Table F-1 lists
Table F-1 Child Elements of: auth-constraint
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The description of the role. |
|
|
|
A valid role name. "Users, Groups, and Roles" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing |
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 this element to configure the default event store provider that uses a Berkeley database instance.
Optionally, you may configure Oracle Event Processing server to use a relational database instance as the event store provider as Section F.32, "rdbms-event-store-provider" describes.
The bdb-config server configuration element supports the child elements that Table F-2 lists
Table F-2 Child Elements of: bdb-config
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Specifies the subdirectory in which Oracle Event Processing server creates Berkeley database instances relative to the Default: |
|
|
|
Specifies the amount of memory, in bytes, available for Berkeley database cache entries. You can adjust the cache size to tune Berkeley database performance. For more information, see: Default: |
Use this 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
The channels server configuration element contains 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.
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 this element to configure one or more channel constraints for a pubsub-bean element.
For more information on channels, see channels.
The channel-constraints server configuration element contains one or more element child element that each support the following child elements:
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 this element to configure one or more channel resource collections for a channel-constraints element.
For more information on channels, see channels.
The channel-resource-collection server configuration element contains zero or more element child elements that support the child elements that Table F-3 lists
Table F-3 Child Elements of: channel-resource-collection
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this channel resource. |
|
|
|
Description of this channel resource collection. This element contains an |
|
|
|
Specifies a channel pattern. This element contains an |
|
|
|
Specifies the operation to channel, validate values include:
This element contains an |
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 this element to configure a cluster component in the Oracle Event Processing server.
For more information, see "Administrating Multi-Server Domains With Oracle Event Processing Native Clustering" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing.
The cluster server configuration element supports the child elements that Table F-4 lists.
Table F-4 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 multi-server 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 multi-server 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. For more information, see "Groups" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing. |
|
|
|
Specifies, in milliseconds, the timeout for point-to-point HTTP multi-server 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>
In the example, the cluster element's unique identifier is MyCluster.
Use this element to specify connection pool-related data-source parameters.
The connection-pool-params server configuration element supports the child elements that Table F-5 lists.
Table F-5 Child Elements of: connection-pool-params
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The time after which a statement currently being executed will time out. Default: -1. |
|
|
|
The number of seconds between diagnostic profile harvest operations. Default: 300. |
|
|
|
The number of inactive seconds on a reserved connection before the connection is reclaimed and released back into the connection pool. Default: 0. |
|
|
|
The number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand. Default: 900. |
|
|
|
Specifies the absolute name of the application class used to intercept method calls to the JDBC driver. The application specified must implement the |
|
|
|
The number of seconds within a connection use that the server trusts that the connection is still viable and will skip the connection test, either before delivering it to an application or during the periodic connection testing process. Default: 10. |
|
|
|
This option can improve performance by enabling execute threads to keep a pooled database connection even after the application closes the logical connection. Default: |
|
|
|
Test a connection before giving it to a client. Requires that you specify Default: |
|
|
|
Specifies that type of profile data to be collected. |
|
|
|
The algorithm used for maintaining the prepared statements stored in the statement cache. Valid values:
Default: |
|
|
|
The number of seconds after which a call to reserve a connection from the connection pool will timeout. When set to 0, a call will never timeout. When set to -1, a call will timeout immediately. Default: -1. |
|
|
|
Enables the server to set a light-weight client ID on the database connection based on a map of database IDs when an application requests a database connection. Default: |
|
|
|
The number of seconds to delay before creating each physical database connection. This delay supports database servers that cannot handle multiple connection requests in rapid succession. The delay takes place both during initial data source creation and during the lifetime of the data source whenever a physical database connection is created. Default: 0. |
|
|
|
The name of the database table to use when testing physical database connections. This name is required when you specify |
|
|
|
The number of prepared and callable statements stored in the cache between 1 and 1024. This may increase server performance. Default: 10. |
|
|
|
SQL statement to execute that will initialize newly created physical database connections. Start the statement with |
|
|
|
The number of seconds between attempts to establish connections to the database. If you do not set this value, data source creation fails if the database is unavailable. If set and if the database is unavailable when the data source is created, the server will attempt to create connections in the pool again after the number of seconds you specify, and will continue to attempt to create the connections until it succeeds. When set to 0, connection retry is disabled. Default: 0. |
|
|
|
The number of seconds between when the server tests unused connections. (Requires that you specify a Test Table Name.) Connections that fail the test are closed and reopened to re-establish a valid physical connection. If the test fails again, the connection is closed. In the context of multi data sources, this attribute controls the frequency at which the server checks the health of data sources it had previously marked as unhealthy. When set to 0, the feature is disabled. Default: 120. |
|
|
|
Specifies the JDBC debug level for XA drivers. Default: 10. |
|
|
|
The number of physical connections to create when creating the connection pool in the data source. If unable to create this number of connections, creation of the data source will fail. Default: 1. |
|
|
|
The maximum number of physical connections that this connection pool can contain. Default: 15. |
|
|
|
The number of connections created when new connections are added to the connection pool. Default: 1. |
|
|
|
The maximum number of connection requests that can concurrently block threads while waiting to reserve a connection from the data source's connection pool. Default: |
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 this element to configure Oracle CQL-specific options in the Oracle Event Processing server.
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>
In the example, the cql element's unique identifier is myCQL.
This configuration type defines configuration for a DataSource service.
The data-source server configuration element supports the following child elements:
The following example shows how to use the data-source element in the Oracle Event Processing server configuration file:
<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>
In the example, the data-source element's unique identifier is orads.
Use this element to specify data source-related data-source parameters.
The data-source-params server configuration element supports the child elements that Table F-6 lists.
Table F-6 Child Elements of: data-source-params
| XML Tag | Type | Description |
|---|---|---|
|
|
See Description |
The algorithm determines the connection request processing for the multi data source. Valid values:
Default: |
|
|
|
Specifies the data chunk size for steaming data types between 1 and 65536. Default: 256. |
|
|
|
Specifies whether or not multiple rows to be prefetched (that is, sent from the server to the client) in one server access. Default: |
|
|
|
The list of data sources to which the multi data source will route connection requests. The order of data sources in the list determines the failover order. |
|
|
|
For multi data sources with the Failover algorithm, enables the multi data source to failover connection requests to the next data source if all connections in the current data source are in use. Default: |
|
|
|
If row prefetching is enabled, specifies the number of result set rows to prefetch for a client between 2 and 65536. Default: 48. |
|
|
See Description |
The JNDI path to where this Data Source is bound. By default, the JNDI name is the name of the data source. This element contains the following child elements:
|
|
|
|
Specifies the scoping of the data source. Note that Default: |
|
|
|
The name of the application class to handle the callback sent when a multi data source is ready to failover or fail back connection requests to another data source within the multi data source. The name must be the absolute name of an application class that implements the |
|
|
|
Determines the transaction protocol (global transaction processing behavior) for the data source. Valid values:
Default: |
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 this element to specify JDBC driver-related data-source parameters.
The driver-params server configuration element supports the child elements that Table F-7 lists.
Table F-7 Child Elements of: driver-params
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Specifies that the server should use the XA interface of the JDBC driver. If the JDBC driver class used to create database connections implements both XA and non-XA versions of a JDBC driver, you can set this attribute to indicate that the server should treat the JDBC driver as an XA driver or as a non-XA driver. Default: |
|
|
|
The password attribute passed to the JDBC driver when creating physical database connections. |
|
|
|
The full package name of JDBC driver class used to create the physical database connections in the connection pool in the data source. |
|
|
|
The URL of the database to connect to. The format of the URL varies by JDBC driver. The URL is passed to the JDBC driver to create the physical database connections. |
|
|
|
Specifies the list of properties passed to the JDBC driver when creating physical database connections. This element contains one or more
|
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 this element to configure a domain name in the Oracle Event Processing server.
Use this element to configure one or more debug properties for the Oracle Event Processing server.
The debug server configuration element supports the child elements that Table F-8 lists.
Table F-8 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 For more information including a full list of all debug flags, see "How to Configure Oracle Event Processing Debugging Options Using a Configuration File" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing |
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 this element to configure an event store for the Oracle Event Processing server.
The event-store server configuration element supports the child elements that Table F-9 lists.
Table F-9 Child Elements of: event-store
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Specifies the name of one or more For more information, see: |
The following example shows how to use the event-store element in the Oracle Event Processing server configuration file:
<config>
<event-store>
<name>myEventStore</name>
<provider-order>
<provider>provider1</provider>
<provider>provider2</provider>
</provider-order>
</event-store>
</config>
In the example, the adapter's unique identifier is myEventStore.
This configuration type is used 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.
The exported-jndi-context server configuration element supports the child elements that Table F-10 lists.
Table F-10 Child Elements of: exported-jndi-context
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The name of the RMI service that should be used to serve this JNDI context over the network. It must match an existing RMI object in the configuration. For more information, see |
The following example shows how to use the exported-jndi-context element in the Oracle Event Processing server configuration file:
<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>
In the example, the adapter's unique identifier is RemoteJNDI.
Use this element to configure an HTTP publish-subscribe service.
The http-pubsub server configuration element supports the following child elements:
The following example shows how to use the http-pubsub 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>
In the example, the http-pubsub element's unique identifier is myPubsub.
Use this element to configure an instance of the Jetty HTTP server.
The jetty server configuration element supports the child elements that Table F-11 lists.
Table F-11 Child Elements of: jetty
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The name of the Network I/O service that should be used. This also defines which port the server listens on. This parameter must refer to the name of a valid "netio" configuration object. |
|
|
|
The name of the Work Manager that should be used for thread pooling. If this parameter is not specified, then Jetty will use a default work manager. For more information, see |
|
|
|
The name of a directory where temporary files required for Web applications, JSPs, and other types of Web artifacts are kept. This parameter is overridden by the |
|
|
|
Enable debugging in the Jetty code. Specified debug messages are logged the same way as all other |
|
|
|
The name of the network port that should be set. This parameter may not be set if the |
|
|
|
The name of the Network I/O service that should be used for secure communications. The specified service must be configured to support SSL encryption. This parameter must refer to the name of a valid |
The following example shows how to use the jetty element in the Oracle Event Processing server configuration file:
<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>
In the example, the jetty element's unique identifier is TestJetty.
Use this 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.
The jetty-web-app server configuration element supports the child elements that Table F-12 lists.
Table F-12 Child Elements of: jetty-web-app
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The context path where this web app will be deployed in the web server's name space. Default: |
|
|
|
The location where Jetty should store temporary files for this web app. This parameter overrides the |
|
|
|
A file name that points to the location of the web app on the server. It may be a directory or a WAR file. |
|
|
|
The name of the Jetty service where this Web application should be deployed. This name must match the name of an existing |
The following example shows how to use the jetty-web-app element in the Oracle Event Processing server configuration file:
<jetty-web-app>
<name>financial</name>
<context-path>/financial</context-path>
<path>../testws2/financialWS.war</path>
<jetty-name>TestJetty</jetty-name>
</jetty-web-app>
In the example, the jetty-web-app element's unique identifier is financial.
Use this element to configure Java Management Extension (JMX) properties in the Oracle Event Processing server.
The jmx server configuration element supports the child elements that Table F-13 lists.
Table F-13 Child Elements of: jmx
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The name of the RMI service that should be used to serve this JNDI context over the network. It must match an existing RMI object in the configuration. For more information, see |
|
|
|
The name of the JNDI service to which the JMX server will bind its object. |
The following example shows how to use the jmx element in the Oracle Event Processing server configuration file:
<jmx>
<name>myJMX</name>
<jndi-service-name>JNDI</jndi-service-name>
<rmi-service-name>RMI</rmi-service-name>
</jmx>
In the example, the jmx element's unique identifier is myJMX.
This configuration object is used 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.
The jndi-context server configuration element supports the child elements that Table F-14 lists.
Table F-14 Child Elements of: jndi-context
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
This parameter defaults to |
Use this element to configure logging to a file on the Oracle Event Processing server.
The log-file server configuration element supports the child elements that Table F-15 lists.
Table F-15 Child Elements of: log-file
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Determines whether old rotated files need to be kept around forever. Default: |
|
|
|
Determines how the log file rotation will be performed based on size, time or not at all. Valid values:
Default: |
|
|
|
The time in Default: 00:00. |
|
|
|
If old rotated files are to be deleted, this parameter determines how many of the last files to always keep. Default: 7. |
|
|
|
The size threshold at which the log file is rotated in KB. Default: 500. |
|
|
|
The factor that is applied to the timespan to arrive at the number of milliseconds that will be the frequency of time based log rotations. Default: ( |
|
|
|
The interval for every time based log rotation. Default: 24. |
|
|
|
Log file name. Default: |
|
|
|
Specifies whether the log file will be rotated on startup. Default: |
|
|
|
Specifies the threshold importance of the messages that are propagated to the handlers. The default is
Default: |
|
|
|
The directory where the old rotated files are stored. If not set, the old files are stored in the same directory as the base log file. |
The following example shows how to use the log-file element in the Oracle Event Processing server configuration file:
<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>
In the example, the log-file element's unique identifier is logFile.
Use this element to configure logging to standard out (console) on the Oracle Event Processing server.
The log-stdout server configuration element supports the child elements that Table F-16 lists.
Table F-16 Child Elements of: log-stdout
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Determines the number of stack trace frames to display on standard out. All frames are displayed in the log file. A value of -1 means all frames are displayed. Default: -1. |
|
|
|
Specifies whether to dump stack traces to the console when included in a logged message. Default: |
|
|
string |
Defines the threshold importance of the messages that are propagated to the handlers. The default is
Default: |
Use this element to configure a logging service on the Oracle Event Processing server.
The logging-service server configuration element supports the child elements that Table F-17 lists.
Table F-17 Child Elements of: logging-service
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The configuration of the log file and its rotation policies. |
|
|
|
The configuration of the stdout output. |
|
|
|
Defines the threshold importance of the messages that are propagated to the handlers. The default is
Default: |
|
|
See Description |
The Severity values for different nodes in the Logger tree composed of one or more |
The following example shows how to use the logging-service element in the Oracle Event Processing server configuration file:
<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>
In the example, the logging-service element's unique identifier is myLogService.
Use this element to configure one or more message filters for a pubsub-bean element.
The message-filters server configuration element contains one or more element child elements that each contain a message-filter-name and message-filter-class child element.
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 this element to declare a unique identifier for an Oracle Event Processing server configuration element.
Use this element to represent a network input/output (IO) service, that may be used by other services to act as the server for network IO.
The netio server configuration element supports the child elements that Table F-18 lists.
Table F-18 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. For a list of the valid provider types, see "Network IO Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing. |
|
|
|
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 |
Use this 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.
The netio-client server configuration element supports the child elements that Table F-19 lists.
Table F-19 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. For a list of the valid provider types, see "Network IO Providers" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing. |
The following example shows how to use the netio-client element in the Oracle Event Processing server configuration file:
<netio-client>
<name>netiossl</name>
<ssl-config-bean-name>sslConfig</ssl-config-bean-name>
<provider-type>NIO</provider-type>
</netio-client>
In the example, the netio-client element's unique identifier is netiossl.
Use this element to define the maximum capacity of a query partition when the ordering-constraint attribute is set to PARTITION_ORDERED. Set this 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 element's default value is 4.
For more information, including best practices and information on the locations where this value can be set (including their precedence), see "Using partition-order-capacity with Partitioning Queries" in Chapter 17, "Querying an Event Stream with Oracle CQL".
Use this element to configure the path for an http-pubsub element.
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 this element to configure a publish-subscribe bean for an http-pubsub element.
The pubsub-bean server configuration element supports the following child elements:
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 this 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 Section F.3, "bdb-config" describes.
The rdbms-event-store-provider server configuration element supports the child elements that Table F-20 lists.
Table F-20 Child Elements of: rdbms-event-store-provider
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The maximum time (in milliseconds) that the Oracle Event Processing server will wait for this provider to initialize. Default: 10000 ms. |
|
|
|
The name of a data source element. For more information, see |
|
|
See Description |
One or more |
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>
In the example, the rdbms-event-store-provider element's unique identifier is test-rdbms-provider.
Use this element to configure an RMI service, which allows server- side objects to be exported to remote clients.
The rmi server configuration element supports the child elements that Table F-21 lists.
Table F-21 Child Elements of: rmi
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The number of failed heartbeat attempts before triggering disconnect notifications to all registered listeners.Default-Value: 4. |
|
|
|
The name of the HTTP service that this service should use to register remote objects. The service may be provided by a Jetty or Tomcat instance of the same name. |
|
|
|
The time in milliseconds between heartbeats. Once the number of unsuccessful heartbeat attempts has reached the value specified by the Default-Value: 5000. |
Use this element to configure cql scheduler options in the Oracle Event Processing server.
The scheduler server configuration element supports the child elements that Table F-22 lists.
Table F-22 Child Elements of: scheduler
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Specify the value for one of the
Default: oracle.cep.execution.scheduler.RoundRobinScheduler |
|
|
|
Total number of seconds that the Oracle Event Processing Service Engine scheduler will run. Default: 1000000 ms. |
|
|
|
The frequency at which the Oracle Event Processing Service Engine scheduler executes Oracle CQL queries. Default: 1000 ms |
|
|
|
Whether or not the Oracle Event Processing Service Engine scheduler will use a separate thread. Options are:
|
Use this element to configure the server-specific properties of a pubsub-bean element.
The server-config server configuration element supports the child elements that Table F-23 lists.
Table F-23 Child Elements of: server-config
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
See Description |
This element contains one or more
For more information, see "How the HTTP Pub-Sub Server Works" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing. |
|
|
|
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 this element to configure the service properties of a pubsub-bean element.
The services server configuration element contains one or more element child elements that each support the child elements that Table F-24 lists.
Table F-24 Child Elements of: services
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Specifies a service channel, for example: |
|
|
|
Specifies the class to service this service, for example: |
|
|
|
Define a service method in the service class. The service method must have only one payload parameter of type |
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 this element to configure whether or not the Oracle Event Processing server uses secure connections.
The show-detail-error-message server configuration element supports the child elements that Table F-25 lists.
Table F-25 Child Elements of: show-detail-error-message
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Whether or not to show detailed error messages. Valid values:
|
The following example shows how to use the show-detail-error-message element in the Oracle Event Processing server configuration file:
<show-detail-error-message>
<name>myShowDetail</name>
<value>true</value>
</show-detail-error-message>
In the example, the show-detail-error-message element's unique identifier is myShowDetail.
Use this element to configure Secure Sockets Layer-specific properties on the Oracle Event Processing server.
The ssl server configuration element supports the child elements that Table F-26 lists.
Table F-26 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. For more information, see "FIPS" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing. |
|
|
|
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:
<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>
In the example, the ssl element's unique identifier is sslConfig.
Use this element to configure weblogic-jta-gateway default transaction timeout in seconds in the Oracle Event Processing server.
Default: 60.
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 this element to configure transaction manager properties in the Oracle Event Processing server.
The transaction-manager server configuration element supports the child elements that Table F-27 lists.
Table F-27 Child Elements of: transaction-manager
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Maximum number of concurrent requests to resources allowed for each server. Default: 50. |
|
|
|
Maximum duration in milliseconds that a resource is declared dead. After the duration, the resource will be declared available again, even if the resource provider does not explicitly re-register the resource.Default: 1800000. |
|
|
|
Specifies the security mode of the communication channel used for XA calls between servers that participate in a global transaction. All server instances in a domain must have the same security mode setting. Valid values:
Default: |
|
|
|
Execute XA calls in parallel if there are available threads. Default: |
|
|
|
The location of the file store that contains the transaction log. This attribute can be either an absolute or relative path in the filesystem. |
|
|
|
Maximum allowed duration of XA calls to resources. If a particular XA call to a resource exceeds the limit, the resource is declared unavailable. Default: 120000. |
|
|
|
The default transaction timeout in seconds. Default: 30. |
|
|
|
The interval at which the transaction manager performs transaction log checkpoint operations. Default: 300. |
|
|
|
Specifies whether the transaction manager will automatically perform an XAResource forget operation for heuristic transaction completions. When enabled, the transaction manager automatically performs an XA Resource Default: |
|
|
|
The maximum number of cycles that the transaction manager will perform the before completion synchronization callback processing. Default: 10. |
|
|
|
The transaction abandon timeout seconds for transactions in the second phase of the two-phase commit (prepared and later). During the second phase of the two-phase commit process, the transaction manager will continue to try to complete the transaction until all resource managers indicate that the transaction is completed. Using this timeout, you can set the maximum time that a transaction manager will persist in attempting to complete a transaction during the second phase of the transaction. After the abandon transaction timer expires, no further attempt is made to resolve the transaction. If the transaction is in a prepared state before being abandoned, the transaction manager will roll back the transaction to release any locks held on behalf of the abandoned transaction. Default: 86400. |
|
|
|
The interval at which internal objects used to serialize resource enlistment are cleaned up. Default: 30000. |
|
|
|
The grace period (number of seconds) that the transaction manager waits for transactions involving the resource to complete before unregistering a resource. The grace period can help minimize the risk of abandoned transactions because of an unregistered resource, such as a JDBC data source module packaged with an application. During the specified grace period, the unregisterResource call will block until the call can return, and no new transactions are started for the associated resource. If the number of outstanding transactions for the resource goes to 0, the unregisterResource call returns immediately. At the end of the grace period, if there are still outstanding transactions associated with the resource, the unregisterResource call returns and a log message is written on the server on which the resource was previously registered. Default: 30. |
|
|
|
The name of the RMI service that is used for distributed transaction coordination. For more information, see |
|
|
|
The maximum number of unique transaction names for which statistics will be maintained. Default: 1000. |
|
|
|
The interval that a particular resource must be accessed within for it to be included in the checkpoint record. Default: 86400. |
|
|
|
The maximum number of simultaneous in-progress transactions allowed on this server. Default: 10000. |
|
|
|
The interval that the checkpoint is done for the migrated transaction logs (TLOGs). Default: 60. |
|
|
|
The interval that recovery is attempted until the resource becomes available. Default: 300000. |
|
|
|
The interval for which the transaction map must be full for the JTA subsystem to declare its health as Default: 60000. |
|
|
|
The dispatch policy to use when performing XA operations in parallel. By default the policy of the thread coordinating the transaction is used. |
The following example shows how to use the transaction-manager element in the Oracle Event Processing server configuration file:
<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>
In the example, the transaction-manager element's unique identifier is My_tm.
Use this element to configure whether or not the Oracle Event Processing server uses secure connections.
For more information, see "How to Configure SSL in a Multi-Server Domain for Oracle Event Processing Visualizer" in the Oracle Fusion Middleware Administrator's Guide for Oracle Event Processing.
The use-secure-connections server configuration element supports the child elements that Table F-28 lists.
Table F-28 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>
In the example, the use-secure-connections element's unique identifier is myUseSecConn.
Use this element to configure Oracle Event Processing server instances for a weblogic-jta-gateway element.
The weblogic-instances server configuration element supports zero or more weblogic-instance child elements that each contain the child elements that Table F-29 lists.
Table F-29 Child Elements of: weblogic-instances
| XML Tag | Type | Description |
|---|---|---|
|
|
|
Specifies the name of the domain of the Oracle Event Processing server. |
|
|
|
Specifies the name of the Oracle Event Processing server. |
|
|
|
Specifies the JTA protocol. Default: |
|
|
|
The host name or IP address of the Oracle Event Processing server. |
|
|
|
The |
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 this element to configure the attributes for the singleton Oracle Event Processing server client JTA gateway service.
The weblogic-jta-gateway server configuration element supports the following child elements:
The following example shows how to use the weblogic-jta-gateway 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>
In the example, the weblogic-jta-gateway element's unique identifier is myJTAGateway.
Use this element to configure the attributes for the singleton Oracle Event Processing server RMI client.
The weblogic-rmi-client server configuration element supports the child elements that Table F-30 lists.
Table F-30 Child Elements of: weblogic-rmi-client
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
Specifies the name of the |
|
|
|
Specifies the name of the |
The following example shows how to use the weblogic-rmi-client element in the Oracle Event Processing server configuration file:
<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>
In the example, the weblogic-rmi-client element's unique identifier is wlclient.
Use this element to configure a work manager on the Oracle Event Processing server.
The work-manager server configuration element supports the child elements that Table F-31 lists.
Table F-31 Child Elements of: work-manager
| XML Tag | Type | Description |
|---|---|---|
|
|
|
The name of this |
|
|
|
The minimum threads constraint this work manager should use. Default: -1. |
|
|
|
The fairshare value this work manager should use. Default: -1. |
|
|
|
The maximum threads constraint this work manager should use. Default: -1. |
The following example shows how to use the work-manager element in the Oracle Event Processing server configuration file:
<work-manager>
<name>WM</name>
<fairshare>5</fairshare>
<min-threads-constraint>1</min-threads-constraint>
<max-threads-constraint>4</max-threads-constraint>
</work-manager>
In the example, the work-manager element's unique identifier is WM.
Use this element to specify distributed transaction-related data-source parameters.
The xa-params server configuration element supports the child elements that Table F-32 lists.
Table F-32 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>