Vous êtes sur la page 1sur 11

Features in SOA12c:

1) The major new feature from a developer perspective is the new installation procedure.
Installation is very easy using the provided quick start installer

2) OSB and SOA can be done in the JDeveloper.
3) Extension to the Mobile Application Framework
4) Newly added cloud Adapters in SOA l2c is Sales force adapter.

5) Mobile Enablement: Oracle SOA Suite 12c introduces a REST binding within JDeveloper to
simplify mobile enablement by exposing traditional SOAP services, Enterprise Java Beans
(EJBs), JCA adapters connecting backend applications or just about any other underlying
implementation through JSON/REST. The REST binding is available for SOA composites and
Service Bus services and allows the configuration of REST interactions as exposed interfaces
and allows the invocation of externally available REST services.

Both SOA composites and Service Bus projects include the same REST binding wizard.

In the Native Schema builder we have feature regarding Json format is added

6) Adapters like coherence (to connect with coherence server cache), Healthcare (to connect with
health care system) , MFT (to connect with MFT server) ,LDAP , MSMQ ( to exchange
messages between Microsoft message queues) SOAP ,Rest ,UMS ( enables communication
between users and deploys services) are added.

7) New SOA Component called Subprocess is added in 12c.

8) JDE world and SAP application adapters are added.

9) Use of Templates in both SOA and OSB.

There are many other features for transformation, debugging and other Bpel components are
added like:
Maven support
Graphical XQuery editor

Debugging with breakpoints(toggle break points can be used): SOA Suite 12c
includes a visual debugger in Oracle JDeveloper that allows the setting of breakpoints
within a SOA composite, a BPEL process and a Service Bus pipeline.

In SOA the Break points are

Testing: Theres no need any more to switch between JDeveloper and Enterprise
Manager Fusion Middleware Control to define, run and analyze tests.

Fault Handling (Fault policy document is created in the project, no needing of doing it

There is Graphical Editor for the creation of Faults, alerts etc.

Some Bpel components are also added in the Oracle Extension where we have
Schedule job
SDO objects like bind , create and Remove entity.

Property Inspector Window:
Before 12c Editing Activities in Bpel are done in the wizard, which is activated by double
clicking the activity or by selecting edit from the menu.
In 12c, the property inspector has been extended to also support editing the properties of BPEL
Translate from Native action:
With this action we can transform a CSV/JSON/String element of the request to XML using a
NXSD transformation. The Transformed output can then be used in the routing rules of the
New graphical editor for the Assign action:
The graphical editor for the assign action is same as BPEL uses. We can create multiple copy
rules by using drag and drop functionality

SOA Suite 12c it also will be possible the define or change them at runtime: Design Time at Run
Time. This functionality is added to the existing SOA Composer application, which is already
used to change other runtime metrics like the Rule Engine and Domain Values Maps (DVMs).

After Deploying the Composite:
In SOA-Infra dashboard there is option for searching the instances and saving them

Deployed Composites are show with status and can easily be started and stopped

We have a SOA composite dashboard in the Enterprise manager. It consists of
It shows components and services.
Image of the Composite in Jdev is displayed as an image.
It is easy to see the Composite dependencies
When flow instance is selected more details are showed about the faults.

SOA Error Hospital
In the SOA-Infra dashboard (recoverable) faults are visual using a chart:

Features as a Part of Service bus:
1) Development for OSB is done in the JDeveloper only.
2) Like in SOA the template creation and usage is available in OSB also.
3) XQuery is available as graphical editor
4) Instead of the SB Console now the flow instances are seen in the Enterprise manager.
5) We can use a domain value map in the OSB.