Modify the CRConfig.xml file to create a Content Platform Engine JDBC connection with Crystal Reports when Content Engine is running on JBoss Application Server.
To create a Content Platform Engine JDBC connection with Crystal Reports server when Content Platform Engine runs on a JBoss Application Server, modify the existing CRConfig.xml file.
XML element | Set to... |
---|---|
JavaDir | Set to the installation path of the JDK. Example:
|
Classpath | Restriction: If you are using JBoss Application Server 4.2.3 or later, Jace.jar and log4j.jar must
be placed in the beginning of the classpath tag in the CRConfig.xml file.
Add the following JAR files to the class path:
Restriction: For JBoss Application Server 5.x only (if the client
does not already have JBoss 5.x installed):
Add the following Crystal Reports JAR files with the full path to the class path:
These JAR files are typically located in: C:\Program Files\Business Objects\Common\4.0\java\lib or C:\Program Files\Business Objects\Common\4.0\java\lib\external. |
JVMMaxHeap | Set the value to: 512000001 -Djava.naming.factory.initial=
org.jnp.interfaces.NamingContextFactory
|
JVMMinHeap | Set the value to 512000000. |
JDBCURL | Enter the JDBC URL used to connect to Content Platform Engine on JBoss Application Server in the following format:
Where CE_server is
the name of your 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. |