z/OS Connect EE: in APIs, enable selection of service based on input data (i.e. http header value) Merged

z/OS Connect EE: in APIs, enable selection of service based on input data (i.e. http header value)

This is another possible solution for the RFEs:
z/OS Connect: Enable back-end service selection based on a header value (intelligent routing) (86399)
and
z/OS Connect: set dynamic code page selection by a header value (87866)

This is to enable the APIs to select a service based on context, or some input data value.

Designate a pre-select input API variable, i.e. a http header, as a selection criteria, and use its value to select a service from a list of available services. The rest of the parameters (method, mapping, etc.) should remain unchanged, and passed to the selected service.

Multiple services should be available to the API. The eligible services should all use the same data and input/output mapping, and be all added to the API. The difference between the services would be
1. code page
2. back-end CICS routing
and more, as needed.

This will allow indirect selection of a code page, and a back-end CICS connection, based on the input.

Please see example below.

Please note that a solution based on the original RFEs:
z/OS Connect: Enable back-end service selection based on a header value (intelligent routing) (86399)
and
z/OS Connect: set dynamic code page selection by a header value (87866)
would be also acceptable, and would lower the number of services that need to be defined and maintained.