Here are the criteria for determining whether or not HostBridge requests can be run without the CWXN transaction:
- You must be running CICS TS 5.3 or later.
- You must be running HostBridge 6.78 or later.
- You must define a set of URIMAPS and a new TCPIPSERVICE definition to allow CICS to realize that the incoming HostBridge request is eligible for CWXN elimination. Examples of these definitions will follow.
- You must be issuing HostBridge requests to CICS using the HTTP protocol. Any requests using SSL are not eligible for CWXN elimination, however AT-TLS requests are. With this AT-TLS configuration, CICS sees the incoming data as HTTP, not HTTPS, because TCP/IP handles the handshaking and encryption/decryption. This means that unlike CICS in an SSL environment, in this scenario CICS TS V5.3 can take advantage of eliminating the CWXN transaction.
- You must indicate in your URIMAP definitions that there is no analyzer program to execute by setting the ANALYZER parameter to NO.
- You must not issue be issuing HostBridge requests where HostBridge is defined as a trusted host (see the documentation for the HB_TRUSTED_HOST and HB_TRUSTED_USERID directives for more information about HostBridge being defined as a trusted host). This capability (also known as asserted ID) Since this capability requires an analyzer program, it is incompatible with the CWXN elimination enhancement.
- You must not be issuing HostBridge requests where authentication is done using the HostBridge "Asserted ID" capability. Since this capability requires an analyzer program, it is incompatible with the CWXN elimination enhancement.
- You must not be issuing HBX script requests (as opposed to HB.js). They are not candidates for CWXN elimination.
- You must not be using the HBR$AUTH security exit. That exit and its processing is incompatible with the CWXN elimination enhancement.