The SAS Visual Process Orchestration Server software
consists of two servers, the Design Server
and the Runtime Server.
The two servers are installed on a single host. Together, the two
servers manage the development and execution of orchestration jobs.
Orchestration
jobs (also known as process jobs) execute an ordered series of component
jobs that were previously created in SAS Data Integration Studio or
in DataFlux Data Management Studio. The component jobs can execute
SAS programs, other programs, scripts, and real-time services. The
component jobs run on the servers on which they were deployed, such
as DataFlux Data Management Servers. Orchestration jobs can use control
logic, events, and parallel processing as needed to coordinate the
execution of their component jobs.
You create orchestration jobs
in the SAS Visual Process Orchestration Web Client, by dragging and
dropping component jobs and coordination nodes into an ordered sequence.
The SAS Visual Process
Orchestration Design Server works with the web clients to create,
modify, and delete orchestration jobs. The orchestration job files
are stored on a SAS Content Server.
The Design Server ensures
that each orchestration job can interact with other orchestration
jobs and with real-time services that run on DataFlux Data Management
Servers. The Design Server can also extract from the job a list of
input and output variables. The Design Server extracts variables when
the SAS web client add or modifies a node that references another
orchestration job or a real-time service.
The
SAS Web Application Server ensures that the user of the SAS web client
is authorized to access all of the component jobs and data tables
that are included in the orchestration job.
The SAS Visual Process
Orchestration Runtime Server executes orchestration jobs. When a SAS
web client requests a job run, the job is retrieved from the SAS Content
Server and executed by the Runtime Server.
For a given orchestration
job, the Runtime Server can trigger the execution of other orchestration
jobs and remotely stored component jobs and real-time services. These
interactions use the input and output variables that are maintained
by the Design Server.
During the execution
of orchestration jobs, the Runtime Server authenticates the requesting
user through the SAS Metadata Server. The SAS Web Application ensures
that the web client is authorized to access the component jobs, real-time
services, and data sources that comprise the orchestration job.
The Runtime Server sole
method of communication is a SOAP interface. The Runtime Server listens
at one port for requests to run orchestration jobs.
All orchestration jobs
run in separate multi-threaded processes.
The Design Server and
Runtime Server are installed together in the SAS Visual Process Orchestration
Server directory. The two servers share several configuration files,
and each server has its own configuration file.
The Design Server encrypts
network communication with SAS clients and servers. The Runtime Server
can be configured use SSL protection for its SOAP interface. SSL uses
encryption, certificates, and HTTPS addresses to protect client connections.
Both the Design Server
and Runtime Server can be configured to use any of several upgraded
encryption algorithms.