You must specify the IBM® WebSphere® Application Server environment
variables so that Content Platform Engine can
access its databases.
See IBM FileNet® P8 system requirements for
information on the JDBC driver file for the database type that you
need for the global configuration database (GCD)
or for an object store or Case Analyzer store
you create later. The version of the JDBC driver file must match the
version of the JDK on the system where WebSphere Application
Server is installed.
To specify the WebSphere environment
variables:
- Install JDBC drivers on each WebSphere Application
Server node where you will deploy Content Platform Engine.
- Obtain the JDBC drivers for your database type.
- DB2®
- Access the IBM Web site and
find the version of the Redistributable DB2 JDBC
Driver that matches the version of the JDK on the system where WebSphere Application
Server is installed.
- Microsoft SQL
Server
- Access the Microsoft Support
web site and find the version of the SQL Server JDBC Driver that matches
the version of the JDK on the system where WebSphere Application
Server is installed.
- Oracle
- Access the http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html Web site and find the JDBC driver file that
matches the version of the JDK on the system where WebSphere Application
Server is installed.
- Extract and copy the JDBC driver file to the following
suggested location:
- AIX®, HPUX,
HPUXi, Linux, Solaris
- /opt/jars
Do not copy the file to ...WebSphere/AppServer/lib/ext.
- Windows
- C:\jars
Do not copy the file to ...WebSphere\AppServer\lib\ext.
- Start the WebSphere Application
Server administrative
console and log on to your Content Platform Engine profile
as appserver_console_user, the Administrator Console
User and complete the following substeps to configure the Content Platform Engine nodes or cluster (if
applicable).
- Navigate to .
- Select Cell scope from the All
scopes list.
- Set the value of the variable to the JDBC driver path
that you specified when you installed the JDBC drivers on the IBM WebSphere Application Server machine. (If the variable
does not exist, create it and then set its value.)
- Select Node scope from the All
scopes list. In a cluster configuration, select Node
scope for all the nodes in the Content Platform Engine cluster.
- In the table of substitution variables, click the item
name in the Name column
that corresponds to the JDBC environment variable for your database
type in the Database environment variables table below.
- Set the value of the name_JDBC_DRIVER_PATH
item to the JDBC driver path you specified (/opt/jars or C:\jars).
- Optional: Select Server scope from
the All scopes list. This step is not required
unless you defined the JDBC_DRIVER_PATH variable at the server scope
level.
- In the table of substitution variables, click the item
name in the Name column
that corresponds to the JDBC environment variable for your database
type in the Database environment variables table.
- Set the value of the name_JDBC_DRIVER_PATH
item to the JDBC driver path you specified (/opt/jars or C:\jars).
- Save your changes to the master configuration.
- Navigate to , and set the initial and maximum heap sizes, where server1 is
the name of the server where you will deploy Content Platform Engine.
- Set the values for the initial and maximum heap sizes:
Table 2. Values for initial and maximum heap sizeParameter |
Value (in MB) |
Initial Heap Size |
At least 512 |
Maximum Heap Size |
1024 or a size consistent
with available RAM on the machine where WebSphere Application
Server is installed |
- Save your changes to the master configuration.
- Optional: Increase the maximum transaction
timeout to prevent administrative processes from failing:
- Navigate to the screen containing the Maximum
transaction timeout parameter:
- Click the Configuration tab,
and set the Maximum transaction timeout parameter
value to at least 600 (seconds), and increase the Total
transaction lifetime timeout as well.
Important: If the timeout value is not large enough, some administrative
processes (such as adding an expansion product) might fail.
- Click Apply and then click Save.
- Repeat this procedure as needed for any object store that
uses a different database type.