Database Reference
In-Depth Information
Managing
composite
application
lifecycles
The typical software development lifecycle is comprised of multiple phases such
as requirements, analysis, design, development, testing, and promotion. Within
the Oracle SOA development lifecycle, deployment and runtime management
tend to introduce certain complexities. As an SOA composite is being developed,
it may reference an endpoint (effectively a fully qualified URL) on a development
server. This reference will need to change as the composite is promoted to
higher up environments such as test and production. For example, your de-
velopers may have developed code that processes payments against PayPal.
Naturally, they would be pointing to the PayPal sandbox server at ht-
tps://api.sandbox.paypal.com/2.0/ during development. What happens when this
code is deployed to production? How are these references automatically updated
to reference the PayPal production servers?
Oracle SOA Suite 11g offers comprehensive lifecycle management features start-
ing from development, packaging, deployment, and post-deployment:
It offers the ability to deploy multiple versions of a given composite application
and specify a default version from either JDeveloper, Oracle Enterprise Man-
ager Fusion Middleware Control, or ant/WLST-based scripts.
Oracle SOA Suite tooling allows you to make/compile your composite applic-
ations and export a deployable SOA archive (SAR) .
An SOA archive (SAR) is a deployment unit that describes
the SOA composite application. The SAR packages service
components such as BPEL/BPMN processes, business
Search WWH ::




Custom Search