2 Introduction to Standalone-Server Domains

2.1 Overview of Oracle CEP Standalone-Server Domain Administration

An Oracle CEP standalone-server domain is a domain that contains a single Oracle CEP server. This is the type of domain created by default by the Configuration Wizard and is the starting point for a multi-server domain.

For more information, see:

• Section 1.1, "Understanding Oracle CEP Servers and Domains"

• Section 1.3, "Understanding Oracle CEP Server Configuration"

2.2 Scalability and Oracle CEP Standalone-Server Domain

Using a standalone-server domain, you can take advantage of some of the Oracle CEP scalability quality of service options.

To maximize scalability, consider a multi-server domain.

For more information, see:

• "Understanding Scalability" in the Oracle CEP Developer's Guide for Eclipse

• Chapter 5, "Introduction to Multi-Server Domains"

2.3 Next Steps

After creating your own Oracle CEP standalone-server domain, consider the administration tasks that Section 1.5, "Understanding Oracle CEP Server Administration Tasks" describes.

For example, you can:

• Create additional servers in the domain and configure the domain to be multi-server.

  See Chapter 5, "Introduction to Multi-Server Domains."

• Optionally configure the server.

  See Section 1.3, "Understanding Oracle CEP Server Configuration."

• Create an Oracle CEP application.

  See Oracle CEP Developer's 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 4.1, "Deploying an Application to an Oracle CEP Standalone-Server Domain"

  • "Assembling and Deploying Oracle CEP Applications" in the Oracle CEP Developer's Guide for Eclipse

• Manage your applications, servers, and domains:

  • Using the Oracle CEP Visualizer.

    See Oracle CEP Visualizer User's Guide.

  • Using the wlevs.Admin command line tool.

    See Appendix A, "wlevs.Admin Command-Line Reference".

  • Using JMX and MBeans.

    See Section 11.3, "Managing With JMX".