Download PDF (1.3 MB) - IBM Redbooks

4.4.3 Locate the Process Portal physically close to the Process Server
One factor that influences network latency is the physical distance between systems. Where
practical, locate Business Process Manager V8.0 servers physically close to each other and
to the Process Portal users to minimize the latency for requests.
4.4.4 Use the WORK tab to refresh the Task List
Instead of refreshing the entire Process Portal browser page through F5 or a similar
mechanism, click the WORK tab on the Process Portal browser page. This way refreshes only
the tasks in the task list, and not refresh the entire browser page.
4.4.5 Use modern desktop hardware
For many Business Process Manager solutions, much of the processing is done on the client
system (for example browser rendering). Therefore, be sure to deploy modern desktop
hardware with sufficient physical memory and high-speed processors with large caches and
fast front-side buses. Monitor your client systems with performance tools (Windows Task
Manager or vmstat) to ensure that the client system has sufficient processor and memory
resources to yield high performance.
4.4.6 Disable or uninstall add-ins or extensions
An important consideration is using add-ins or extensions in your browser. If you experience
problems, always disable or uninstall all add-ins or extensions unless they are necessary.
4.5 Business Processing Modeling Notation business process
tuning
In addition to the common tuning guidance, this section provides tuning guidance that is
specific to BPMN business processes. Much of this tuning applies to the Performance Server
and the Performance Server’s database.
4.5.1 Tune the Process Server Database
The following list indicates the ways that databases can be tuned for better performance. In
addition to these items, see 4.13, “General database tuning” on page 80 and vendor-specific
database tuning sections (4.14, “DB2-specific database tuning” on page 82 and 4.15,
“Oracle-specific database tuning” on page 88).
► Increase log file size for the Process Server database to 16,384 pages.
►
►
Enable file system caching for the Process Server database as follows (this example is for
DB2):
db2 alter table space userspace1 file system caching
Exclude the table SIBOWNER from automatic runstats execution as described in the
following technote:
http://www.ibm.com/support/docview.wss?uid=swg21452323
Chapter 4. Performance tuning and configuration 57