Database Reference
In-Depth Information
Exporting a repository
Policy documents such as assertion templates, policies, and policy sets can be
exported all at once from the policy repository to a supported archive by using
the following export command. In the archive argument, you need to specify the
name and path of the archive where all policy documents are exported to:
exportRepository(archive, [documents=None], [expandReferences='false'])
For
example,
to
export
everything
from
the
policy
repository
to
the
Policies.zip
archive, the command is:
exportRepository(
'Policies.zip'
)
The
documents
argument is optional and is used to specify the kind of doc-
uments that are to be exported into the archive. If no argument is specified,
everything gets exported, as is the case with the preceding command. The
documents
argument can take a policy file name just to export that particular
policy, or use a search expression to find and export specific documents in the
repository. For example, to export all message protection policies from the do-
main, enter the following command:
exportRepository(
'MessageProtectionPolicies.zip'
, ['policies:oracle/wss10_message_protection_%', 'policies:oracle/wss11_message_protection_%'])
Importing a repository
Importing documents into a policy repository uses the following command:
importRepository(archive, [map=none], [generateMapFile='false'])
Similar to the
export
command, the
archive
argument in the
importRe-
pository
command reads a valid policy archive and its location. The optional
map
argument saves mapping information in a policy set, from the source envir-
onment to the target environment, in a target file. For example, a map file en-
