Options for controlling requester pipeline processing

In service requester pipelines, message handlers can determine where the web service request is sent by changing the URI. CICS provides support for different URI formats so that you have much more flexibility in the way that the pipeline processes web service requests.

When the service requester pipeline reaches the end of its processing, you have the following options:

Linking to a program
If you change the URI to the format cics://PROGRAM/program, where program is the name of the target application program, CICS passes the current channel and its containers or COMMAREA to the program using an EXEC CICS LINK command.
This processing is similar to the local optimization that occurs when the service requester and service provider applications are in the same CICS region. However, using this URI format provides the benefit of running the request through the pipeline and any custom message handlers first. The target application program must be able to handle the contents of the containers or COMMAREA.
Starting another requester mode pipeline
If you change the URI to the format cics://PIPELINE/pipeline?targetServiceUri=targetServiceUri, where pipeline is the name of a PIPELINE resource and targetServiceUri is the URI that you want to put in the DFHWS-URI container, CICS passes the current channel and its containers to the specified requester pipeline. Use this URI when you want to link two or more requester pipelines together before sending the request to the service provider. The number of requester pipelines that you can chain together is not limited.
In the following example, one generic requester pipeline supports one application. Message handlers 1 or 2 can change the URI for each request depending on the application data in the containers, sending the request to one of two requester pipelines that contain different message handlers.
The image shows an application program linking to a service requester pipeline with two handlers in it. The requester pipeline has links to two different requester pipelines, each with a different set of message handlers. The request processes through either of these pipelines before going to different service providers.
Although the example shows only one service requester application, many applications could use the same generic requester pipeline and have their requests sent to different requester pipelines before the request is finally sent to the appropriate web service provider.
Sending the request straight to the provider mode pipeline
If you change the URI to the format cics://SERVICE/service?targetServiceUri=targetServiceUri, where service is the name of the target service and targetServiceUri is the path to the service, CICS resolves the request by matching the path to a URIMAP and passes the request to the correct provider pipeline. Use this option when you want to take advantage of processing the request through both the requester and provider pipelines without using the network.
This URI might also be useful where the requester and provider applications are written in different languages, or use different mapping levels, and expect different binary data.


dfhws_pipelineoptions.html | Timestamp icon Last updated: Sunday, 4 June 2017