Setting Java Properties¶

Edit the WebLogic startup script for your platform to include the settings described in the following tables. Substitute the location of your JasperReports Server license file where necessary:

WebLogic Startup Settings on Windows
Filename	`<wl-domain>\bin\startWebLogic.cmd`
Settings	`set JAVA_OPTIONS=%JAVA_OPTIONS%` `-Djs.license.directory=C:\<js-install>\` `-Dfile.encoding=UTF-8` `-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0` `-Dlog4j.configurationFile=WEB-INF/log4j2.properties` `-Xms2048m` `-Xmx4096m` `-Xss2m`
For Oracle (optional)	`set JAVA_OPTIONS=%JAVA_OPTIONS% -Doracle.jdbc.defaultNChar=true`

Note

Setting the Oracle localization option, defaultNChar, can substantially impact the performance of JDBC queries. If you don't need to support UTF-8 for your Oracle database, you can omit this setting.

WebLogic Startup Settings on Linux
Filename	`<wl-domain>/bin/startWebLogic.sh`
Settings	`export JAVA_OPTIONS="$JAVA_OPTIONS` `-Djs.license.directory=/home/<user>/weblogic/jasperlicense/` `-Dfile.encoding=UTF-8` `-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0` `-Dlog4j.configurationFile=WEB-INF/log4j2.properties` `-Xms2048m` `-Xmx4096m` `-Xss2m"`
For Oracle (optional)	`export JAVA_OPTIONS="$JAVA_OPTIONS -Doracle.jdbc.defaultNChar=true"`

Note

Setting the Oracle localization option, defaultNChar, can substantially impact the performance of JDBC queries. If you don't need to support UTF-8 for your Oracle database, you can omit this setting.