Installing and Verifying the Oracle Enterprise Scheduler Installation

3.1 Installing Oracle Enterprise Scheduler

Oracle Enterprise Scheduler does not have its own installer, but is installed by the installer of the embedding product such as Oracle SOA Suite.

Refer to the embedding product's installation documentation for details.

The IDE is installed by the Oracle SOA Quick Start for Developers which is described in Installing Oracle SOA Suite and Business Process Management for Developers. The installer installs the IDE and automatically configures it to Oracle JDeveloper. Before you run JDeveloper, make sure to set the variable MW_HOME to the middleware home location as required by the IDE.

The Oracle Enterprise Scheduler runtime component is installed by the design time or production installer of the embedding product (for example, Oracle SOA suite whose installation is described in Installing and Configuring Oracle SOA Suite and Business Process Management). The embedding product may automatically deploy Oracle Enterprise Scheduler, but if it does not, then it can be deployed using the “Oracle Enterprise Scheduler Service Basic" template to a server or cluster. The “Oracle Enterprise Manager Plugin for ESS" template can then be deployed for Oracle Enterprise Manager Fusion Middleware Control functionality.

3.1.1 Targeting Oracle Enterprise Scheduler During Domain Creation

When you extend SOA with Oracle Enterprise Scheduler, ess-server1 is created and by default the ESS-MGD-SVRS server group is targeted to ess_server1. You can use the following steps in the FMW Configuration Wizard to re-target Oracle Enterprise Scheduler to soa_server1:

Check ESS-MGD-SVRS for soa_server1
Uncheck ESS-MGD-SVRS for ess_server1
Delete ess_server1

See Creating WebLogic Domains Using the Configuration Wizard for more information about the wizard.

3.1.2 OWSM-PM Targeting With Oracle Enterprise Scheduler

OWSM-PM is intended to be targeted to just one server in a domain. To facilitate this requirement, Oracle Enterprise Scheduler templates no longer target OWSM-PM. If another product in the domain automatically targets OWSM-PM, then there is nothing to do. However, if there are no managed servers in the domain except for Oracle Enterprise Scheduler, or none of these servers has OWSM-PM, then OWSM-PM must be targeted manually.

3.1.2.1 Targeting OWSM-PM Manually

In the Fusion Middleware Configuration Wizard, select the Managed Servers, Clusters and Coherence check box as shown in Figure 3-1.

Figure 3-1 Fusion Middleware Configuration Wizard

Description of "Figure 3-1 Fusion Middleware Configuration Wizard"

On the Managed Server screen, for ess_server1, select the WSMPM-MAN-SVR server group. ESS-MGD-SVRS should already be selected.

3.2 Introduction to Verifying the Oracle Enterprise Scheduler Installation

The Oracle Enterprise Scheduler health check enables verifying the Oracle Enterprise Scheduler installation using a web browser.

The health check web page submits a simple scheduled job so as to verify that Oracle Enterprise Scheduler works as it should.

3.3 How to Verify the Oracle Enterprise Scheduler Installation Using a Browser

You can verify the installation of Oracle Enterprise Scheduler using a web browser.

Access the Java health check servlet in a web browser. Access to the health check page is available only to users with administrator privileges.

To verify the Oracle Enterprise Scheduler installation:

In a web browser, enter the following URL:
```
http://<hostName>:<port>/EssHealthCheck/checkHealth.jsp
```
where hostName is the server to which Oracle Enterprise Scheduler is installed and port is the port number.

To verify an Oracle Enterprise Scheduler cluster, use the following URL:
```
http://<hostName>:<port>/EssHealthCheck/diagnoseHealth.jsp
```
The Oracle Enterprise Scheduler Diagnostic Health Check page displays, as shown in Figure 3-2.

Figure 3-2 Diagnostic Health Check Page
Log in to the diagnostic servlet using an Oracle WebLogic Server administrator user name and password.
Click the Check Health button to verify the installation.

3.4 How to Programmatically Verify the Oracle Enterprise Scheduler Installation

You can programmatically access the health check servlet from your application to verify the Oracle Enterprise Scheduler installation.

Access to the health check page is available only to users with administrator privileges.

To programmatically verify the Oracle Enterprise Scheduler installation:

Access the following URL:
```
http://<hostName>:<port>/EssHealthCheck/checkHealth
```
where hostName is the server to which Oracle Enterprise Scheduler is installed and port is the port number.

Use the HTTP response codes to gauge the health of the Oracle Enterprise Scheduler installation, as shown in Table 3-1.

Table 3-1 HTTP Response Codes

Response Code Oracle Enterprise Scheduler Status Code Comments

Response Code	Oracle Enterprise Scheduler Status Code	Comments
`200(OK)`	Oracle Enterprise Scheduler is up and running.	The test job has been submitted and has succeeded within the default duration.
`202(ACCEPTED)`	Oracle Enterprise Scheduler is up and running but a delay in processing has occurred. A value of `202 (SC_ACCEPTED)` indicates to the client that the request is being acted upon but processing is not yet complete.	The test job has been submitted but has failed to complete within the default duration.
`500 (INTERNAL_SERVER_ERROR)`	The Oracle Enterprise Scheduler installation has errors.	An error has occurred during the submission or execution of the job.

200(OK)

Oracle Enterprise Scheduler is up and running.

The test job has been submitted and has succeeded within the default duration.

202(ACCEPTED)

Oracle Enterprise Scheduler is up and running but a delay in processing has occurred.

A value of 202 (SC_ACCEPTED) indicates to the client that the request is being acted upon but processing is not yet complete.

The test job has been submitted but has failed to complete within the default duration.

500 (INTERNAL_SERVER_ERROR)

The Oracle Enterprise Scheduler installation has errors.

An error has occurred during the submission or execution of the job.

3.5 What Happens at Runtime: How the Oracle Enterprise Scheduler Installation is Verified

The health check servlet schedules a job with Oracle Enterprise Scheduler as part of an HTTP request and waits for the job to either reach a terminal state, or run for 10 seconds

The health check servlet schedules a trivial job with Oracle Enterprise Scheduler as part of an HTTP request. After a few seconds, the servlet calls RuntimeServiceBean.getRequestState() to check the status of the job and constructs a response message within the servlet code. The servlet then returns a response indicating the success or failure of the job.

The servlet waits for the job to either reach a terminal state, or run for 10 seconds, whichever occurs first.

If the job reaches a terminal state in less than 10 seconds, the job results in a state of success.
If the job's terminal state does not change within 10 seconds, the job results in a state of success. However, the job is listed as not having been executed. This is because the system may be overloaded such that executing the job may take some time.
If any problems occur when submitting or executing the job, the job results in a state of failure.