How to make a Job Scheduler in Oracle ESS

Create a scheduling job for a SOAP Service using ESS

The Job shown in the demo here was created in JDeveloper Studio Edition Version 12.2.1.1.0 and
Fusion Middleware ESS 12.2.1.1.0.

Create new Application and new Project as per the screenshots below. Provide valid package directory during creation.


Prerequisite -- This article is for developers who already have knowledge on Integration and little experience with Oracle Fusion Middleware









While creating the project the options selected should be exactly as per the screenshots below. Give any name for Application and Project -

Once Project is created, create a Job definition-

Click on the red arrow and paste the SOAP WSDL

Add caption

Create the proper service and operation. It’s a good advice to have the service tested in SOAP UI before creating the Job here in Jdeveloper

The Job is now created. Now we need to create schedule

Configure the parameters as per the requirements. Here I have put 6 AM

Click the Save button for Job and Schedule. Now browse ProjectàRight ClickàProject PropertiesàDeploymentà Edit Deployment Profile

 Goto Filter and select the ESS.jar and Schedule that you created now and click OK.

Now Browse Project àRightClickàUpdatedProfile

The project will be deployed like this-

Login to ESS EM console and Browse -- > Target Navigation àApplication DeploymentsàESSNativeHostingApp

Once the page for managed server opens, select as per below screenshot

Goto the configuration and select the Import option to import the Jar from the browser using the machine. Select import

Browse -- > Target Navigation à Scheduling Service àJob Requests à Submit Job Request

Select the imported Job name and the corresponding schedule

OIC Introduction

What is OIC? It’s an Oracle PAAS offering to integrate both Cloud based and On-Premise Applications.

Before going through OIC, there is a need to understand that there is additionally another product SOA CS. For advanced level Middleware Solutions SOA CS will be particularly helpful. Developers can use the JDeveloper IDE and deploy SOA composite to SOA CS cloud. This is a way of saying SOA SUITE/OSB will be available to the customers who rely heavily of traditional integration style or someone wants to create complex integrations.

Above said, OIC is needed for faster, lightweight, simplified integrations. OIC is currently providing 50 connectors. You can go through my other blog on ICS Agent to understand more on how to connect to a On Prem application.

OIC currently has 3 components –

1. Integration Cloud Service
2. Process Cloud Service
3. Visual Builder Cloud Service

Integration Cloud Service is Oracle’s original PAAS. With OIC Oracle applied all its patches to ICS. The latest features comes first to OIC.

Process Cloud Service is a lightweight cloud version to rapidly design, automate, and manage business processes in the cloud bit similar to Oracle BPM.

Visual Builder Cloud Service makes it’s possible to create forms and pages for your processes and integrations. For coding Oracle JET and Groovy scripting.

Oracle ICS Agent - When do we need it and how to create

Why do we need an Oracle ICS Agent? 

Often the question arises, what is the need of using an agent when ICS has so many adapters. Cloud based adapters are mostly API based which may or may not need needs firewall or VPN settings.

The on-premises connectivity agent enables you to create integrations between on-premises applications (example On-premise database) and Oracle Integration Cloud Service (ICS)

The below STEPS  are required to create the connectivity - 

Step1: Create an Agent Group in ICS. Save the configuration.
Step2: Open the agent and download the agent to the Linux environment of On Prem.
Step3: Execute the On-Premise Agent installer and on-premise Linux machine, the result will be a lightweight WebLogic server instance that will be running on port 7001.
Step4: Verify the agent count change from O to 1.

Detailed example can found here 

REST or Representational State Transfer

REST - Is it a Architecture design pattern or Communication protocol

REST is an Architecture design pattern that follow a set of rules to create Web Services, mostly in the context of HTTP protocol communication. 

REST METHOD	USE
GET	READ
POST	CREATE
PUT	UPDATE
DELETE	DELETE
HEAD	RESPONSE STATUS (METHOD LEVEL)
OPTIONS	REQUEST INFORMATION (METHOD LEVEL)
TRACE	ECHO ORIGINAL REQUEST GOING TO CLIENT
PATCH	PARTIAL UPDATE
PROPFIND	RETRIEVES PROPERTIES DEFINED FOR RESOURCE
LOCK	LOCK RESOURCE
UNLOCK	UNLOCK RESOURCE

REST Data Types - 

STRING 

NUMBER

BOOLEAN

NULL

OBJECT

ARRAY

XSLT - ForEach Indexing

Sometimes we come across scenarios where we need to map uneven repeating nodes in Source and Target. In such a case we need to use the indexing carefully.

Tips and Tricks 1: Mapping uneven repeating nodes between Source and Target

Use <xsl:variable name="FirstLevel1Index" select="position()"/> for holding the position of each loop.

<xsl:for-each select="/Xpath1 ">

   <xsl:variable name="Counter1" select="position()"/>

   <xsl:for-each select="/Xpath1[$Counter1]/Xpath2 ">

        <xsl:variable name="Counter2" select="position()"/>

                 <!--  Mapping -->

   </xsl:for-each>

</xsl:for-each>