SOA 12c - Oracle Enterprise Scheduler (Stopping and Starting ESS Application)

Here we go!
Information that you need to know:

About Oracle Enterprise Scheduler.
Enterprise applications require the ability to respond to many real-time transactions requested by online users or web services. However, they also require the ability to offload larger transactions to run at a future time or automate the running of application maintenance work based on a defined schedule. Oracle Enterprise Scheduler provides the ability to run different job types, including: Java, PL/SQL, and binary scripts, distributed across the nodes in an Oracle WebLogic Server cluster. Oracle Enterprise Scheduler runs these jobs securely, with high availability and scalability, with load balancing and provides monitoring and management through Fusion Applications Control. Oracle Enterprise Scheduler provides scheduling services for the following purposes:

  • To distribute job request processing across a grid of application servers,
  • To run Java, PL/SQL and binary process jobs,
  • To group job requests into job sets,
  • To schedule job requests based on recurrence expressions,
  • To administer job requests with Fusion Applications Control.

Oracle Enterprise Scheduler provides the critical requirements in a service-oriented environment to automate processes that must recur on a scheduled basis and to defer heavy processing to specific time windows. Oracle Enterprise Scheduler lets you:

  • Support sophisticated scheduling and workload management,
  • Automate the running of administrative jobs,
  • Schedule the creation and distribution of reports,
  • Schedule a future time for a step in a business flow for business process management.

Oracle Enterprise Scheduler provides features to manage the complete life cycle of a job definition: development, distribution, scheduling, and monitoring. Using Oracle JDeveloper, application developers can easily create job requests in their development environment. Application administrators and other users can specify when and where they want their job requests to run. Users and administrators can monitor how the job ran and access the end results of those jobs.

Customers that implement large systems typically have to manage a large number of diverse machines to handle the workload of their users. Oracle Enterprise Scheduler provides the ability to control how work is distributed to individual machines or groups of machines.

The ESSAPP application module is deployed to the ESS managed server, allowing you to control the starting/stopping of job scheduling and processing. The application module also provides an interface to view and edit job definitions, search for job requests, set up purge polices, and so on. Oracle Enterprise Manager Fusion Middleware Control can be used to conveniently start/stop an ESS instance.

For more detailed information read the following URLs:
https://docs.oracle.com/cd/E15586_01/fusionapps.1111/e10142/intro1.htm#BGBIGEFC
https://docs.oracle.com/middleware/1213/ess/administer-scheduler/GUID-A7FBE88B-8E78-4424-97A9-BC12EBB86B5A.htm#ESSAG4108

In this post, we will learn how Shut Down and Start Up the ESS Application

1.- The first step is Log in to Oracle Enterprise Manager.

For example:
 

2.- The second step, we are going to click on Target Navigation button, next click on Scheduling Services, and then Select the ESSAPP.

For example:
 

3.- The third step, we are going to click on Shut Down, then again Shutdown button.

For example:
 
 Operation Logs

Validate Shutdown operation on target /YourDomain/YourServerName/ESSAPP
------------------------------------------------
Perform Shutdown operation on target /YourDomain/YourServerName/ESSAPP
Invoking stop operation on targets YourServerName.
------------------------------------------------
Checking operation status on target /YourDomain/YourServerName/ESSAPP
Checking operation status on target Shutdown
Status of Shutdown operation on target /YourDomain/YourServerName/ESSAPP is STATE_RUNNING
[Deployer:149192]Operation "stop" on application "ESSAPP" is in progress on "YourServerName".
Status of Shutdown operation on target /YourDomain/YourServerName/ESSAPP is STATE_RUNNING
[Deployer:149192]Operation "stop" on application "ESSAPP" is in progress on "YourServerName".
Status of Shutdown operation on target /YourDomain/YourServerName/ESSAPP is STATE_RUNNING
[Deployer:149192]Operation "stop" on application "ESSAPP" is in progress on "YourServerName".
Status of Shutdown operation on target /YourDomain/YourServerName/ESSAPP is STATE_COMPLETED
[Deployer:149194]Operation "stop" on application "ESSAPP" has succeeded on "YourServerName".

