Web Services tuning

If the target of the Web Services import binding is hosted locally in the same application server, the performance can be further improved by exploiting the optimized communication path provided by the Web container.

In general, requests from the Web Services clients are sent through the network connection between the client and the service provider. For local Web Services calls, however, WebSphere® Application Server offers a direct communication channel, which bypasses the network layer completely. You can use the following steps to enable this optimization in the administrative console.

• Set the Web container custom property enableInProcessConnections to true by clicking Application servers > server_name > Container Settings > Web Container Settings > Web container > Additional Properties > Custom Properties.
• Do not use a wildcard (*) for the host name of the Web Container port. Use the host name or IP address instead. The property can be accessed by clicking Application servers > server_name > Container Settings > Web Container Settings > Web container > Additional Properties > Web container transport chains > WCInboundDefault > TCP inbound channel (TCP_2) > Related Items > Ports > WC_defaulthost > Host.
• Use localhost instead of the host name in the Web Services client binding. If the actual host name is used and even if it is aliased to localhost, this optimization is disabled. The property can be accessed by clicking Enterprise Applications > application_name > Manage Modules > application EJB jar > Web services client bindings > Preferred port mappings > binding_name. Use localhost (for example, localhost:9080) in the URL.
• Make sure there is not an entry for your server host name and IP address in your server hosts file for name resolution. An entry in the hosts file inhibits this optimization by adding name resolution overhead.