IBM Enterprise Records, Version 5.1.2   

Editing the CRConfig.xml file on WebSphere Application Server

Modify the CRConfig.xml file to create a Content Engine or Content Platform Engine JDBC connection with Crystal Reports when Content Engine or Content Platform Engine is running on WebSphere® Application Server.

About this task

To create a Content Engine or Content Platform Engine JDBC connection with Crystal Reports server when Content Engine or Content Platform Engine runs on WebSphere Application Server, you must modify the existing CRConfig.xml file.

Procedure

To create a Content Engine or Content Platform Engine JDBC connection with Crystal Reports server:

Update the XML element content shown in the following table:
Table 1. XML elements when Content Engine or Content Platform Engine runs on WebSphere Application Server
XML element Set to...
JavaDir

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:

  • Jace.jar
  • log4j.jar
  • log4j-1.2.13.jar on WebSphere 6.x or earlier

Add the following Crystal Reports JAR files with the full path to the class path:

  • cecore.jar
  • celib.jar
  • ebus405.jar
  • corbaidl.jar
  • freessl201.jar
  • asn1.jar
  • certj.jar
  • jsafe.jar
  • sslj.jar

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 correct JVMMaxHeap value for WebSphere Application Server.
  • The value in this string must be set higher than the value of the JVMMinHeap element.
  • You must type the Java™ properties as one line of code within the JVMMaxHeap element. The line breaks shown in the example are included only for readability.

Set the Java properties for JNDI, as in the following examples:

Crystal Reports and Content Engine or Content Platform Engine are collocated
Set the Java properties (for all WebSphere Application Server versions):
<JVMMaxHeap>512000001
-Djava.ext.dirs="C:\Program
Files\IBM\WebSphere\AppServer\java\jre\lib\ext;
C:\Program Files\IBM\WebSphere\AppServer\lib;
C:\Program Files\IBM\WebSphere\AppServer\plugins"
-Djava.naming.factory.initial=
com.ibm.websphere.naming.WsnInitialContextFactory
-Djava.naming.provider.url=iiop://CE_server:port#
-Dcom.ibm.CORBA.loginSource=none
-Dcom.ibm.CORBA.ConfigURL="file:C:\Program
Files\IBM\WebSphere\AppServer\
profiles\default\properties\sas.client.props"</JVMMaxHeap>
Crystal Reports and Content Engine or Content Platform Engine are on separate servers
Set the Java properties for JNDI to have paths pointing to the WebSphere Application Server Client 6.1.x or 7.0.x folders:
<JVMMaxHeap>512000001
-Djava.ext.dirs="C:\Program
Files\IBM\WebSphere\AppClient\java\jre\lib\ext;
C:\Program Files\IBM\WebSphere\AppClient\lib;
C:\Program Files\IBM\WebSphere\AppClient\plugins"
-Djava.naming.factory.initial=
com.ibm.websphere.naming.WsnInitialContextFactory
-Djava.naming.provider.url=iiop://CE_server:port#
-Dcom.ibm.CORBA.loginSource=none
-Dcom.ibm.CORBA.ConfigURL=
"file:C:\Program Files\IBM\WebSphere\
AppClient\properties\sas.client.props"</JVMMaxHeap>
Tip: WebSphere Application Server Client must be installed on the Crystal Report server.
Tip: The CE_server:port # is typically the port that specified in the RemoteServerURL parameter in ier_install_path/RecordsManager/WEB-INF/WcmApiConfig.properties file.
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:
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 or Content Platform Engine on WebSphere Application Server in the following format:
jdbc:filenetp8:iiop://CE_server:port#/
FileNet/Engine?objectstores=FPOS
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:
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.


Feedback

Last updated: November 2013
frmic129a.htm

© Copyright IBM Corporation 2013