Database Reference
In-Depth Information
soacustom
partition in the
mds-custom
repository to the
mds-soa
repository
as follows:.
cloneMetadataPartition(fromRepository=
'mds-custom'
, fromPartition=
'soacustom'
, toRepository=
'mds-soa'
, toPartition=
'soacustom'
)
Deploying a MAR using WLST
Most of the time Oracle SOA Suite 11g developers would create an MDS archive
during development which would contain bundled composites, shared assets, or
reusable resources, and it would be left to the administrator to deploy it to the
infrastructure. The easiest and recommended way to deploy an MDS bundle is
to use the WLST command line utility. Deploying an MDS archive is a two-step
process and involves adding the MDS repository configuration information in a
MAR (Metadata Archive) file and then deploying it to a given partition. The fol-
lowing steps would outline how to deploy an archive to a specified partition:
1.
Open the WLST command line by executing the
wlst.sh
script from the
$ORACLE_HOME/common/bin
directory of your middleware installation.
2.
Invoke the
getMDSArchiveConfig()
command to obtain a handle to
the
MDSArchiveConfig
object for a given MDS bundle and assign it to
a variable. The
getMDSArchiveConfig()
commands take a parameter,
fromLocation
, pointing to the location of the archive on the file system.
3.
The object of
MDSArchiveConfig
can be used to set the MDS information
such as repository name, partition, repository type, and JNDI of repository
database connection by invoking the
setAppMetadataRepository()
operation.
4.
Invoke the
save()
operation on the
MDSArchiveConfig
object to save
changes to the archive. If the
toLocation
argument is specified in the op-
eration, changes are applied to the target archive file and the original file re-
mains unchanged. Otherwise, the changes are saved in the original file itself.
5.
Use the
connect()
command to connect to the instance of the server to
which the metadata archive is to be deployed.
