A Web
service job is a SAS Data Integration Studio job that is designed
to be executed by a Web service client. The process flow for a Web
service job has these requirements:
-
The job can receive zero or more
inputs from the Web service client that executes the job.
-
The job can send zero or one output
to the client that executes the job.
-
Input to the job from the client,
and output from the job to the client, must be in XML table format.
-
The XML tables that specify client
input or output in the job must be members of a SAS XML library. For
details about SAS XML libraries, see the
SAS XML LIBNAME
Engine: User's Guide.
-
The XML table for a client input
can have an XMLMap associated with it through the library. An XMLMap
can help the XML LIBNAME engine to read the table. However, the XML
table that specifies a client output cannot have an XMLMap associated
with it through the library.
-
The XML table for each client input
or output in the job must have a unique libref.
-
The XML table for each client input
or output in the job must be configured as a Web stream.
The following
display illustrates a typical process flow for a Web service job.
Sample Process Flow for a Web Service Job
In the
sample flow, INTABLE is a metadata object for an input table in XML
format. Convert Temp GT is a generated transformation with custom
SAS code that processes the input. OUTTABLE is a metadata object for
an output table in XML format. The small blue circle that overlays
the table icons indicates that the input table and output table are
configured as Web streams.
The preceding
Web service job is deployed as a stored process. Then the stored process
is deployed as a Web service. Users with Web client software access
the Web service job, and they are prompted to supply input. The job
processes the input and displays the result to the Web client.