New in SOA Suite 12c: Enterprise Scheduler

SOA Suite 12c has a new component added. This component is called Oracle Enterprise Scheduler (ESS for short). This is a powerful Scheduler component that is a key part of Fusion Applications and now has been added to SOA Suite. It is automatically installed when you install SOA Suite or Service Bus. Deployment of ESS is optional in both SOA Suite and Service Bus, but customers are strongly advised to atleast always deploy it with SOA Suite since a number of features in SOA Suite depends on it and these features are disabled if ESS is not deployed. ESS can be deployed to the SOA or Service Bus server/cluster or to a separate server/cluster in the domain. ESS is also part of MFT.

ESS can be used to schedule SOA Suite composites and Service Bus proxy services. Composites can be scheduled in two ways. One is to have a composite with a web service interface be executed at the scheduled time by ESS. The second is for a composite with an inbound polling adapter to be scheduled to process messages only between scheduled times. Also Service Bus proxy services with a web service interface can be executed at the scheduled time by ESS. ESS is also used in SOA Suite for the following:

  • Schedule periodic notifications for faulted instances that meet the selection criteria in the error hospital.

  • Schedule or execute immediate in the background long running job to recover instances in the error hospital in bulk that meet the selection criteria.

  • Schedule a user created script.

  • Submit a job from BPEL. 

Schedules can be execute immediately in the background, run once at a future time, or at a recurring schedule. Job definitions must first be created so ESS knows how to invoke the job implementation. Then a job has to be submitted and tied to a schedule. Lastly at the scheduled time the job implementation is invoked.

ESS has powerful features for job and resource management. Enterprise Manager Fusion Middleware Control (EM FMWC)  provides full management and visibility to ESS jobs and job outputs, UI to create job metadata and UI to submit jobs. You can do all of the following with ESS.

  • Support for job dependencies and incompatibilities. Examples: run import job before report job, ensure that a payroll job does not run at the same time as a salary increase job.

  • Parellel execution of sub jobs. Example: parallel process payroll for a large # of employees into “sub jobs”,one for each letter of the alphabet

  • Throttling and Prioritization. Examples: No more than 70 Financials jobs should run concurrently, A newly submitted CRM job should not wait for 5,000 backed up Financials jobs to execute.

  • Targeting of jobs to machines during time windows. Examples: machines X, Y and Z are reserved the last 5 days of every quarter for end of quarter processing jobs, timecard job should run on machine X from 9am-5pm PST and different machine at night

ESS has a rich set of java APIs. However direct use of these API’s is not supported for first release. Customers can use Enterprise Manager Fusion Middleware Control (EM FMWC) or WLST or the ESS web service interface to interact with ESS. Also java jobs and PLSQL jobs, while supported in ESS are not supported at this time for SOA customers. For java jobs, use a web service as the job implementation instead and for PLSQL, use the DB scheduler or schedule a composite that uses the DB adapter to invoke the PLSQL procedure.


This is great news. My hope is that in the future ESS will be able to schedule and run various purge activities since this is an area that customers frequently neglect and can have a big impact on performance.

Posted by Jim on September 03, 2014 at 08:45 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Find Us on facebook Follow us on twitter Oracle SOA Suite forum
SOA PM team
Welcome to the Oracle SOA Suite team blog. We'll use this site for news and information that did not make it into our official documentation for a reason or another.


« May 2015