Oracle Cloud Infrastructure Documentation

Export Objects

You can export Data Transforms artifacts such as projects, connections, data loads, data flows, workflows, and schedules from one environment and import them to another.

The Export and Import options in Data Transforms allow you to do the following:
  • Move code from development environments to production environments.
  • Share code between development environments.
  • Backup and restore objects.

To export objects from a Development environment you need to provide an Object Storage connection as an input. You need to use the same Object Storage connection when you want to run the import process in another environment. See Import Objects. The export operation exports all the metadata of the repository objects along with all its dependent parent and child objects, and stores the information in an XML format in the Object Storage bucket.

You can use the Export wizard to export the entire project or export individual objects at the following levels:
  • Projects
  • Connections
  • Data Load
  • Data Flow
  • Workflow
  • Schedule
When you export an individual object, all the dependent objects are automatically included in the export.
Note

Individual variables export is not currently supported. However, when you export a Project, the variables within that project are also exported.

To export objects using the Export wizard:

  1. From the left pane, click the Home tab. Click Export.

    The Export wizard appears.

  2. In the Export File Name field, enter a name for the file. The exported data will be stored in the ZIP format with the filename_timestamp_DTR file naming convention.
  3. Select an Object Storage connection from the drop-down to store the exported file. Note that you need to select the same Object Storage connection during the import operation.
  4. Click Next.
  5. Select the objects that you want to export. You can choose to export a single, multiple, or all the objects that are listed on the page.
  6. Click Next.
  7. Select the connections that you want to export.

    You may choose not to make any selection on this page. The connections that are associated with the objects that you selected in the previous screen are automatically included during the export operation.

  8. Click Next to preview your selections.
  9. Click Export to start the export operation.

    A confirmation prompt appears when the export operation completes successfully.

To export individual objects:

  1. Click the Actions menu of the project, connection, dataload, dataflow, workflow, or schedule that you want to export, and click Export.
  2. In the Export File Name field, enter a name for the file. The exported data will be stored in the ZIP format with the filename_timestamp_DTR file naming convention.
  3. Select an Object Storage connection from the drop-down to store the exported file. You need to select the same Object Storage connection during the import operation.
  4. Click Export to start the export operation.

    A confirmation prompt appears when the export operation completes successfully.

  • Import Objects
    To import objects you need to provide the same Object Storage connection that you had used for the export operation.

Parent topic: The Data Transforms Page

Import Objects

To import objects you need to provide the same Object Storage connection that you had used for the export operation.

Note the following about the import process:
  • Projects - To import projects, you can choose whether you want to overwrite the data in the repository or merge the matching container objects with the objects that are being imported.
    • Overwrite - If there is a match in the repository, all the dependent child objects will be overwritten by default.

      If there is no match, the project along with the child objects will be copied into the repository.

    • Merge - If the project exists in the repository, but the dependent child objects have no match, all the child objects in the repository will be merged with the new child objects that are coming through the import process.

      If the project exists in the repository, and the dependent child objects have a match, all the child objects in the repository will be overwritten with the new child objects that are coming through the import process.

      If the project does not exist in the repository, the project along with the child objects will be copied into the repository.

  • Connections - For connections that have a match in the repository, the import process updates only the advanced properties of the connection in the repository along with the connection name. Credentials such as the schema name, passwords, and connection URL are persisted as is in the new environment. You can use such connections without any modification in the target repository.

    For connections that have no match in the repository, credentials such as the schema name, passwords, and connection URL are not carried over during the import operation. Post import, you need to update the credential information for such connections. You also need to make sure that you create a schema user in the database along with the required tables created for the schema user, which you may use as a data entity in dataloads, dataflows, workflows, and schedules.

  • Data Loads, Data Flows, and Workflows - For these objects if there is a match in the repository, all the objects will be overwritten by default.
  • Schedule - The status for schedules that have no match in the repository are set to Inactive. You need to update the connection information that is associated with the schedule, and then set the status of the schedule to Active.

To import objects:

  1. From the left pane, click the Home tab. Click Import.

    The Import dialog box appears.

  2. From the Object Storage Connection drop-down, select the connection that you had used for the export operation. See Export Objects.
  3. From the Import File Name drop-down, select the exported file.
  4. Choose one of the following import options:
    • Merge - Choose this to merge the objects that are already in the repository with the objects that are coming through the import process. This option is only available for container objects such as Projects.
    • Overwrite - Choose this to replace the objects that are already in the repository with the objects that are coming through the import process.
  5. Click Import to start the import operation.

    A confirmation prompt appears when the import operation completes successfully.

Parent topic: Export Objects