This chapter provides a reference to the ocep_cluster_config.xsd schema. The ocep_cluster_config.xsd file describes the high availability clustering configuration elements and attributes
All of the high availability adapters are based on the basic adapter configuration and add elements specific to their type of adapter. See Component Element Hierarchies for the basic adapter elements. This section covers the elements specific to high availability adapters.
This chapter includes the following sections:
Use the ha-buffering-adapter element to create a high availability buffering adapter. This element has the following child elements:
The following example shows how to use these elements in a configuration file:
<ha:ha-buffering-adapter > <name>mySlidingWindowingAdapter</name> <window-length>15000</window-length> <warm-up-window-length units="minutes">6</warm-up-window-length> </ha:ha-buffering-adapter >
Use the ha-broadcast-adapter to create a high availability broadcast adapter. The element has the following child elements:
The following example shows how to use the trimming-interval element in a configuration file:
<ha:ha-broadcast-adapter> <name>myBroadcastAdapter</name> <trimming-interval units="events">10</trimming-interval> <warm-up-window-length units="minutes">6</warm-up-window-length> </ha:ha-broadcast-adapter>
Use the ha-correlating-adapter to create a high availability correlating adapter. This element has the following child elements:
The following example shows how to use the fail-over-delay element in a configuration file:
<ha:ha-correlating-adapter> <name>myHaBroadcastAdapter</name> <fail-over-delay>2000</fail-over-delay> </ha:ha-correlating-adapter>
Use the ha-inbound-adapter to create a high availability input adapter. This element has the following child elements:
The following example shows how to use the heartbeat and batch-size elements in a configuration file:
<ha:ha-inbound-adapter> <name>myHaInputAdapter</name> <heartbeat units="millis">1000</heartbeat> <batch-size>10</batch-size> </ha:ha-inbound-adapter>
batch-size: An integer value that indicates the number of events to send to the secondary server with the same time stamp. By default, batching is disabled (value 0).
fail-over-delay: The time in milliseconds that a secondary server waits to received a correlating message before considering the primary to have failed.
heartbeat: The value (n) for the heartbeat time out on this adapter. Oracle Event Processing generates a heartbeat after n time units of time go by without any event being generated on this adapter. The default time unit is nanoseconds.
trimming-interval: The interval at which Oracle Event Processing trims events from a secondary server buffer. Units are either events or milliseconds.
warm-up-window-length: The length of the warm-up window. Units can be in seconds (default) or minutes. The warm-up window is the length of time that a secondary server needs before it begins to produce valid output events after joining the cluster. Set the warm-up window long enough to allow the input windows of all Oracle CQL queries to be fully populated. By default, the length is 0 meaning no warm-up window.
window-length: The length of the warm-up window. Units can be in seconds (default), or minutes and type Long with units (seconds or minutes). The warm-up window is the length of time that a secondary server needs before it begins to produce valid output events after joining the cluster. Set the warm-up window length long enough to allow the input windows of all CQL queries to be fully populated. By default, the length is 0 seconds meaning there is no warm-up window.