SOA12c- Enterprise Service Scheduler Introduction

Oracle SOA 12c comes with lot of new features; I listed some of it in my previous post. One of new feature in Enterprise Service Scheduler, this is Out Of Box scheduler provided by Oracle which is integrated to EM console. You need not to install it separately; it comes with Oracle SOA Suite 12c installer. At first look it’s look really good and easily to use. You can easily schedule your job within 2 minutes.

So if we think how it benefits SOA, here is the answer. We can schedule synchronous or asynchronous web services or service bus proxy services from ESS. We can also schedule Manage File Transfer to transfer the file from one location to another. We can also schedule to recover bulk instances from SOA EM console. Etc.

So next question is how to configure Enterprise Service Scheduler to schedule simple service? Here are the steps that we need to follow.

• Define the job
• Schedule the job
• Run the job

Below job types are included in the Enterprise Service Scheduler.

• Java
• Web Service
• EJB
• PL/SQL
• Process job type for executing a command-line command.

Click here to see how to schedule SOA service from ESS.

SOA12c - Share Artifacts using SOA Design-Time MDS Repository

Oracle SOA 12c bring couple of new features to MDS which were explained in my previous post. Another major change which brought to MDS is that we can publish the files to MDS design time repository from Jdeveloper itself.

In earlier version, to add the file to design time repository we manually need to put the file to file system and made required changes in our code to refer to that MDS file. But with the release of Oracle SOA 12c this all become graphical, we simply publish the file to design time repository by right clicking on the file, this automatically change the required references in the code.

In this post, we see how to publish the message to design time MDS from Jdeveloper.

Click here to Read- How to create Derby Database connection

To publish the file, right-click on the file and choose “Share using SOA Design-Time MDS Repository”.

This opens the SOA-MDS transfer wizard, simply click on next.

Choose the folder under which you want to add this file, if needed you can also create new folder.

In third step, it shows file name and target URL.

In next step, it should all the files which are referring to the file which we are moving to MDS.

You see file is successfully published to MDS and if you check your code all XSD references are replaced with new MDS path.

Click here to Read- New Features in Oracle SOA 12c MDS.

SOA 12c - Get Started With MDS

Oracle has introduced couple of new features in Oracle SOA Suite 12c. I have listed couple of new features that Oracle introduced for developer in my post. These new features really make developers life easy as these reduce development cycle.

Here we discuss about MDS and what all featured introduced in that. As we know MDS is used to store artifacts like WSDL, XSD, XSLT etc. we have two types of MDS, File based MDS and DB based MDS. In Oracle SOA 12c, when we use default server which is integrated with Jdeveloper then we can use only Design Time MDS (File Based MDS), Run Time MDS (DB Based MDS) is not supported.

Check this post to create design time MDS connection.

In Oracle SOA 12c release, Oracle provided couple of new options that we can use when we use Design Time MDS, these options were not there in 11g.  Below are options available with Design Time MDS.

• Create and Delete folders
• Export and Import MDS artifacts
• Transfer Artifacts between MDS repositories

In this post, we discussed these options one by one.

Get started with Oracle SOA 12c.

Create and Delete Folders

We can simple add and remove folders from design time MDS repository.

To add a new folder to it, simply right click on the apps folder and choose “Create Folder”.

To delete the folder, right-click on the folder and delete it.

Export and Import MDS Artifacts

We can export MDS artifacts from one repository and import it to other repository. This is helpful when we want to add artifacts from Design time repository to run time repository.

To export the MDS artifacts, right-click on MDS repository and choose “Export to Jar”.

We can import the Jar to any other repository, to do that right click on the repository and choose “Import from Jar”.

Transfer artifacts between repositories

We can also transfer the files from one repository to another, to transfer the file right click on the file which we want to transfer and choose the target repository.

Click here to see how to share MDS artifacts to SOA Design Time Repository.

SOA 12c - Create Java Derby Database Connection

Oracle SOA 12c comes as single installer that means we need not to install DB, Weblogic, SOA and OSB separately.  Oracle SOA 12c use Derby Java database by default.

In this post, we see how to create Derby Database connection. To create derby DB connection, you need to make sure that your default server is running which automatically start the Derby database.

To see how to start the default server check this post.

To create new DB connection, go to Resources à IDE Connections à Database

Name your connection and choose “Java DB (Derby)” from connection Type drop-down.

Enter Hostname, database name and port details. We need to choose drivers to create this DB connection. Click on driver browse button and choose “Java DB JDBC Driver”.

Now test your connection.

Once you create this DB connection, it will automatically create default Design time MDS connection.

