Migrate Your Data Integration Platform Cloud Classic Instances to Oracle Cloud Infrastructure

Migrate Your Data Integration Platform Cloud Components

Data Integration Platform Cloud components such as Agents, Connections, Tasks, and Policies cannot be migrated. You must recreate the components on your Data Integration Platform Cloud instance on Oracle Cloud Infrastructure.

Refer to the following topics in the Using Oracle Data Integration Platform Cloud Guide to create your components in Data Integration Platform Cloud on Oracle Cloud Infrastructure:

Migrate Enterprise Data Quality

If you use Oracle Enterprise Data Quality (EDQ), follow these steps to migrate your projects to Data Integration Platform Cloud (DIPC) on Oracle Cloud Infrastructure (OCI) or to any standalone EDQ installation either on-premises or on a cloud IaaS provider such as OCI.

Before you begin

Your migration target instance is either the DIPC Governance edition on OCI or a standalone EDQ installation either on-premises or on OCI Compute. If migrating to a standalone version of EDQ, your target migration instance must be the same or later version of EDQ that you're using with DIPC Classic on OCI Classic. Before you migrate your EDQ projects, make sure your migration target instance has been created and available for you to use.

Export metadata from DIPC Classic

As an administrator with permission to all EDQ projects, go to the DIPC Console User menu and select Open EDQ.
In Enterprise Data Quality, click Director.
In the Project Browser, right-click on Projects and select Package.
Be sure to package any Reference Data or Data Stores at the system level (outside of any projects), other than the default Reference Data sets marked with an asterisk.

Import metadata into DIPC on OCI or EDQ on OCI-Compute

On your target migration instance, open EDQ Director as an Administrator.
From the File menu, select Open Package File, and then select your DXI file.
Drag the projects in the DXI file to the Projects node of your target server.

Notes and Limitations

The exported DXI file doesn't include EDQ Dashboard or Case Management configurations.

To migrate your Dashboard configuration:
1. Import the configuration that publishes to the Dashboard, following the same steps above.
2. Run any jobs that publish Dashboard Elements and ensure that they appear in Dashboard Administration.
3. Open Dashboard Administration on both your DIPC Classic instance and the migration target instance, and then mirror the configuration on the new instance.
To migrate your Case Management configuration,
1. Package the workflows and case source using Case Management Administration on your DIPC Classic instance.
2. Use Case Management Administration on your OCI instance to import the workflows and case source from your DIPC Classic instance.
All results data in the repository, including data in the Dashboard and Case Management can't be imported. In most cases, it's possible to regenerate the data from the configuration you imported into your migration target instance using Case Management Administration.
Passwords used to connect to Data Stores must be reentered after import. You can edit each Data Store to reenter the password.
The configuration import assumes that any configured Data Store connections are still reachable by the migration target instance.

Migrate Oracle Data Integrator

If you're using Oracle Data Integrator (ODI) with Data Integration Platform Cloud Classic, follow these steps to migrate your metadata to Data Integration Platform Cloud (DIPC) on Oracle Cloud Infrastructure (OCI) or a standalone ODI installation either on-premises or on OCI Compute.

Before you begin

Your target migration instance can be DIPC on OCI or a standalone ODI installation either on-premises or on OCI Compute, however, you must manually create and manage your own ODI installation (software and repositories) outside of DIPC for all your ODI development work. This user-managed installation can be located on OCI Compute or on-premises.

For more information about how to install ODI, see Installing the Oracle Data Integrator Software in the Installing and Configuring Oracle Data Integrator guide.

Before you migrate your ODI projects, be sure that your target migration instance is created and available for you to use.

Migrate your ODI metadata

Export metadata from DIPC Classic, and then import metadata into your user-managed ODI installation.

You can follow the steps outlined in, Exporting and Importing the Master and Work Repositories.
Configure your target migration instance environment, if needed.

For more information, see Setting Up the Topology.
(Required only if your target is DIPC on OCI) Export ODI Scenarios for execution in DIPC on OCI.

Using ODI Studio, create a Patch Deployment Archive and add the scenarios you want to execute in DIPC. For information about how to create a Patch Deployment Archive, see Creating a Patch Deployment Archive from the ODI Repository.
(Required only if your target is DIPC on OCI) Import ODI Scenarios into DIPC.

Using the DIPC Console,
1. Download and configure a DIPC Agent for ODI Execution.
  
  For more information, see Set up a Remote Agent for ODI.
2. Create Source and Target Connections, as needed.
  
  For more information, see Create a Connection.
3. Create a new ODI Execution Task, import your Patch Deployment Archive, and then Save and Run the task.
  
  For more information, see Set up an ODI Execution Task.

Migrate GoldenGate

If you're using Oracle GoldenGate with the Enterprise edition of Data Integration Platform Cloud, follow these steps to migrate your projects to DIPC on OCI or a standalone GoldenGate installation either on-premises or on OCI Compute.

Before you begin

Your target migration instance can be either DIPC on OCI or a standalone GoldenGate installation either on-premises or on OCI Compute. Before you migrate your projects, be sure that your target migration instance is created and available for you to use.

Migrate your GoldenGate projects

Run the following commands in ggsci where your DIPC Agent is installed to stop all GoldenGate proccesses gracefully:
```
GGSCI > stop extract <extract name>
GGSCI > stop replicat <replicat name>
```
Copy the following subdirectories from your DIPC OCI-C GoldenGate directory to your target migration instance GoldenGate directory:
- dirbdb
- dirchk
- dircrd
- dirdat
- dirdef
- dirdmp
- diretc
- dirjar
- diroby
- dirout
- dirpcs
- dirprm - only copy *.prm files except for MGR.prm
- dirsca
- dirsql
- dirtmp
- dirwit
- dirwww
Any customized directory created (trail location, for example) also must be copied to the target migration instance.
Run the following commands in ggsci where the DIPC Agent or OGG is installed on your target migration instance to start Extract and Replicat
```
GGSCI > start extract <extract name>
GGSCI > start replicat <replicat name>
```