Routing inbound web service requests

You can use a distributed routing program to dynamically route inbound web service requests.

Dynamic routing of inbound requests in a terminal handler
When the terminal handler of a service provider pipeline is one of the CICS-supplied SOAP message handlers, the target application handler program specified in container DFHWS-APPHANDLER is, in some cases, eligible for dynamic routing. All pipeline processing before the application handler program is always performed locally in the CICS region that received the SOAP message.
When the distributed routing program is invoked
Changing the target CICS region
Telling CICS whether to route the request
When the routing program is invoked for routing, if you want the request to be routed (whether you have changed any values or not) return a zero value to CICS in field DYRRETC of the communications area.
If an error occurs in route selection
If an error occurs in route selection—for example, if the sysid returned by the distributed routing program is unavailable or unknown—the routing program is invoked again.
Invoking the distributed routing program on the target region
The route selection, notification, route selection error, and routing complete invocations of the distributed routing program all occur on the routing region. However, you can re-invoke the routing program on the target region.

Parent topic: Writing a distributed routing program

Related concepts

Routing BTS activities
Routing by user ID
Dealing with an abend on the target region
Link checks and information for distributed routing programs

Related tasks

Naming your distributed routing program
Assembling and link-editing user-replaceable programs

Related reference

Differences between the distributed and dynamic routing interfaces
Parameters passed to the distributed routing program
Distributed transaction routing sample programs