Process Scheduler Service
This section discusses the PROCESSREQUEST service.
Services are used to logically group a set of service operations. The service PROCESSREQUEST contains all of the service operations for Process Scheduler. When you publish a web service, a WSDL document is created containing all of the selected service operations as well as the endpoints based on the Service Configuration.
See Using the Service Configuration Page to Set Service Configuration Properties.
Image: Providing PROCESSREQUEST web service
This diagram illustrates how a client application consumes the web service
The Service page provides links to Provide Web Service and to Generate SOAP Template. The Provide Web Service wizard generates a WSDL document containing all of the service operations selected. This WSDL document is consumed by the client application.
The published web service is stored in the WSDL Repository. Client applications consume the WSDL by accessing the WSDL URL from the repository. The WSDL for PROCESSREQUEST is delivered and updated with the appropriate WSDL Repository location whenever the target location is updated on the Service Configuration page (Select PeopleTools, Integration Broker, Configuration, Service Configuration).
To view the generated WSDL Repository for the PROCESSREQUEST, click the View WSDL link on the service page.
Image: WSDL Repository page for PROCESSREQUEST service
This example illustrates the fields and controls on the WSDL Repository page for PROCESSREQUEST service.
All of the service operations contained in the WSDL are listed in the Exported Service Operations section. Use the View WSDL link to view the WSDL document.
The WSDL document is created by means of the request and response message schemas for each service operation. To view the message schema, select PeopleTools, Integration Broker, Integration Setup, Messages and select the message to view. Select the Schema tab to view the schema.
For each service operation, you can use the Generate SOAP Template utility to generate SOAP message templates for request messages, response messages, and fault messages found in the WSDL document. The generated SOAP template will include WS-Security SOAP Header tags. You can then use the templates to test SOAP messages in your third-party application.