Databases Reference
In-Depth Information
server that is used to access the external file. This server must be able to resolve the
physical path that you specify for the external file.
As another example, suppose that you use the View Data option to view the contents
of a table in the Inventory tree. To display the contents of the table, the default SAS
application server or a SAS application server that is specified in the library metadata
for the table must be able to resolve the path to the table.
For the relevant server to resolve the path to a table in a SAS library, one of the
following conditions must be met:
The metadata for the library does not include an assignment to a SAS application
server, and the default SAS application server can resolve the physical path that is
specified for this library.
The metadata for the library includes an assignment to a SAS application server
that contains a SAS Workspace Server component, and the SAS Workspace Server
is accessible in the current session.
The metadata for the library includes an assignment to a SAS application server,
and SAS/CONNECT is installed on both the SAS application server and the
machine where the data resides.
For more information about configuring SAS/CONNECT to access data on a machine
that is remote to the default SAS application server, administrators should see
“Multi-Tier Environments” in the SAS Data Integration Studio chapter in the
SAS
Intelligence Platform: Administration Guide
.
Note:
If you select a library that is assigned to an inactive server, you receive a
Cannot connect to workspace server error. Check to be sure that the server assigned to
the library is running and is the active server.
Execute a Job on a Remote Host
See “Deploying a Job for Execution on a Remote Host” on page 68.
Deploying a Job for Scheduling
Preparation
After you have verified that a SAS Data Integration Studio job runs successfully, you
might want to schedule it to run in batch mode at a specified date and time. Scheduling
a job is a two-stage process as follows:
1
An administrator deploys the job for scheduling. 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.
2
The job is scheduled using the Schedule Manager plug-in to SAS Management
Console or another scheduler.
If possible, test a job and verify its output before deploying the job for scheduling.
A job cannot be deployed for scheduling 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 for scheduling unless your metadata profile enables you to
connect to SAS Data Integration Studio without change-management control. For
Search WWH ::
Custom Search