The Web messaging service must be enabled for a Web messaging enabled application to run. Due to the duration that Web messaging requests stay open, the existing Web container is not able to scale to handle more concurrent clients than the Web container thread pool. To solve this problem, the Web messaging service provides a new channel framework channel and chain that shares ports with existing Web container transport chains. By default, the Web messaging transport chain is not enabled. To start the Web messaging transport chains, a custom property must be set on a Web container channel in an existing transport chain. You must identify which Web container transport chains need to be configured to run Web messaging requests before enabling this custom property.
There are two default Web container transport chains that serve Web traffic. These two transport chains are named WCInboundDefault and WCInboundSecure. In most cases you should determine whether you will be running Web messaging requests over HTTP or HTTPS. If you are running requests over HTTP only, follow the steps below to enable the Web messaging service on the WCInboundDefault transport chain. If you require a secure connection over HTTPS, follow the steps below for the WCInboundDefaultSecure transport chain. If Web message traffic is coming in on both HTTP and HTTPS, enable the Web messaging service on both WCInboundDefault and WCInboundDefaultSecure chains. If you end up configuring a transport chain and not handling Web messaging requests through that transport chain, there is a very small amount of overhead to determine if the Web messaging channel is involved in the request.
Procedure
Enabling the Web messaging service on z/OS
After completing the previous steps, follow the steps below to complete Web messaging enablement on z/OS.
It is possible that additional Web container transport chains have been enabled to serve Web traffic. To determine if the Web messaging service should be enabled for these transport chains, determine which Virtual hosts your Web messaging enabled application will be installed to, then enable the corresponding transport chains that match the virtual host's ports.
In some situations, it might be desirable to create a new Web container transport chain for the sole purpose of handling Web messaging requests. Please refer to the developer works Know your proxy server basics developer works article. The section provides info on created a new Web container transport chain with it's own thread pool.