Main Tasks for Administrators - SAS Data Integration Studio 3.3 User's Guide - page 68

Deploying a Job for Execution on a Remote Host
Preparation
Administrators can use the Deploy for Scheduling window to deploy a job for
execution on a host that is remote from the default SAS application server. Code is
generated for the job and the generated code is saved to a file. Metadata about the
deployed job is saved to the current metadata repository. After a job has been deployed
to the remote host, it can be executed by any convenient means.
Remember that the generated code is local to the server that is selected in the
Deploy for Scheduling window. For example, suppose that the default SAS application
server for SAS Data Integration Studio is named SASMain, but you want a job to
execute on another SAS application server that is named DEZ_App Server. You would
select DEZ_App Server in the Deploy for Scheduling window, and the code that is
generated for the job would be local to DEZ_App Server.
If possible, test a job and verify its output before deploying the job.
A job cannot be deployed unless it is checked in. If you attempt to deploy a job that
has been checked out, deployment fails and an error message displays. The error
message indicates that the job is locked by a user.
You cannot deploy a job unless your metadata profile enables you to connect to SAS
Data Integration Studio without change-management control. For details about
administrative profiles, see “Creating a Metadata Profile (for Administrators)” on page
58.
A SAS Workspace Server and a SAS Data Step Batch Server must be configured on
the remote host. For information about this configuration, administrators should see
“Multi-Tier Environments” in the SAS Data Integration Studio chapter in the SAS
Intelligence Platform: Administration Guide .
Task Summary
1 Start SAS Data Integration Studio. A window displays that has various options
for maintaining a metadata profile.
2 Select a profile that will enable you to connect to SAS Data Integration Studio
without change-management control.
3 In the tree view, select the Inventory tab.
4 In the Inventory tree, expand the Jobs group.
5 Select one or more jobs that you want to deploy, right-click to display the pop-up
menu, and select Deploy for Scheduling . The Deploy for Scheduling window
displays.
If you selected only one job, the file name for that job appears in the Directory
Path field in the Deploy for Scheduling window. If you selected more than one job,
no file names appear in the Directory Path field of the Deploy for Scheduling
window. However, a separate file will be created for each job that is selected. Each
deployed job file will be named after the corresponding job.
6 In the SAS server field, select the server that is to used to execute the selected
job. In this example, you would not accept the default but would select the remote
server, DEZ_App Server.