Database Reference
In-Depth Information
SOA Suite deployment
The
Service Component Architecture
(
SCA
) is an assembly model for composite
services. The specifications for SCA are managed by the standard body OASIS. The
SCA specification assumes that any business application consists of a series of ser-
vices. All the services can be assembled as composite services using the SCA model.
A typical web application written using JSPs and/or servlets is deployed as a
.war
(web archive) file and an enterprise application written using EJBs and others is de-
ployed as an
.ear
(enterprise archive) file. Similarly, a SOA composite application
written using BPEL is deployed as a
.sar
(service archive) file. All service compon-
ents such as business rules, mediator, BPEL processes, adaptors, and others are
packaged in a single
.sar
file called
Service Archive
.
The deployment descriptor for a
.war
file is
web.xml
; similarly, the composite applic-
ation assembly model uses
composite.xml
. The
composite.xml
file conforms to
the SCA specifications. The composite application is deployed as a single application
unit
.sar
file.
We can design composite applications without completing all the external service im-
plementations. The alternate approach is to design and implement the external ser-
vice implementations first before creating the composite application components. The
advantage of the alternate approach is that we have all WSDL and XSD documents
that are readily available for packaging. The best approach is to use a hybrid model
where you can create some external service as a reference to start.
The following diagram depicts the packaging model for an SOA deployment:
The
composite.xml
file has the elements representing binding, properties, external
references, component, services entry points, adaptor configurations, and so on.
