About Deploying Jobs

In a production environment, SAS Data Integration Studio jobs must often be executed outside of SAS Data Integration Studio. For example, a job might have to be scheduled to run at a specified time, or a job might have to be made available as a stored process.

Accordingly, SAS Data Integration Studio enables you to do the following tasks:

Deploy a job for scheduling; see About Deploying Jobs for Scheduling.
Deploy a job as a SAS stored process; see About Deploying Jobs as Stored Processes.
Deploy a job as a SAS stored process that can be accessed by a Web service client; see About Deploying Jobs as Web Services.

You can also deploy a job in order to accomplish the following tasks:

Divide a complex process flow into a set of smaller flows that are joined together and can be executed in a particular sequence; see Using Scheduling to Handle Complex Process Flows. Alternatively, you can drop jobs into other jobs, and build up complexity that way as well. For example, you could build an outer job that contains inner jobs. You might find that these nested jobs provide a more direct and efficient solution to the problem of creating and scheduling complex process flows. This approach does not require separate deployment steps. For more information, see Creating a Job That Contains Jobs.
Execute a job on a remote host; see Using Deploy for Scheduling to Execute Jobs on a Remote Host. Alternatively, you can save the SAS code generated by the job to a file, and then manually move that file to the remote host.

Note: Under change management, only administrators can deploy jobs.

Last updated: January 16, 2018