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.