Check my next post which shows how to get started withOracle SOA 12c.

Oracle SOA 12c Features

Oracle has released SOA Suite 12c and lots of new features are introduced in this release. Below is list of some of the new features.

Single Installer: Oracle Suite 12c comes as single installer for developers that means you only need to install only one setup (SOA Suite 12c), DB/Weblogic/SOA will get installed, you need to install it separately. Oracle SOA 12c use Java Derby database, which is file based and that makes it really fast.

Click here to see how to run single installer and install SOA 12c.

Single IDE: In Oracle SOA 12c Jdeveloper is used as IDE for all designs. For OSB development we need not to use different IDE (Eclipse) anymore, we can develop OSB application in Jdeveloper itself.

Click here to see how to create OSB project from Jdeveloper 12c.

Debugger: This is new feature in Oracle SOA 12c, debugger is introduced to debug SOA and OSB applications. With the help of debugger we can debug our code before deploying it; this saves lot of development efforts. We can also change message text while debugging it.

Click here to see how to use debugger.

Graphical MDS: In Oracle SOA 12c graphical tool is provided to publish, search and consume filed from MDS and OER.

Click here to see how this graphical MDS works.

SOA Templates: With the introduction of templates sharing of code between teams become earlier and development efforts reduced. There are three types of templates introduced.

• Project Template
• Component Template
• Custom Activity Template

Click here to see for more details.

BPEL Sub-process: Sub-process is introduced in this launch which helps to reduce redundancy. Suppose we need to update database table 3 times in one flow so instead of add 3 different invoke to same BPEL, create sub-process which update the database table and use that sub-process 3 times in that BPEL. There are two types of sub-processes.

• Standalone sub-process
• Inline sub-process

Click here to see for more details.

Re-sequencing in OSB: In 11g this feature was available in Mediator, in Oracle SOA 12c this features added to service bus also, with the help of this feature we able to process the request message in proper sequence.

Click here for more details.

Adapter: Coherence, LDAP and cloud adapter are introduced in this release.

Click here to see how Coherence adapter works.

Xquery Mapper: In this release Xquery mapper is introduced which provide XQuery support.

Enterprise Service Scheduler: ESS is out of box scheduler. By using this we can schedule the services.

Click here to see how ESS used to schedule SOA service.

Translate Activity:  Translate activity is also introduced which is used for Native to XML and XML to Native transformation.

Click here to see how translate activity works.

MDS support for OSB: In 11g version MDS support was not there for OSB but in 12c MDS support is provided for OSB.

Click here to see how to use MDS file to create OSB business service.

SOA 12c - Oracle Service Bus Hands On

In a major Oracle SOA 12c release, Oracle made significant changes for Oracle Service Bus. Now we can use Jdeveloper to use build OSB applications, no need to use separate IDE tool (Eclipse) any more. OSB web based console is totally redesigned, all monitoring and run time configuration features are now provided in EM console itself. Message flows which were part of OSB proxy service now added as separate resources in form of Split-join and Pipeline etc.

In this post, I will walk you through the steps to create sample OSB application in Jdeveloper and test it using integrated server.

Let’s get started with OSB application creation. Go to File à New à Application àService Bus Application.

New OSB Application

Name your application and OSB project.

Add required folder structure as per your naming standards. To add a new folder right click on required folder or file under which you want to add the folder then go to New à From Gallery.

Choose Folder from Items list and rename the folder.

Repeat above step for all other folders.

Now we add business service to the project which will invoke the HelloWorld SOA Composite which we created in previous post, to add the business service drag “HTTP” adapter to composite.

Name your business service and make sure transport in HTTP. Click on Next.

Choose WSDL option and browse HelloWorld Composite WSDL file.

Wizard asked you to add required WSDL and XSD file of HelloWorld application to your OSB project. Check all and click on finish.

Now we add the proxy service and Pipeline to the composite. Pipeline contains all the actions which need to be performed before invoking business service.

Name you pipeline and click on next.

You see Expose as a proxy option in the pipeline; this option will configure proxy service for you based on pipeline message type.

We use same HelloWorld WSDL file for the pipeline and proxy. Check the WSDL option and browse the HelloWorld WSDL file.

Once you add the HelloWorld WSDL file, your pipeline window should look like below.

Your flow looks like below. Now wire pipeline to business service.

With the above step we are done with build part. Now we need to test on integrated server. To test it right click on proxy service and click on Run.

This opens a OSB console for you. Provide request message and click on Execute.

You should see response in same console.

You can also check the flow in EM console.