Exporting and Importing a Job

Exporting Jobs

Method 1: Export a job on the job development page.

1. Double-click a job name to access the development page of the job, click , and select the type of the job to be exported.
   • Export jobs only: Export the connection relationships and property configurations of nodes to a local PC, excluding sensitive information such as passwords. After the export, you can use a browser to download the .zip package.
   • Export jobs and their dependency scripts: Export the node connection relationships, node property configurations, job scheduling configurations, parameter configurations, dependency scripts, and resource definitions to a local PC, excluding sensitive information such as passwords. After the export, you can use a browser to download the .zip package.
   Figure 1 Exporting a job (method 1)
   

2. Click OK to export the required job file.

Method 2: Export one or more jobs from the job directory.

1. Click in the job directory and select Show Check Box.
   Figure 2 Clicking Show Check Box
   

2. Select the jobs to export, click , and select Export Job. In the displayed dialog box, select Export jobs only or Export jobs and their dependency scripts and resource definitions. After the export is successful, you can obtain the exported .zip file.
   Figure 3 Selecting and exporting a job
   

Importing a Job

This function is available only if the OBS service is available. If OBS is unavailable, jobs can be imported from the local PC.

Export one or more jobs from the job directory.

1. Click > Import Job in the job directory, select the job file that has been uploaded to OBS or local directory, and rename the policy.
   

   If you select Overwrite for Duplicate Name Policy but the hard lock policy is used and the script is locked by another user, the overwriting will fail. For details about soft and hard lock policies, see Configuring the Hard and Soft Lock Policy.

   Figure 4 Importing job definitions and dependencies
   

2. Click Next to import the job as instructed.
   

   During the import, if the data connection, DLI queue, or GES graph associated with the job does not exist in DataArts Factory, the system prompts you to select one again.

Example

Context:

• A DWS data connection doctest is created in DataArts Factory.
• A real-time job doc1 is created in the job directory. Node DWS SQL is added to the job. The Data Connection of the node is set to doctest. SQL Script and Database are both configured.

1. Log in to the DataArts Studio console. Locate an instance and click Access. On the displayed page, locate a workspace and click DataArts Factory.
   Figure 5 DataArts Factory
   
2. In the left navigation pane of DataArts Factory, choose Development > Develop Job.
3. Search for doc1 in the job search box, export the job to the local host, and then upload it to the OBS folder.
4. Delete the doctest data connection associated with the job in DataArts Factory.
5. Click > Import Job in the job directory, select the job file that has been uploaded to OBS, and set the duplicate name policy.
6. Click Next and select another data connection as prompted.
7. Click Next and then Close.