Download PDF (1.3 MB) - IBM Redbooks

Complete the following steps to enable this optimization. Use the administrative console to
change these values.
1. Click Application servers and the then the name of the server that you want. Click
Container Settings Web Container Settings Web container Additional
Properties Custom Properties. Set the web container custom property
enableInProcessConnections to true.
Do not use wildcard characters (*) for the host name of the web container port. Replace it
with the host name or IP address. The property can be accessed by clicking the following
path:
Application servers messaging engine 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.
2. Use localhost instead of host name in the web services client binding. Using the actual
host name (even if it is aliased to localhost), disables this optimization. To access the host
name, use the following steps:
a. Click Enterprise Applications and select the application name.
b. Click Manage Modules and select the application EJB JAR file.
c. Click Web services client bindings Preferred port mappings and select the
binding name.
Use the localhost (for example, localhost:9080) in the URL.
3. Make sure that there is not an entry for the server host name and IP address hosts file of
your server for name resolution. An entry in the hosts file inhibits this optimization by
adding name resolution processor usage.
4.7.7 Tuning Human Workflow for Business Space
The following optimizations are applicable when you use the Advanced Human Workflow
Template with Business Space clients.
Optimizing performance when not using federation mode
If you are familiar with the performance characteristics of Human Workflow widgets with
WebSphere Process Server V7.0, you might experience an initial performance degradation
when using Human Workflow widgets such as Tasks, Processes, and Task Definitions in
Business Process Manager V8.0. This degradation is apparent only if you use Business
Space on a new (not a migrated) installation of Business Process Manager V8.0. These
performance considerations apply if you use the Human Task Management widgets with only
Business Process Definition (BPD) processes and human services on a single application
server, or on a cluster.
This performance degradation is caused by the addition of a federation service layer and the
higher number of items to be retrieved. Addition of the federated service layer is a usability
enhancement initially delivered in Business Process Manager V7.5 that enables the display of
all tasks in a single unified task list.
Chapter 4. Performance tuning and configuration 71