Databases Reference
In-Depth Information
7 The next step is to select the job deployment directory. One or more job
deployment directories were defined for the selected server when the metadata for
that server was created. Click the Select button. The Deployment Directories
window displays.
8 In the Deployment Directories window, select a directory where the generated code
for the selected job will be stored, then click OK . You are returned to the Deploy for
Scheduling window. The directory that you selected is specified in the Directory
name field.
If you selected one job, in the File name field you can edit the default name of
the file that will contain the generated code for the selected job. The name must
be unique in the context of the directory name that is specified above.
9 When you are ready to deploy the job or jobs, click OK . Code is generated for the
selected job or jobs and is saved to the directory that is specified in the Directory
name field. Metadata about the deployed jobs is saved to the current metadata
repository. A status window displays. It states whether the deployment was
successful or not.
The icon next to the jobs that you selected changes to indicate that the jobs
have been deployed to the remote server.
Next Tasks
After a job has been deployed to the remote host, it can be executed by any
convenient means.
Converting Jobs into Stored Processes
About Stored Processes
SAS Data Integration Studio enables you to create jobs that perform various data
integration tasks. You can execute jobs immediately, or you can save them to a file so
that a stored process server can execute them later.
A stored process is a SAS program that is stored on a server and can be executed as
required by requesting applications. You can use stored processes for Web reporting,
analytics, building Web applications, delivering result packages to clients or to the
mid-tier, and publishing results to channels or repositories. Stored processes can also
access any SAS data source or external file and create new data sets, files, or other data
targets supported by SAS.
Administrators can generate one or more stored processes for a job that is selected in
the Inventory tree or the Custom tree on the SAS Data Integration Studio desktop.
Code is generated for the stored process and the generated code is saved to a file.
Metadata about the stored process is saved in the current metadata repository.
After the metadata has been saved to a repository, other applications can connect to
the repository and access the stored processes that are defined there—if they have
appropriate privilege. For example, a stored process that was generated for a SAS Data
Integration Studio job could be executed from the following applications:
￿ SAS Add-In for Microsoft Office, a Component Object Model (COM) add-in that
extends Microsoft Office by enabling you to dynamically execute stored processes
and embed the results in Microsoft Word documents and Microsoft Excel
spreadsheets.
 
Search WWH ::




Custom Search