import Comosite application Metadata in SOA

importMetadata

Description

The application metadata can be transferred from one server location (for example, testing) to another server location (for example, production) by exporting and importing the metadata.
Use this command to import metadata.

Syntax

importMetadata(application, server, fromLocation, [docs,] [restrictCustTo],
    [excludeAllCust], [excludeBaseDocs], [excludeExtendedMetadata],
    [cancelOnException], [applicationVersion])

Argument	Definition
application	The name of the application for which the metadata is to be imported.
server	The target server on which this application is deployed.
fromLocation	The source directory or archive file from which documents will be selected for transfer. The directory or archive file must be a local or network directory or file where the application is physically deployed. This argument can be used as a temporary file system location for transferring metadata from one server to another. For more information, see "Moving Metadata from a Test System to a Production System" in the Oracle Fusion Middleware Administrator's Guide
docs	Optional. A list of comma-separated, fully qualified document names or document name patterns, or both. The patterns can have the following wildcard characters: * and **. This argument defaults to "/**", which imports all of the documents in the repository. The asterisk (*) represents all documents under the current namespace. The double asterisk (**) represents all documents under the current namespace and also recursively includes all documents in subnamespaces. For example, "/oracle/*" will include all documents under "/oracle/" but not include documents under "/oracle/mds/". "/oracle/**" will include all documents under "/oracle/" and also under "/oracle/mds/" and any other documents further in the namespace chain.
restrictCustTo	Optional. A list of comma-separated customization layer names used to restrict the import operation to import only customization documents that match the specified customization layers. This argument will be ignored if the excludeAllCust argument is also specified.
excludeAllCust	Optional. A Boolean value (true or false) that specifies whether or not to import all customization documents. This argument defaults to false. This argument overrides the restrictCustTo argument.
excludeBaseDocs	Optional. A Boolean value (true or false) that specifies whether or not to import base documents. This argument defaults to false.
excludeExtendedMetadata	Optional. A Boolean value (true or false) that specifies whether or not to import the Extended Metadata documents. This argument defaults to false.
cancelOnException	Optional. A Boolean value (true or false) that specifies whether or not to abort the import operation when an exception is encountered.
applicationVersion	Optional. The application version, if multiple versions of the same application are deployed.

Example

The following example imports all metadata available in /tmp/myrepos to the application mdsapp deployed in the server srg:

wls:/weblogic/serverConfig> importMetadata(application='mdsapp', server='srg',
                             fromLocation='/tmp/myrepos',docs="/**")
Executing operation: importMetadata.
"importMetadata" operation completed. Summary of "importMetadata" operation is:
List of documents successfully transferred:
/app1/jobs.xml
/app1/mo.xml
2 documents successfully transferred.
wls:/weblogic/serverConfig>