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 WebSphere® Application Server.
To create a Content Engine or Content Platform Engine JDBC connection with Crystal Server when Content Engine or Content Platform Engine runs on WebSphere Application Server, modify the existing CRConfig.xml file.
XML element | Set to... |
---|---|
JavaDir32 JavaDir64 |
Set to the installation path of the WebSphere Application Server or WebSphere Application Server Client JDK. For example: WebSphere Application Server C:/ProgramFiles/IBM/WebSphere/AppServer/java/bin Application Client for WebSphere Application Server: C:/ProgramFiles/IBM/WebSphere/AppClient/java/bin |
Classpath | Add the following JAR files to the class path:
When the Crystal Server and the 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 the 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. |
JVMMaxHeap | Set the correct JVMMaxHeap value for WebSphere Application
Server.
Set the Java properties for JNDI, as in the following examples:
Important: In a clustered Content
Engine or Content Platform Engine environment, the value of the Djava.naming.provider.url parameter might contain node:port# pairs. The node:port# pairs
might be found in the RemoteServerURL parameter
in the ier_install_path/RecordsManager/WEB-INF/WcmApiConfig.properties file. Remove the cemp: prefix and the trailing /cell/clusters/CECluster/FileNet/Engine when specifying
the parameter value. For example:
with the Djava.naming.provider.url parameter of:
|
JVMMinHeap | Set the value to: 512000000 |
JDBCURL | Enter the JDBC URL used to connect to Content Engine or Content Platform Engine on WebSphere Application
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. FPOS is the name of your file plan object store.Important: In a clustered Content Engine or Content Platform Engine environment, the value
of the JDBCURL tag might contain node:port# pairs. The node:port# pairs might be found in
the RemoteServerURL parameter in the ier_install_path/RecordsManager/WEB-INF/WcmApiConfig.properties file. Replace the cemp: prefix with jdbc:filenetp8, and add to the end ?objectstores-FPOS when specifying the tag value. For example:
with the JDBCURL tag of:
|
JDBCClassName | Set the value to: com.filenet.api.jdbc.Driver |
JDBCUserName | Set the value to the name of a user with the GCD Administrator role. |
GenericJDBCDriver | Replace the entire JDBC GenericJDBCDriver element with:
|