08.06.2014 Views

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4.9.2 Disabling event distribution for Common Event Infrastructure<br />

The event server that manages events can be configured to distribute events and log them to<br />

the event database. Some mediations only require events to be logged to a database. For<br />

these cases, performance improves by disabling event distribution. Because the event server<br />

might be used by other applications, it is important to check that none of them use event<br />

monitoring, which requires event distribution before disabling event distribution.<br />

Event distribution can be disabled from the administrative console by clicking Service<br />

integration Common Event Infrastructure Event service Event services <br />

Default Common Event Infrastructure event server. Clear the Enable event distribution<br />

check box.<br />

4.9.3 Configuring WebSphere Service Registry and Repository cache timeout<br />

WebSphere Service Registry and Repository (WSRR) is used by WebSphere ESB for<br />

endpoint lookup. When accessing the WSRR (for example, using the endpoint lookup<br />

mediation primitive), results from the registry are cached in WebSphere ESB. You can<br />

configure the lifetime of the cached entries from the administrative console by clicking<br />

Service Integration WSRR Definitions and entering the WSRR definition name. Then<br />

click Timeout of Cache and set a value for the cached registry results.<br />

Validate that the timeout is a sufficiently large value. The default timeout is 300 seconds,<br />

which is reasonable from a performance perspective. A value that is too low results in<br />

frequent lookups to the WSRR, which can be expensive (especially if retrieving a list of<br />

results) and includes the associated network latency if the registry is on a remote machine.<br />

4.10 Business Monitor tuning<br />

This section provides advanced tuning suggestions for Business Monitor.<br />

4.10.1 Configuring Java heap sizes<br />

The default maximum heap size in most implementations of Java is too small for many of the<br />

servers in this configuration. The Business Monitor Launchpad installs the Business Monitor<br />

and its prerequisite servers with larger heap sizes, but you might check that these sizes are<br />

appropriate for your hardware and workload.<br />

4.10.2 Configuring Common Event Infrastructure<br />

By default, when an event arrives at CEI, it is delivered to the registered consumer (in this<br />

case, a particular monitor model) and into an additional default queue. Performance improves<br />

by avoiding this double-store by removing the All Events event group:<br />

1. In the administrative console, click Service Integration Common Event<br />

Infrastructure Event Service Event Services Default Common Event<br />

Infrastructure event server Event Groups<br />

2. Remove the event group.<br />

76 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!