yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
main
doc-exports/docs/dataartsstudio/umn/dataartsstudio_01_0010.html
chenxiaoxiong f9e2808b7c DataArts UMN 20250810 version 
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com>
Co-authored-by: chenxiaoxiong <chenxiaoxiong@huawei.com>
Co-committed-by: chenxiaoxiong <chenxiaoxiong@huawei.com>
2025-09-02 10:44:13 +00:00

9.6 KiB
Raw Permalink Blame History

Configuring DataArts Studio Resource Migration

To migrate resources in one workspace to another, you can use the resource migration function provided by DataArts Studio.

Resources can be imported from OBS or a local path. Resources that can be migrated include the following service data:
  • Data connections created in Management Center
  • CDM jobs created in DataArts Migration, including the links in jobs
  • Scripts and jobs that have been submitted in DataArts Factory. By default, when jobs are exported, their dependent scripts and resources are not exported.

Constraints

  • Only an exported .zip file can be imported. During the import, the system verifies the resources in the file.
  • For security concerns, passwords of connections are not exported when the connections are exported. You need to enter the passwords when importing the connections.
  • The file to be imported from an OBS bucket or local path cannot be larger than 10 MB.

Exporting a Resource

  1. Log in to the DataArts Studio console by following the instructions in Accessing the DataArts Studio Instance Console.
  2. On the DataArts Studio console, locate a workspace and click Management Center.
  3. In the navigation pane, choose Migrate Resources.

    Figure 1 Migrating Resources

  4. Click Export Task to configure the file name and the OBS path for saving the file. If OBS is unavailable, you only need to set the file name.

    Figure 2 Export Task

  5. Click Next and select the resources to export.

  6. Click Next and wait until the export is complete. The resource package is exported to the OBS path you have set.

    Figure 3 Export completed

    If no result is displayed in 1 minute, the export fails. Try again. If the failure persists, contact the customer service or technical support.

  7. After the export is complete, you can click Download in the row of the corresponding migration task to download the exported resource package.

    Figure 4 Downloading the exported result

Importing a Resource

  1. In the navigation pane, choose Migrate Resources.

    Figure 5 Migrating Resources

  2. Click Import File. On the displayed page, select an import mode and set the OBS bucket and path or local path that stores resources. The resource to be imported must be a .zip file exported from the console.

    Figure 6 Configuring the path that stores the resources to be imported

  3. Click Import File and upload resources. a .zip resource file that you have exported.
  4. Click Next and select the resources to import.

  5. If you select DataSource, click Next to configure a data connection.

    Figure 7 Configuring a data connection

  6. Click Next and wait until the import task is delivered. When the import task is delivered successfully, the system displays message "Import task started."

    Figure 8 Import task started

  7. Click OK. You can view the import result in the resource migration task list.

    Subtasks that fail are marked in red. You can click their names to view the failure causes.
    Figure 9 Viewing the import result

Parent topic: Management Center
<script language="JavaScript"> </script>