Database Reference
In-Depth Information
The JAR file
SOAMetaData.jar
can now be unzipped and browsed through
the filesystem. When extracted to a temporary folder such as
/tmp/svn
, it may
extract the following files:
/tmp/svn/SOAMetaData/faultPolicies/fault-bindings.xml
/tmp/svn/SOAMetaData/faultPolicies/fault-policies.xml
These files can now be navigated through the filesystem.
The pattern argument can be used to filter the contents you wish to export, al-
lowing you to pick and choose what you want to export if you choose not to
export the entire MDS content. For example, specifying a pattern of
/apps/
SOAMetaData/dvm/**;/apps/SOAMetaData/faultPolicies/**
will
only export the artifacts under those two subfolders within the MDS.
Importing artifacts to the MDS with ant
Since MDS artifacts and contents are exported as a JAR file, it makes sense for
it to be imported in the same manner.
For example, you may have the following files that you just updated on your local
file system and wish to import them to the MDS. This may include fault policies,
DVMs, and schemas located in the following local directory structure:
/tmp/svn/tmp/svn/SOAMetaData/faultPolicies/fault-bindings.xml
/tmp/svn/SOAMetaData/faultPolicies/fault-policies.xml
/tmp/svn/SOAMetaData/dvm/CurrencyCode.dvm
/tmp/svn/SOAMetaData/xsd/ErrorHandling/errorEvent.xsd
Firstly, you should zip up the contents of the
~/SOAMetaData
subfolder gener-
ating a single
SOAMetaData.jar
file:
cd /tmp/svn
zip -r SOAMetaData.jar SOAMetaData
