Oracle released SOA Suite 12c (12.1.3)
bringing a further integration between components and a bunch of new
features. Most of them are quite spectacular, but at the same time all
are useful. A release to persuade potential buyers and a lot more to
please users of the product.
In addition to adding new features
supporting emerging industry trends like cloud and mobile, Oracle SOA
Suite 12c also provides many new features and enhancements around
developer tooling, administration and operations and, of course,
Quick Start Install
The Quick Start install
provides the foundation for a single user development environment, which
includes all Oracle SOA Suite core components - Oracle BPEL Process
Manager, Oracle Human Workflow, Oracle Business Rules, Oracle Mediator, Oracle Service Bus,
Oracle Technology Adapters, Oracle Enterprise Scheduler, SOA Spring
Component and Enterprise Manager Fusion Middleware Control. In addition,
Oracle JDeveloper is installed with all SOA IDE extensions and an integrated WebLogic Server.
JDeveloper, the WebLogic Integrated Server is pre-configured with above
SOA Suite components runtime and JavaDB (JavaDB is a development
database that allows development with SOA Suite without needing RCU)
and reuse” has always been one of the pillars of a service-oriented
architecture. Oracle SOA Suite 12c introduces several new features to
boost the ability to share and reuse services and components, while at
the same time enabling best practices and improving manageability. The
new SOA starter templates provide an easy way to package SOA composites,
components or fragments of a BPEL process and distribute them to other
departments, partners or customers. This enables the sharing of
frequently used patterns and speeds up development for template users.
Three types of SOA starter templates are supported:
- Project templates: They
include a complete project with all components and resources used and
will be used when creating a new project in your SOA application.
- Component templates:
A component with all references resources and components. For example, a
BPEL process that calls a business rule or adapter can be packaged as
component template. The component does not have to be complete and does
not have to compile. A component template can be added to an existing
Component templates will be visible in the composite palette if they’re available in the template path, configured in JDev.
- Custom activity templates:
A scope in a BPEL process, which may include an invoke/receive from/to a
partnerlink, can be packaged as a custom BPEL activity. For example, an
assign activity and a call to an adapter. Those custom activities will
be available in the BPEL palette.
Read the complete article here.
SOA & BPM Partner Community
regular information on Oracle SOA Suite become a member in the SOA
& BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Facebook Wiki