Metadata Manager Custom Metadata Integration Guide

10.5.7
- 10.5.9
- 10.5.8
- 10.5.6
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0

Back Next

Custom Resource Migration Steps

To migrate a custom resource between Metadata Manager instances of the same version, you must migrate the models and resources to the target environment. To migrate objects, you export them from the source repository and import them into the target repository.

The method that you use to migrate a custom resource varies based on whether the resource uses a load template. If the resource uses a load template, you migrate the model, load template, and resource configuration, and then load the resource in the target environment. If the resource does not use a load template, you migrate the model, create the resource in the target environment, and then migrate the resource metadata.

Migrating a Custom Resource that uses a Load Template

The following image shows the process to migrate a custom resource that uses a load template:

Migrate the model:

Export the model from the source repository. On the

Model

tab, select

Actions

Export Models

. If the model has associated rule set definitions, include them in the export file.

Import the model into the target repository. On the

Model

tab, select

Actions

Import Models

Migrate the load template:

Export the load template from the source repository. On the

Model

tab, right-click the model, and select

Get Load Template

Upload the load template into the target repository. On the

Model

tab, right-click the model, and select

Upload Load Template

Migrate the resource configuration:

Export the resource configuration from the source repository. On the

Load

tab, select

Actions

Export Resource Configuration

. If the resource has associated rule sets or parameter definitions, include them in the export file.

Import the resource configuration into the target repository. On the

Load

tab, select

Actions

Import Resource Configuration

Load the resource in the target environment.

Load the resource to import the metadata and create the data lineage links.

Migrating a Custom Resource that does not use a Load Template

The following image shows the process to migrate a custom resource that does not use a load template:

Migrate the model:

Export the model from the source repository. On the

Model

tab, select

Actions

Export Models

. If the model has associated rule set definitions, include them in the export file.

Import the model into the target repository. On the

Model

tab, select

Actions

Import Models

In the target environment, create a custom resource with the same name as the resource in the source environment.

Migrate the custom resource metadata:

Export the resource metadata to an XML file. On the

Browse

tab, click

Actions

Export Metadata

XML

Import the resource metadata into the target repository. On the

Browse

tab, click

Actions

Import Metadata

XML

Custom Resource Migration

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Metadata Manager Custom Metadata Integration Guide

Metadata Manager Custom Metadata Integration Guide

Custom Resource Migration Steps

Custom Resource Migration Steps

Migrating a Custom Resource that uses a Load Template

Migrating a Custom Resource that does not use a Load Template