Modify the CRConfig.xml file to create a Content Engine or Content Platform Engine JDBC connection with Crystal Server when Content Engine or Content Platform Engine is running on Oracle WebLogic Server.
To create a Content Engine or Content Platform Engine JDBC connection with Crystal Server when Content Engine or Content Platform Engine runs on Oracle WebLogic Server, modify the existing CRConfig.xml file.
XML element | Set to... |
---|---|
Classpath | Add the following JAR files to the class path:
When the Crystal Server and Content Engine or Content Platform Engine server are collocated, the Jace.jar and log4j.jar can be located under the Content Engine or Content Platform Engine deployed folder. When the Crystal Server and Content Engine or Content Platform Engine server are on separate servers, the Jace.jar and log4j.jar can be located under Content Engine or Content Platform Engine at ce_install_path/lib. Copy the JAR files locally to the Crystal Server. For example: C:/CE_jars. Then point the classpath to this location. The wlclient.jar can
be located in the following directory:
For
example:
|
JVMMaxHeap | Set the value to: 512000001 -Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
|
JVMMinHeap | Set the value to: 512000000 |
JDBCURL | Enter the JDBC URL used to connect to Content Engine or Content Platform Engine on Oracle WebLogic Server in the following format:
Where CE_server is
the name of your Content Engine or Content Platform Engine server, and port is
the port number used in the RemoteServerURL parameter
found in the ier_install_path/RecordsManager/WEB-INF/WcmAPIConfig.properties file. |
JDBCClassName | Set the value to: com.filenet.api.jdbc.Driver |
JDBCUserName | Enter the name of a user with the GCD Administrator role. |
GenericJDBCDriver | Replace the entire JDBC GenericJDBCDriver element with:
|