This path should start with a forward slash (/).
A Web Service request creates a new order which is added to the job chain.
Cannot be used with the
request_xslt_stylesheet
and
response_xslt_stylesheet
attributes.
See
When an order is not forwarded to the first job within the allocated waiting time,
then the JobScheduler will reject HTTP call with "504 Gateway Timeout
"
and cancel the order with a
The path to the XSLT style sheet with which the XML document forwarded using HTTP-POST is transformed into a JobScheduler command.
Cannot be used with the job_chain
attribute.
The path to the XSLT style sheet used to transform the XML result of the JobScheduler command into an XML document. This style sheet is used to answer a Web Service query.
Cannot be used with the job_chain
attribute.
Valid for an order which has been started with
forward_xslt_stylesheet
has been specified.
Transforms the order or task with the style sheet to a
Cannot be used with the job_chain
attribute.
xercesImpl.jar
class archive in the CLASS_PATH
(see
Only when request_xslt_stylesheet
is specified:
debug="yes"
- the JobScheduler allows internally created XML documents
to be saved in the directory specified with
service_name.transaction_number.raw_request.txt |
The text forwarded with HTTP-POST |
service_name.transaction_number.service_request.xml |
The |
service_name.transaction_number.command.xml |
The command created using request_xslt_stylesheet |
service_name.transaction_number.service_response.xml |
The Web Service response transformed using response_xslt_stylesheet |
service_name.forward.xml |
The forward_xslt_stylesheet
(without the transaction number, which is not known here) |
The JobScheduler does not clean up the files.
<web_service name = "my_web_service" url_path = "/webservice" job_chain = "my_service_job_chain" />
<web_service name = "my_web_service" url_path = "/webservice" request_xslt_stylesheet = "$SCHEDULER_CONFIG/web_service_request.xsl" response_xslt_stylesheet = "$SCHEDULER_CONFIG/web_service_response.xsl" forward_xslt_stylesheet = "$SCHEDULER_CONFIG/web_service_forward.xsl" />
Web services can be set up to create orders or tasks and immediately answer requests. The results of these orders or tasks can be forwarded to another Web Service.
The TCP port for the HTTP-Server is specified using
The JobScheduler creates an order in response to a HTTP-POST to the Web Service URL.
It then adds this order to the job chain queue.
Jobs can access the HTTP data using
In this case a HTTP-POST to the Web Service URL initiates the following steps:
<service_request> <web_service name="service_name" url_path="url_path"/> <content>…xmldata…</content> </service_request>
<service_request>
is transformed into an XML command using the
request_xslt_stylesheet
style sheet -
usually <spooler>
response_xslt_stylesheet
style sheet to a <service_response> <content>…xmldata…</content> </service_response>
request_xslt_stylesheet
style sheet can immediately
send out a
When it is not possible to forward an XML document using POST,
then a "404 Bad Request" HTTP error code will be generated.
An error in the transformation causes a HTTP "500 Internal Server Error" error code.
Orders and tasks can be allocated to a Web Service.
In this case, the web_service="service_name"
attribute.
Such orders and tasks are transformed by forward_xslt_stylesheet
and forwarded as
forward_xslt_stylesheet
:
<order service="service_name" last_job="job_name" …> <payload> <params> … </params> </payload> <log last_error="…" last_warning="…"/> … </order>
and
<task job="…" …> <log last_error="…" last_warning="…"/> … </task>
The result of the transformation is a
<service_request url="url"> <content>…data…</content> </service_request>
The JobScheduler packs the scheduler_service_forwarding
job chain.
The only job in the scheduler_service_forwarder
job chain.
Uses a URL to make a HTTP connection, transfers data using POST and
waits for the answer, which it then logs.
The properties of this job can be defined in the configuration file in the same way as if the job
were published using
<job name="scheduler_service_forwarder"> <delay_order_after_setback setback_count="1" delay="00:01"/> <delay_order_after_setback setback_count="2" delay="01:00"/> <delay_order_after_setback setback_count="3" delay="24:00"/> <run_time> <period begin="07:00" end="17:00"/> </run_time> </job>
The job has been implemented in Java (see also