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.

Use the following procedure to enable cache clearing:<br />

1. Click Tools Options.<br />

2. Click the Privacy tab and make sure that it reads Firefox will: Remember History. Click<br />

OK. This setting enables caching.<br />

If you click Never remember history, caching is disabled and you must change the<br />

setting.<br />

If you click Use custom settings for history, you have additional options that still allow<br />

caching:<br />

– If you select Automatically start Firefox in a private browsing session, caching is<br />

enabled. However, after the browser is closed, everything is erased (not only cache,<br />

but also browsing history) as though you were never using the browser.<br />

– If private browsing is not selected, make sure the Clear history when Firefox closes<br />

check box is cleared.<br />

3. Restart the browser to apply the changes.<br />

4.12 Tuning the HTTP server<br />

The Process Server and Process Center in production scenarios are generally deployed by<br />

using a topology that includes an HTTP server or an HTTP server plug-in. The Process Portal<br />

and Process Designer send multiple requests to their respective server, which are then<br />

handled by this HTTP server. To minimize the number of requests and the size of the<br />

response data to obtain good user response times, tune your HTTP server to efficiently<br />

handle the expected load.<br />

In particular, ensure that caching is effectively enabled in the HTTP server. Much of the<br />

content that is requested by the Process Portal and Process Designer is static (for example<br />

images and JavaScript files), and can be cached in the browser. Of course, ensure that<br />

browser caching is enabled first, but also tune the HTTP server to support caching at that<br />

level. Specifically in the httpd.conf file, use the following caching and compression settings:<br />

► nExpiresActive on<br />

► ExpiresByType image/gif A86400<br />

► ExpiresByType image/jpeg A86400<br />

► ExpiresByType image/bmp A86400<br />

► ExpiresByType image/png A86400<br />

► ExpiresByType application/x-javascript A86400<br />

► ExpiresByType text/css A86400<br />

Tip: 86400 seconds = 1 day<br />

For more information about tuning the <strong>IBM</strong> HTTP Server, which is included as part of<br />

Business Process Manager V8.0, see the <strong>IBM</strong> HTTP Server Performance Tuning page:<br />

http://publib.boulder.ibm.com/httpserv/ihsdiag/ihs_performance.html<br />

For more information about tuning Business Space, see Scalability and Performance of<br />

Business Space and Human Task Management Widgets in WebSphere Process Server v7<br />

white paper:<br />

http://www.ibm.com/support/docview.wss?uid=swg27020684&wv=1<br />

Chapter 4. Performance tuning and configuration 79

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

Saved successfully!

Ooh no, something went wrong!