Modify the CRConfig.xml file to create a Content Engine JDBC connection with Crystal Reports running on WebSphere® Application Server.
To create a Content Engine JDBC connection with Crystal Reports on WebSphere Application Server, you must modify the existing CRConfig.xml file.
XML element | Set to... |
---|---|
JavaDir | Set to the install path of the WebSphere Application Server or WebSphere Application Server Client JDK. For example: WebSphere Application ServerC:\ProgramFiles\IBM\WebSphere\AppServer\java\bin WebSphere Application Server Client: C:\ProgramFiles\IBM\WebSphere\AppClient\java\bin |
Classpath | Add the following JAR files to the classpath:
You copied these files to the Crystal Reports server as part of Installing and configuring the Crystal Reports server.
These JAR files are typically located in: C:\Program Files\Business Objects\common\4.0\java\lib |
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 environment, the value of the Djava.naming.provider.url parameter
may contain several node:port# pairs.
These node:port# pairs may be
found in the RemoteServerURL parameter in the RM_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:
RemoteServerUrl = cemp:corbaloc::server_node1:port#,:server_node2:port#/cell/ clusters/CECluster/FileNet/Engine with the Djava.naming.provider.url parameter of: -Djava.naming.provider.url=corbaloc::server_node1:port#,: server_node2:port# |
JVMMinHeap | Set the value to: 512000000 |
JDBCURL | Enter the JDBC URL used to connect to Content Engine on WebSphere Application
Server in the following format:
jdbc:filenetp8:iiop://CE_server:port#/ FileNet/Engine?objectstores=FPOSWhere CE_server is the name of your Content Engine server, and port# is the port number used in the RemoteServerURL parameter found in the RM_install_path/RecordsManager/WEB-INF/WcmApiConfig.properties file. FPOS is the name of your file plan object store. Important: In
a clustered Content Engine environment, the value
of the JDBCURL tag may contain several node:port# pairs.
These node:port# pairs may be found in the RemoteServerURL parameter
in the RM_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:
RemoteServerUrl = cemp:corbaloc::server_node1:port#,:server_node2:port#/cell/ clusters/CECluster/FileNet/Engine with the JDBCURL tag of: <JDBCURL>jdbc:filenetp8:corbaloc::server_node1:port#,: server_node2:port#/cell/ clusters/CECluster/FileNet/Engine?objectstores=FPOS</JDBCURL> |
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. |
DatabaseStructure | Set the value to: tables |