If your service flow is deployed as a Web service provider,
you can use the existing Web services support in CICS to invoke it.
Before you begin
You must enable the provider PIPELINE resource to process
the Web service request and response messages and the WEBSERVICE and
URIMAP resources for your Web service provider application. If the
request is using HTTP, you must also have an enabled TCPIPSERVICE
resource.
About this task
To invoke a service from a Web service, follow these steps:
Procedure
- Send the SOAP message from the service requester to the
Web service provider. The SOAP message body contains the
request message. The contents vary depending on what you modeled in service flow project tools.
- By default, the SOAP body includes the request name of the service
flow that you want to invoke and any application data.
- If you select to expose the whole message header, the SOAP body
includes the DFHMAH header structure and any application data.
The provider mode pipeline processes the SOAP
message, and the contents of the SOAP body are placed in the DFHWS-DATA
container by default. If you select to expose the whole message header
in service flow project tools, the DFHMAC-ALLPARMS
container is used instead.
- The application handler in the pipeline passes the appropriate
container to the CICS SFR interface
program DFHMADPL.
- DFHMADPL checks the channel for additional containers. If you have added additional message handlers to the pipeline
to override the contents of DFHWS-DATA with the DFHMAC-SYSPARMV1 or
DFHMAC-LNK3270V1 containers, DFHMADPL uses the values in these containers
instead.
- DFHMADPL defines and runs the BTS process for the Navigation
Manager to invoke the service flow using the values in the containers.
- If the request message is successfully processed and a response
is required, the interface program DFHMADPL places the response in
the DFHWS-DATA or DFHMAC-ALLPARMS container. The pipeline creates
a SOAP response message and sends it to the service requester.
- If an error occurs, the interface program creates a SOAP fault
message which is sent to the service requester instead. Details of
the error are also placed in the DFHMAC-ERROR container on the channel.