Skip to main content

SOA 12c: New features

With increase in requirements and challenges such as Cloud Integration , Mobile Integration and IoT things, Oracle Soa 12c suite brings a lot of new features with it. It has focused on both integration and ease.

This article will go through some such features of SOA 12c .

Integration
Quick Installer with all in One
Single-Click Installer package which include JDeveloper, a integrated Weblogic service with SOA Suite (including Service Bus), JavaDB (for it’s Database) and the Enterprise Manager.

SOA and OSB Together
Unlike 11g, 12c came up with SOA and OSB together. Integration of Service Bus and SOA Suite will helps developer to create. REST and SOAP based service on one tool

New Technology
Mobile Integration, Cloud Integration , Cache integration are some of major highlights of 12c
SOA and Service Bus
SOA
Templates : Introduction of templates (Project Template, Component Template, Activity Template improved the reusability factor in SOA.


Sub-Process : Process both type Standalone and inline sub-process will reduce rework and increase reusability.


XQuery and XSLT Mapper : Improving XSLT mapper features and usage of XQuery at design level in SOA are one of the key point in soa12c.


Fault Editor : Unlike 11g, 12c comes wit Fault Editor to design fault policies and Fault Bindings.


MDS : Compile (File Based) time and Runtime (Database Based) is more easy to create and update unlike 11g.

Service Bus
REST Service :  Creation of REST based service in SOA 12c both xml and json based is major advantage. Mobile enablement.


Templates : Provision of usage of templates in Service Bus also.


Separation of Pipeline : Pipeline in 12c can be developed from the service component and can be exposed independently.


MDS: Usage of MDS in Service Bus is key component in 12c.
New Technology
MFT
Managed File Transfer is an integrated solution that has reduce the file transfer complexities between Source and many targets. This allows customers to load data securely into Oracle cloud application as well as third-party cloud or partner applications.

ESS
Enterprise Scheduler Service  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.

BAM
Business Activity Monitoring  in 12c has been enhanced to enable rapid and flexible assessment of key performance indicators (KPIs) by storing the   data in the industry standard star schema format.

OEP
Oracle Event Processing in 12c can handle millions messages per second at low latencies.


Comments

  1. Unknown14 October 2016 at 13:58

    Thanks Sumit for the useful blog, it really helped.

    ReplyDelete

Post a Comment

Popular posts from this blog

Tune your JDeveloper 12c (12.1.3)

Is your JDeveloper 12c too slow, follow these 3 basic steps and increase perfomance of JDeveloper 12c  (12.1.3) Step 1:  Configure JVM settings in jdev.conf Path:  $MV_HOME$/jdeveloper/jdev/bin/jdev.conf # optimize the JVM for strings / text editing AddVMOption -XX:+UseStringCache AddVMOption -XX:+OptimizeStringConcat AddVMOption -XX:+UseCompressedStrings # if on a 64-bit system, but using less than 32 GB RAM, this reduces object pointer memory size AddVMOption -XX:+UseCompressedOops # use an aggressive garbage collector (constant small collections) AddVMOption -XX:+AggressiveOpts # for multi-core machines, use multiple threads to create objects and reduce pause times AddVMOption -XX:+UseConcMarkSweepGC AddVMOption -DVFS_ENABLE=true AddVMOption -Dsun.java2d.ddoffscreen=false AddVMOption -XX:+UseParNewGC AddVMOption -XX:+CMSIncrementalMode AddVMOption -XX:+CMSIncrementalPacing AddVMOption -XX:CMSIncrementalDutyCycleMin=0 AddVMOption -XX:CMSIncrementalDutyCycle=10 Step 2:
Post a Comment
Read more

How to use Log4j logger in Simple few steps

Steps to follow : 1. Download Log4j Jar file  and add in Project Lib Path.        http://logging.apache.org/log4j/1.2/download.html 2. Create Log4j.properties file in your project and add below details.      log4j.rootLogger=DEBUG, Appender1,Appender2 log4j.appender.Appender1=org.apache.log4j.ConsoleAppender log4j.appender.Appender1.layout=org.apache.log4j.PatternLayout log4j.appender.Appender1.layout.ConversionPattern=%-7p %d [%t] %c %x - %m%n log4j.appender.Appender2=org.apache.log4j.FileAppender log4j.appender.Appender2.File= applog.txt log4j.appender.Appender2.layout=org.apache.log4j.PatternLayout log4j.appender.Appender2.layout.ConversionPattern=%-7p %d [%t] %c %x - %m%n 3. In the main method of Java program add below code.         Logger logger = Logger.getLogger(Conn.class);          String log4jConfigFile = System.getProperty("user.dir") + File.separator + "log4j.properties";         PropertyConfigurator.configure(log4jConfigFile);  
Post a Comment
Read more

CHANGING THE INBOUND FILE ADAPTER ARCHIVE FILE NAME IN SOA

Default archive name will be filename_ digest _timestamp. This format was introduced with SOA 11g. To configure the File Adapter archive filename to use this format: filename_yyyymmdd_hh24mmss we have to use property “UseDigest” in JCA file. By default “UseDigest” is set to true, which tells the Inbound File Adapter that the archive file name format will be the default: filename_digest_timestamp. When the “UseDigest” property is set to false, the filename format will revert to: filename_timestamp. Modify your File Inbound JCA file, and add the following property: <property name=”UseDigest” value=”false”/>
Post a Comment
Read more