IBM Content Navigator, Version 2.0.3
Supports:
Content Manager, FileNet P8, OnDemand, OASIS CMIS
Preparing your web application server for IBM Content
Navigator components
There are several changes that you must make to your web
application server configuration in order to support IBM® Content
Navigator components.
Before you begin
Remember: You must have sufficient memory in the
Java virtual machine (JVM) in the web application server where you
plan install and deploy IBM Content
Navigator components:
If you are deploying to WebSphere® Application
Server,
you must increase the JVM minimum heap size on the web application
server to at least 1 GB or, preferably, to 2 GB. This setting prevents
the web application server from hanging when deploying IBM Content
Navigator components.
If you are deploying to WebSphere Application
Server Network Deployment,
you must increase the JVM minimum heap size on the deployment manager
to at least 1 GB or, preferably, to 2 GB. This setting prevents the
web application server from hanging or running out of memory when
deploying IBM Content
Navigator components.
If you are deploying to Oracle WebLogic Server,
you must set the memory arguments (MEM_ARGS)
parameter to at least 1 GB or, preferably, to 2 GB. This prevents
the web application server from running out of memory when deploying IBM Content
Navigator components.
About this task
Complete the tasks appropriate to your environment:
Preparing WebSphere Application Server for IBM Content Navigator components
Before you install and deploy IBM Content
Navigator components, you must
prepare WebSphere Application
Server for IBM Content
Navigator components. The steps
that you must complete depend on the repositories that you are connecting
to and the components that you are deploying.
Preparing Oracle WebLogic Server for IBM Content Navigator
Before you can install and configure IBM Content
Navigator, you must prepare Oracle WebLogic Server for IBM Content
Navigator components. The steps
that you must complete depend on the repositories that you are connecting
to and the components that you are deploying.