Database Reference
In-Depth Information
database-based repository for all production purposes. This provides a range of
features such as versioning metadata, querying, and change detection that are
typically not supported by a file-based MDS repository. An added advantage of
using an MDS backed with a database is that it allows updates from multiple
hosts to the metadata information. This is ideal in a multiserver installation,
where each of the servers can access the same repository and save concurrent
changes that become available immediately for the remaining servers in a do-
main. On the contrary, a file-based MDS can only update from one host at a
time.
For most production-enabled systems, Oracle SOA Suite 11g utilizes a set of
database schemas to store metadata and instance information during the li-
fecycle of a composite's execution. In a standard installation, the repository
schemas are created prior to creating the WebLogic domain by executing the
Repository Creation Utility (RCU)
. Typically, these schemas are appended to
a user defined prefix at the time of installation. The two schemas of prime import-
ance are
[PREFIX]_SOAINFRA
, used to manage composite instance informa-
tion, and the
[PREFIX]_MDS
schema, which stores shared artifacts, metadata,
and runtime customizations of composites. In the sections that follow, you will
learn in detail about all the aspects of administration which are related to these
schemas, as they impact the performance of your infrastructure at runtime in a
big way.
The product database schemas include a user defined prefix
so that multiple installations can share the same database
instance, for example, DEV_SOAINFRA, TEST_SOAINFRA,
and so on.
These respective schemas are loaded during the startup of the managed server
after the database connections are established via WebLogic JDBC connection
pools. SOA composites are then checked out from the database repository
