1. Migrating Oracle MFT Cloud Service Instances to Oracle Cloud Infrastructure
  2. Migrate an Oracle Managed File Transfer Cloud Service instance to Oracle Cloud Infrastructure
  3. Migrate Data Components in MFT Cloud Service
  4. Move OWSM Data

Move OWSM Data

Move OWSM data by exporting it from the source and importing it to the target environment.

OWSM has the following artifacts of interest:

  • CSF keys: There are references to CSF keys in OWSM policies/policy overrides. There is no change required as long as actual values are available in the credential store owned by OPSS. CSF keys must be available in the target environment.

  • certs and keys: OWSM supports two types of keystores: JKS (file based) and KSS (owned by OPSS). The certificates/aliases in the source environment should be made available in the target environment. There are references to keys/certificates in OWSM policies/policy overrides.

  • Custom OWSM authorization policies: These are same as custom policies.

  • Custom OWSM policies

    See Exporting Documents from the Repository Using WLST in Securing Web Services and Managing Policies with Oracle Web Services Manager.

    See Importing Documents into the Repository Using WLST in Securing Web Services and Managing Policies with Oracle Web Services Manager.

  • Additional configurations that may be required: trust config and OAuth config

In 12c, exportWSMRepository exports all custom policies from the repository, the trust configuration, OAuth configuration, and any other configuration documents.

In 11g, the specific custom policies have to be enumerated to export them. Note that it may not be as simple as moving the documents from 11g to 12c because as part of upgrade, the OWSM upgrade plugin takes care of adding/updating 12c specific changes in the artifacts. There may be no easy way to automate policy movement from 11g to 12c as part of migration.