IBM® Content
Navigator is installed with default settings. Based
on your hardware environment, you can tune or change some settings to improve IBM Content
Navigator performance. Tuning makes the system run faster and work
more efficiently.
Important: The parameters are intended for use as tuning tools to improve
performance, not as troubleshooting tools. For best results, tune the default parameters
after installation.
In addition to tuning
IBM Content
Navigator, you can tune the other
components that work with
IBM Content
Navigator, such as databases
or repository components. Make sure to tune those components before you tune the
IBM Content
Navigator settings. Also, be sure to tune the
IBM Content
Navigator settings before you put the system into production.
The components that you can tune include:
- IBM Content
Navigator
- Web application servers, such as WebSphere® Application
Server or
Oracle WebLogic Server
- Databases (DB2®, DB2 for z/OS®, DB2 pureScale®,
Microsoft SQL
Server, Oracle database, or Oracle RAC
database)
- IBM FileNet® Content Manager
- FileNet P8 components
- IBM Content
Manager
- Content Manager OnDemand
- Operating systems
The following operations can dramatically increase the processor usage of
IBM Content
Navigator, based on the size and complexity of the documents:
- Download as PDF or use of the PDF Conversion Viewer
- Preview documents or use of the HTML Conversion Viewer
- Thumbnail rendering
- Viewing documents with IBM Daeja
ViewONE Virtual Viewer, AJAX
Viewer
- Viewing AFP or Line data with AFP2PDF or Line2PDF conversion
Simple documents, such as plain text, do not cause significant processor usage. Larger,
complex documents however, can cause a significant increase in IBM Content
Navigator processor usage. You must allocate sufficient
resources to your IBM Content
Navigator server to keep up with
processor usage.
The performance tuning topics include suggested parameter settings. Performance information
is provided for your consideration so that you can determine the appropriate settings to fit
your environment. This tuning is an iterative process. The correct tuning for your system is
based on your environment and your usage. Tuning results differ for each user, depending on
the environments and the components used.