Introduction to Multi-Server Domains 5-5
domain directory. Additionally, the name of the servers and domain correspond to the name of the server directories and domain directory, respectively. This is by
convention only, and not required, although Oracle recommends you set up your domains this way for simplicity and consistency. If the servers of the multi-server
domain are located on different computers, you can replicate the directory structure on both computers, also for simplicity and consistency.
Figure 5–1 shows a multi-server domain directory with three servers.
Figure 5–1 Multi-Server Domain Directory Structure
The myServer1 configuration file snippet shows how the domain directory and domain object are configured with the same name, as well as the server directory and
server name. The domain directory is located in the ORACLE_CEP_HOMEuser_ projectsdomains directory, which is the default location for Oracle CEP domains.
5.5 Order of cluster Element Child Elements
The order of cluster element child elements in the config.xml file is important; if you include elements in the incorrect order you may encounter an error. The following
list describes the order in which you should list the child elements:
■
server-name
■
server-host-name: Specifies the host addressIP used for point-to-point HTTP multi-server communication. Default value is localhost.
If all the Oracle CEP servers in your multi-server domain are on the same host, this element is optional.
If one or more Oracle CEP servers in your multi-server domain are on different hosts, this element is mandatory if you plan to manage the multi-server domain
using the Oracle CEP Visualizer.
■
multicast-address: The multicast communication address. For Coherence well-known addressing WKA a unicast address can be used.
■
multicast-port: Optional. Specifies the port used for multicast traffic. Default value is 9001.
■
identity: Mandatory only for Oracle CEP native clustering; not used for Oracle Coherence.
■
enabled
■
security
■
groups
5-6 Oracle Complex Event Processing Administrators Guide
■
operation-timeout: Optional. Specifies, in milliseconds, the timeout for point-to-point HTTP multi-server requests. Default value is 30000.
For a complete description of the Oracle CEP server config.xml file cluster element, see cluster in the Oracle Complex Event Processing Developers Guide for
Eclipse.
5.6 High Availability and Multi-Server Domains
If you use Oracle Coherence clustering for your multi-server domain, you can take advantage of Oracle CEP high availability quality of service options. These options are
not supported using Oracle CEP native clustering.
For more information, see Understanding High Availability in the Oracle Complex Event Processing Developers Guide for Eclipse.
5.7 Scalability and Multi-Server Domains
Using either Oracle Coherence or Oracle CEP native clustering, you can take advantage of Oracle CEP scalability quality of service options.
For more information, see Understanding Scalability in the Oracle Complex Event Processing Developers Guide for Eclipse.
5.8 Next Steps
After creating your own Oracle CEP multi-server domain, consider the administration tasks that
Section 1.5, Understanding Oracle CEP Server Administration Tasks describes.
For example, you can:
■
Optionally configure the server. See
Section 1.3, Understanding Oracle CEP Server Configuration.
■
Create an Oracle CEP application. See Oracle Complex Event Processing Developers Guide for Eclipse for a description of
the programming model, details about the various components that make up an application, how they all fit together, and typical steps to create a new application.
■
Deploy your new, or existing, Oracle CEP application to the domain. For more information, see:
■
Section 8.1, Overview of Deploying an Application to an Oracle CEP Multi-Server Domain
■
Assembling and Deploying Oracle CEP Applications in the Oracle Complex Event Processing Developers Guide for Eclipse
■
Manage your applications, servers, and domains:
– Using the Oracle CEP Visualizer.
See Oracle Complex Event Processing Visualizer Users Guide.
– Using the wlevs.Admin command line tool.
See Appendix A, wlevs.Admin Command-Line Reference
. –
Using JMX and MBeans.
