Database Reference
In-Depth Information
a file's path. If the location does not exist in the filesystem, a directory is created.
An exception to this is that when the name ends with
.jar
or
.zip
, an archive
is created. If a directory name is specified then the metadata archive is written to
a subdirectory of the directory specified, with the name of the partition that was
exported as the name of the subdirectory.
In order to similarly export items from within an MDS and import them in another
server using the WLST command line, perform the following steps:
1.
Execute the
wlst.sh
file for administering an MDS repository on the source
server instance from the
$ORACLE_HOME/common/bin
directory:
cd $ORACLE_HOME/common/bin
./wlst.sh
2.
Connect to the server instance from the offline prompt and enter the
ex-
portMetadata()
command to extract all composites and metadata de-
ployed to a partition in a temporary folder:
wls:/offline>connect(
'<username>', '<password>', '<host>:<adminport>'
)
wls:/DomainName/serverConfig>exportMetadata(application='soa-infra', server=
'<server_name>'
, toLocation=
'<export_folder>'
, docs=
'/**'
)
wls:/DomainName/serverConfig>exit()
If you are unsure about the composite name then you can find it from the
composite dashboard from the Oracle Enterprise Manager Fusion Middle-
ware Control console. The server name has to be the server to which the
MDS repository is targeted to. The
/**
wildcard filter indicates that all doc-
uments from the root folder are to be extracted out. However, you can even
specify a path filter to traverse the MDS path internally to export any desired
file or folder. The following WLST command illustrates how to export all the
.xml
files from the
/soa/configuration/default
directory under the
MDS root:
exportMetadata(application='soa-infra', server='soa_server1', toLocation=
'export_folder'
,docs='/soa/configuration/default/*.xml')
