If Content Platform Engine and Rendition Engine use different databases,
you must install drivers for the Rendition Engine database
on the Content Platform Engine server.
Important: This task is only required if your Content Platform Engine and IBM®
FileNet® Rendition Engine use different databases.
Rendition Engine might be configured to
use a different database than the Content Platform Engine object store. For example, Rendition Engine might use Microsoft SQL Server and Content Platform Engine might use DB2®. In this case, you must configure Content Platform Engine with the corresponding
JDBC driver for the Rendition Engine database
to allow the Rendition Engine client
software that is running on the Content Platform Engine application server
to access the Rendition Engine database.
To install database drivers on JBoss Application Server:
- Obtain the JDBC drivers, depending on your database type.
- Microsoft SQL Server
- Find the version of Microsoft JDBC
Driver at Microsoft Support
that matches the version of the JDK on JBoss Application Server.
- Oracle
- Access the Oracle JDBC Driver Downloads website and find
the JDBC driver file that matches the version of the JDK on JBoss Application Server.
- Place the file JDBC driver file in the CLASSPATH:
- Standard deployment
- Copy the JDBC driver file to the jboss_install_dir/server/server1/lib directory.
- Cluster deployment
- Copy the JDBC driver file to the jboss_install_dir/all/server1/lib directory.
- If you are deploying multiple instances of Content Platform Engine on the same server,
do the following for each additional instance:
- Copy the configuration file set that you created and
modified from the jboss_install_dir/server/server1 directory
to a new directory. Use a separate directory for each instance. For example, copy the jboss_install_dir/server/server1 directory
to jboss_install_dir/server/server2 and jboss_install_dir/server/server3.
- Assign unique port numbers to each instance. Refer to
your JBoss Application Server documentation
for details.