A service requester is the application that is looking for and invoking or initiating an interaction with a service.
The requester role can be played by a browser driven by a person, or a program without a user interface, e.g. a Web service. A service requester issues one or more queries to locate a service and to determine how to communicate with that service.
At run time, a service requester is looking for and invoking an interaction with the adapter service that has been deployed to the CICS® Service Flow Runtime. The following table lists the supported interfaces that a service requester can use to pass in the message header and application data.
Service requester type | Interface used |
---|---|
WebSphere® MQ-enabled application | WebSphere MQ-CICS bridge. This product serves as the interface between an WebSphere MQ-enabled service requester and CICS. The request message is passed in a WebSphere MQ message to a WebSphere MQ message queue. |
Non-WebSphere MQ applications | A CICS-supplied interface, such as EXEC CICS
LINK, EXCI or ECI.
The IBM® CICS Transaction Gateway (CTG) product. |
If you want to implement a passthrough deployment type to process requests from the service requester, you must program the service requester to handle the passthrough response, one screen at a time.
For passthrough processing, the service requester is responsible for interpreting the application data structure (ADS) and based on its interpretation, taking appropriate action in the language of the service requester.