4.- After the shut down operation was completed, the ESS application should has the next appearance.

For example:
 

5.- The last step, we are going to click on Start Up.

For example: 

Operation Logs 

Validate Start Up operation on target /YourDomain/YourServerName/ESSAPP
------------------------------------------------
Perform Start Up operation on target /YourDomain/YourServerName/ESSAPP
Invoking start operation on targets YourServerName.
------------------------------------------------
Checking operation status on target /YourDomain/YourServerName/ESSAPP
Checking operation status on target Start Up
Status of Start Up operation on target /YourDomain/YourServerName/ESSAPP is STATE_RUNNING
Status of Start Up operation on target /YourDomain/YourServerName/ESSAPP is STATE_COMPLETED
[Deployer:149192]Operation "start" on application "ESSAPP" is in progress on "YourServerName".
[Deployer:149194]Operation "start" on application "ESSAPP" has succeeded on "YourServerName".


Comments

Post a Comment

Popular posts from this blog

SOA 12c - Fault Handling (Creating Fault Policies and Fault Bindings)

Image
Here we go! Information that you need to know: Using Fault Handling in a BPEL Process. Fault handling allows a BPEL process service component to handle error messages or other exceptions returned by outside web services, and to generate error messages in response to business or runtime faults. For more detailed information read the following URLs: https://docs.oracle.com/cloud/latest/soa121300/SOASE/GUID-FE546F09-E9DF-4859-AEF6-A1C7A3F40C75.htm#SOASE478 Fault management framework is used to catch faults and perform user-specified actions defined in a fault policy file. In SOA Suite 12c we have a wizard to create fault policies and fault binding files. In this post, we will learn how to add a Fault Policy in an SOA project. We need to start the JDeveloper IDE. Click on File menu, then click on New option, followed immediately by Application option. For Example: Then on the New Gallery window, choose Applications option in General Category, then choose SOA Application ...
Read more

SOA 12c - DB Adapter (Poll for New or Changed Records in a Table)

Image
Here we go! Information that you need to know: Polling Strategies The inbound receive enables you to listen to and detect events and changes in the database, which in turn can be the initiators of a business process. This is not a one-time action, but rather an activation. A polling thread is started, which polls a database table for new rows or events. Whenever a new row is inserted into the MOVIES table, the polling operation raises it to the SCA Run Time. The strategy is to poll every record once. The initial SELECT has to be repeated over time, to receive the rows that exist at the start and all new rows as they are inserted over time. However, a new row once read is not likely to be deleted, and therefore can possibly be read repeatedly with each polling. The various ways to poll for events, called polling strategies, also known as after-read strategies or publish strategies, range from simple and intrusive to sophisticated and nonintrusive. Each strategy employs a dif...
Read more

SOA 12c - DB Adapter (Perform an Operation on a Table)

Image
Here we go! Information that you need to know: Data manipulation language (DML) operations align with basic SQL INSERT , UPDATE , and SELECT operations. SQL INSERT , UPDATE , DELETE , and SELECT are all mapped to Web Service operations of the same name. The MERGE is either an INSERT or UPDATE , based on the results of an existence check. A distinction is made between the data manipulation operations—called outbound writes—and the SELECT operations—called outbound reads. The connection between the Web Service and the SQL for merge (the default for outbound write) and queryByExample are not as obvious as for basic SQL INSERT , UPDATE , and SELECT . For more detailed information read the following URL: https://docs.oracle.com/cd/E28280_01/integration.1111/e10231/adptr_db.htm#CHDFGBGD In this post, we will learn how create a SOA Project with Database Adapter - Operation Type: Perform an Operation on a Table The next images are the SOA Project execution: We are going...
Read more