Oracle SOA Stack 12.2.1.3

SOA Suite 12c has a new component: Oracle Enterprise Scheduler Service (ESS). ESS provides the ability to run different job types 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 Middleware Control. ESS was available as part of the Fusion Applications product offering. Now it is available in SOA Suite 12c. In this blog, I will demonstrate how to use a new Oracle extension, “Schedule Job”, in JDeveloper 12c to submit an ESS job request from a BPEL process.

Set up a scheduled job in Enterprise Scheduler Service

Create a SOA composite with a simple synchronous BPEL process, HelloFromMindTelligent.
Deploy HelloFromMindTelligent to SOA using Enterprise Manager.

Logon to Fusion Middleware Enterprise Manager.
Go to Scheduling Services -> ESSAPP -> Job Metadata -> Job Definitions. This takes you to the Job Definitions page.

Click the “Create” button, this takes you to Create Job Definition page. Enter:

Name: HelloFromMindTelligentJob

Display Name: HelloFromMindTelligentJob

Description: HelloFromMindTelligentJob

Job Type: SyncWebserviceJobType

Select Web service

Secure the Oracle Enterprise Scheduler Web Service

The ESS job cannot be run as an anonymous user, you need to attach a WSM security policy to the ESS Web Service:

In Fusion Middleware Enterprise Manager, go to Scheduling Services -> ESSAPP, right click, select “Web Services”.

In Web Service Details, click on the link “ScheduleServiceImplPort”.

Open tab “WSM Policies” and click on “Attach/Detach”.

In “Available Policies”, select “oracle/wss_username_token_service_policy”, click “Attach” button to attach the policy and then click on “Ok” to finish the policy attachment.

You should see the policy attached and enabled.

Create a SOA Composite to Submit a HelloFromHarvinderJOB

Create a new SOA Application/Project with an asynchronous BPEL (2.0) process, InvokeSchedulerJobMindTelligent, in JDeveloper 12c.

Create a SOA_MDS connection.

In the BPEL process, add Schedule Job Activity.
Open Schedule Job Activity
Double click on Schedule Job Activity

Choose HelloFromMindtelligentJob
Set Start Time as current date time, and click OK.

You may see this pop up message.

Click “Yes” to continue. In the next several steps we will replace WSDL URL with concrete binding on the reference binding later to fix this.
In EM, go to Scheduling Services -> Web Services.

Click on link “SchedulerServiceImplPort”

Click on link “WSDL Document SchedulerServiceImplPort”.

It launches a new browser window displaying the ESSWebService wsdl. WSDL URL is in the browser address.

Update EssService WSDL URL.

You need to attach WSM security policy to EssService request.

Add Security Policy: oracle/wss_username_token_client_policy.

Setting up the credential store for policy framework is beyond the scope of this blog. However, please ensure that CSF Map with valid credentials is attached.

After the composite is deployed, run the composite and check the Flow. A JOB ID is created

</requestId>

Go ESSAPP -> Job Requests -> Search Job Requests. Find Job 606. Job was executed successfully.

Click on the JOB Link

Summary

In this blog, we demonstrated how to set up a SOA web service ESS job and how to invoke ESS web service to submit a job request from BPEL process in SOA Suite 12c 12.2.1.3

SOA 12c 12.2.1.3. Send Error Notifications.

You can create error notification rules at the SOA Infrastructure or individual partition
level that cause an alert message to be triggered when specific fault criteria are met.

For example, you can create a rule that sends an alert if more than 10 errors occur in a
48 hour period.

The error notification rules provide the following benefits:

• An aggregated notification of faults occurring in the system.

• A scheduled-based notification system with a configurable re-occurrence interval. For example, send an alert every 24 hours if rule criteria are met.

• Rule-configured faults and notification channel specifications. When a fault policy is triggered, an email is sent. You can create fault notification rules at the following levels:

• SOA Infrastructure (for system-wide alerts) • Individual partition level (for alerts specific to that partition)

To create a Error Notification Rule, first create a scheduler

This will navigate to Schedules Page

Click on Create

Enter the name , display name ,package, Description, Frequency,Timezone, Start Date and click on OK. Only /oracle/apps/ess/custom/soa package can be used to create SOA Error Notification Rules