z/OS Connect: Enable back-end service selection based on a header value (intelligent routing)

z/OS Connect: Enable back-end service selection based on a header value (intelligent routing)

In z/OS Connect EE, provide service selection based on a HTTP request header content.

1. Define a HTTP request header as a criteria for routing
2. Select a
zosconnect_localAdaptersConnectService
or
registerName
based on the header content.

Example 1:
A service invocation:
https://xxxx.com/queryAcct and Request header “Country: XX”

in zosconnect_zosConnectService
define routeHeader=”Country”

<zosconnect_zosConnectService id="CARDSREQ"
invokeURI="/queryAcct"
serviceName="CICS-CARDS"
dataXformRef="cardsJSON2Byte"
routeHeader=”Country”
serviceRef="cardsCICS"/>

Then in zosconnect_localAdaptersConnectService select a registerName conneciton based on the routeHeader content, with a logic similar to a "case" selection statement.
This will allow for the same back-end service program name, but from a different CICS connection or with different START_SRVR parameters.

<zosconnect_localAdaptersConnectService id="cardsCICS"
serviceName="GBOJCRRD"
connectionFactoryRef="wolaCF"
case routeHeader
routeValue=”US” registerName="US_CICS"
routeValue="MX" registerName="MX_CICS"
routeValue=”CA” registerName="CICS001"
routeValue=”*” registerName="DEFAULT_CICS"
/>


Example 2:
A service invocation:
https://xxxx.com/queryAcct and Request header “Country: XX”

in zosconnect_zosConnectService
define routeHeader=”Country”
then select a serviceRef based on the header value
This will allow for a completely different back end service program, or CICS region etc.

<zosconnect_zosConnectService id="CARDSREQ"
invokeURI="/queryAcct"
serviceName="CICS-CARDS"
dataXformRef="cardsJSON2Byte"
routeHeader=”Country”
routeValue1=”US”
serviceRef1="cardsUS"
routeValue2=”MX”
serviceRef2="cardsMX"/>

serviceRef1, serviceRef2 may contain different LinkTaskTranID, or serviceName - program name, etc