Database Reference
In-Depth Information
Chapter 2. Management
of
SOA
Composite Applications
Developers typically create composite applications or simply composites that are
packaged into single, deployable JAR files. These applications can contain any
number of service components that include BPEL or BPMN processes, Mediat-
or services, human tasks and workflows, and business rules. Composites include
logic and code that form the foundation of SOA-based integrations. Though the
design and development of composites are not the ultimate responsibility of the
Oracle SOA Suite 11g administrator, the deployment, monitoring, and manage-
ment of them are.
In this chapter, we will discuss the concepts that enable you to manage these
composites, and cover the following areas in more detail:
•
Managing composite lifecycles
•
Structuring composite deployments with partitions
•
Setting up ant for automated composite build management
•
Promoting code, using configuration plans
•
Understanding and configuring composite audit levels
Managing composite lifecycles
Every composite has a state, mode, and associated metadata. The state can
be up (started) or down (shut down). The mode can either be active or retired.
Metadata is stored in the
Metadata Store (MDS)
, which is a database-based re-
pository used by Oracle SOA Suite 11g, and consists of information that includes
default revision number, last modification date, deployment and redeployment
times, and instance statistics. Before walking through how to manage the state
and mode of composites, we will begin by describing composite revisions.
