SAP Knowledge Base Article - Public

1199267 - Information on the CRConfig.xml file used for Crystal Reports

Symptom

  • Where can we find information on understanding the CRConfig.xml file used in Crystal Reports?
  • What are the options availables in the CRConfig.xml file?

Environment

  • SAP Crystal Reports 2016
  • SAP Crystal Reports 2020
  • SAP Crystal Reports 2025

Resolution

The CRConfig.xml file is installed by default in the following directory:

    \\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java

Below are all the parameters available for the crconfig.xml file:

General Settings

Tag Name

Description

<reportlocation>

Specifies the root directory used to locate report files when using the Java Reporting Component. Accepts relative or absolute paths.

Relative path example:
../reports/sample.rpt resolves to /WEB-INF/reports/sample.rpt when the JAR is in /WEB-INF/lib.

If this tag is absent, absolute paths are used. To use absolute paths, ensure CRConfig.xml does not contain a
<reportlocation> tag.

<timeout>

The inactivity interval (in minutes) before a report source is disposed. Default: 10 minutes. Set to 0 to disable.

The timer resets each time a report source request completes successfully. Active reports are never timed out.

 

ExternalFunctionLibraryClassNames

Tag Name

Description

<classname>

Fully qualified class name of a Java function library. Repeat this tag for each library you want to reference.

<keycode>

Key code used when running the Java Reporting Component.

 

DataDriverCommon

Tag Name

Description

<JavaDir>

Directory of the Java executable. Use this to target a specific JRE version.
Supports environment variables, e.g.
${JAVA_HOME}\bin.

<Classpath>

List of classpaths to required .jar files, including CRDBJavaServer.jar and all JDBC driver .jar files. Supports environment variables. Enclose paths that contain spaces in quotation marks.

<IORFileLocation>

Temporary directory for use by the JDBC driver. Must exist and be accessible by the system; otherwise the driver will fail.

<JavaServerTimeout>

Maximum time (in seconds) the Java server will process a request before shutting down. Default: 1800 seconds (30 minutes).

<JVMMaxHeap>

Maximum heap space the JVM can allocate for the Java server. Default: 64 MB. Increase for large data processing.

<JVMMinHeap>

Minimum heap space the JVM can allocate for the Java server. Default: 32 MB.

<NumberOfThreads>

Number of concurrent instances that can run. Default: 50.

 

JDBC

Tag Name

Description

<CacheRowSetSize>

Number of rows to cache in memory. Default: 100 rows.

<JDBCURL>

Default JDBC connection URL displayed in Crystal Reports when creating a new JDBC data connection. Format is driver-specific.

Oracle example:
jdbc:oracle:thin:@<hostname>:<port>:<sid>

  -
<hostname> — TCP/IP address or host name of the server
  -
<port> — TCP/IP port number
  -
<sid> — Oracle database ID

<JDBCClassName>

Default fully qualified JDBC driver class name displayed when creating a new JDBC data connection.

Oracle example:
oracle.jdbc.driver.OracleDriver

<JDBCUserName>

Default user ID displayed when creating a new JDBC data connection. Used by the JDBC driver to connect to the database.

<JNDIURL>

Default JNDI connection URL displayed in Crystal Reports when creating a new JNDI data connection. Format is driver-specific.

<JNDIConnectionFactory>

Name of the JNDI server connection factory.

  - WebLogic:
weblogic.jndi.WLInitialContextFactory
  - WebSphere:
com.ibm.websphere.naming.WsnInitialContextFactory

<JNDIInitContext>

Starting point for JNDI context lookup on the server.

  - WebLogic example:
/
  - WebSphere example:
cell/nodes/localhost/servers/server1/jdbc

<JNDIUserName>

Default user ID displayed when creating a new JNDI data connection.

 

GenericJDBCDriver — Default Section

Used when no matching configuration section exists for the target database server.

 

Tag Name

Description

<ServerType>

Keyword representing the database server type. Typically UNKNOWN for default settings.

<QuoteIdentifiedOnOff>

ON or OFF. When ON, quote characters are added to generated SQL statements.

<StoredProcType>

Type of stored procedure the database uses. Valid values: Standard, Oracle.

<LogonStyle>

Logon style to emulate when using a generic JDBC driver. Valid values: DB2, SQLServer, Oracle, MySQL, Standard.

 

GenericJDBCDriver — Sybase Section

Used when connecting specifically to a Sybase server.

 

Tag Name

Description

<ServerType>

Keyword representing the Sybase server type. Value: SYBASE.

<QuoteIdentifiedOnOff>

ON or OFF. When ON, quote characters are added to generated SQL statements for Sybase connections.

<DriverClassName>

JDBC driver class name for the Sybase database.

<StoredProcType>

Type of stored procedure the database uses. Valid values: Standard, Oracle.

<LogonStyle>

Logon style to emulate when using a generic JDBC driver. Valid values: DB2, SQLServer, Oracle, MySQL, Standard.

 

XML

Tag Name

Description

<CacheRowSetSize>

Number of rows to cache in memory. Default: 100 rows.

<PreReadNBytes>

Number of bytes to read from the XML document per logical read (equivalent to block read size). Minimum recommended: 4096. Setting too high affects memory usage. Default: 4096.

<XMLLocalURL>

Default connection URL for a local XML file, displayed in Crystal Reports when creating a new XML data connection.

<SchemaLocalURL>

Default connection URL for the XML schema file. (Note: definition was truncated in the source document.)

 

Keywords

This document provides information about the CRConfig.xml configuration file that is shipped with Crystal Reports XI. In particular, this document discusses the purpose of the CRConfig.xml file, when it is needed and the tag properties that are exposed by this configuration file. , 3775939 , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , How To

Product

SAP Crystal Reports 2016 ; SAP Crystal Reports 2020 ; SAP Crystal Reports 2025

Attachments

CR Parameter Reference.pdf