Introduction

Below are some notes provided by customers on using ReportMill with WebLogic.

WebLogic Policy

1) In weblogic.policy, add the following line to where ReportMill.jar is located:
 
        permission java.io.FilePermission "${/}REPORT_MILL_JAR_LOCATION${/}-",
"read,write,delete,execute";

Or for quick, hassle-free development setup (although not recommended for production), add the following line to the "grant {" section:
 
        permission java.security.AllPermission;
2) Modify the startup script for Weblogic 5.1 to add the following:
-Xbootclasspath/a:$MY_3RD_PARTY_LIB_PATH/pja.jar:$MY_3RD_PARTY_LIB_PATH/
rtgraphics.jar:$MY_3RD_PARTY_LIB_PATH/ReportMill.jar
-Dawt.toolkit=com.eteks.awt.PJAToolkit
-Djava.awt.graphicsenv=com.eteks.java2d.PJAGraphicsEnvironment -Djava.awt.fonts=$JAVA_HOME/jre/lib/fonts -Djava2d.font.userPlatformFont=false
 
    This will setup ReportMill.jar to be part of bootclasspath, which is necessary for headless document generation.  Notice that the PJA libraries are also setup here.
 
3) Add to $WEBLOGIC_CLASSPATH the ReportMill.jar

Configuring Responses

Another customer reported a problem in configuring HTML responses for HTML reports, documented at BEA's website. The solution was to call resetBuffer on the response:

response.setContentLength(imgBytes.length);
response.resetBuffer();
response.getOutputStream().write(imgBytes);
response.getOutputStream().close();