Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4.3.7 Messaging engine properties<br />
Two messaging engine custom properties might affect the messaging engine performance:<br />
► sib.msgstore.discardableDataBufferSize<br />
– The property stays in the data buffer for best effort nonpersistent messages.<br />
– The default value is 320 KB.<br />
– After the buffer is full, messages are discarded to allow newer messages to be written<br />
to the buffer.<br />
► sib.msgstore.cachedDataBufferSize<br />
– The property stays in memory cache for messages other than best-effort<br />
nonpersistent.<br />
– The default is 320 KB.<br />
To access these properties in the console, use the following steps:<br />
1. Click Service Integration Buses and select the bus name.<br />
2. Click Messaging Engines and select the messaging engine name.<br />
3. Click Additional properties Custom properties.<br />
4.3.8 Running production servers in production mode<br />
Business Process Manager servers can be run in development mode to reduce startup time<br />
for the server by using JVM settings to disable bytecode verification and reduce just-in-time<br />
(JIT) compilation time. Do not use this setting on production servers because it is not<br />
designed to produce optimal runtime performance. Make sure to clear the Run in<br />
development mode check box for the server. This setting is found in the configuration<br />
window of the server in the administrative console. Click Servers Application Servers.<br />
Click the server whose setting you want to change and click Configuration.<br />
You might also create server profiles with production or development templates. Use<br />
production profile templates for production servers.<br />
4.4 Process Portal tuning and usage<br />
This section contains tuning advice and usage guidelines for the Process Portal.<br />
4.4.1 Using a high-performing browser<br />
The choice of browser technology is crucial to Process Portal performance. In some cases,<br />
more recent versions of the browser will perform much better than older versions..<br />
4.4.2 Enable browser caching<br />
Browsers generally cache static data after it is initially retrieved from the server, which can<br />
significantly improve response time for scenarios after the cache is primed. This improvement<br />
is especially true for networks with relatively high latency. Ensure that the browser cache is<br />
active and is effective. Note that cache settings are browser-specific; see 4.11, “Enable<br />
browser caching” on page 78 for further details.<br />
56 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices