Using Deploy for Scheduling to Execute Jobs on a Remote Host :: SAS(R) Data Integration Studio 4.6: User's Guide

Problem

You want to execute one or more SAS Data Integration Studio jobs that process a large amount of data on a remote machine and then save the results to that remote machine. In this case, it might be efficient to move the job itself to the remote machine.

Solution

In order for this solution to work, a SAS Workspace Server and a SAS DATA Step Batch Server must have been configured on the remote host. For information about this configuration, administrators should see the "Multi-Tier Environments" section in the SAS Data Integration Studio chapter of the SAS Intelligence Platform: Desktop Application Administration Guide. Note especially the “Processing Jobs Remotely” topic.

A SAS Data Integration Studio user can then use the Deploy for Scheduling window to deploy a job for execution on the remote host. Code is generated for the job and the generated code is saved to a file on the remote host. After a job has been deployed to the remote host, it can be executed by any convenient means.

For example, assume that the default SAS Application Server for SAS Data Integration Studio is called SASApp, but you want a job to execute on another SAS Application Server that is called SASApp2. Select SASApp2 in the Deploy for Scheduling window, so that the code that is generated for the job is local to SASApp2.

Note: Instead of using this deployment mechanism, you can also save the SAS code generated by the job to a file. Then, you can move that file to the remote host.

Tasks

Deploy One or More Jobs for Execution on a Remote Host

Perform the following steps to deploy jobs for execution on a remote host:

In a tree view, right-click the job or jobs that you want to deploy. Then, select SchedulingDeploy in the pop-up menu to access the Deploy for a job for scheduling window.
In the Batch Server field, select the SAS Application Server that contains the servers on the remote host.
In the Deployment Directory field, select a predefined directory where the generated code for the selected job is stored. If the wrong directory is displayed, click New and specify the correct directory in the New directory window.

If you selected one job, you can edit the default name of the file that contains the generated code for the selected job in the Deployed Job Name field. The name must be unique in the context of the directory that is specified above. Click OK to deploy the job.

If you selected more than one job, SAS Data Integration Studio automatically generates filenames that match the job names. If the files already exist, a message asking whether you want to overwrite the existing files is displayed. Click Yes to overwrite them. Otherwise, click No.

Code is generated for the current jobs and saved to the directory that is specified in the Deployment Directory field. Metadata about the deployed jobs is saved to the current metadata server. In the Inventory tree, metadata for the deployed job is added to the Deployed job folder. The deployed job can either be scheduled or executed by any convenient means.