Using a customized implementation of jet.server.api.http.CustomizedServerEnv

You can implement the interface and add your class to the generated WAR/EAR file, then use the <env-entry></env-entry> tags to specify your implemented class in the target "web.xml" in the makewar.xml file or in ejb-jar.xml.

The following is an example of specifying a customized implementation of CustomizedServerEnv in the target web.xml in the makewar.xml file or in ejb-jar.xml using the <env-entry></env-entry> tags. Here the customized implementation of CustomizedServerEnv is named my.JReportServerEnv.

<!-- JReport Server calls my.JReportServerEnv to obtain reporthome and server properties.-->
<env-entry>
    <env-entry-name>jreport.servenv</env-entry-name> <!-- must be jreport.servenv-->
    <env-entry-value>my.JReportServerEnv</env-entry-value> <!-- your class name --> 
    <env-entry-type>java.lang.String</env-entry-type>
</env-entry>

Notes:

JReport Server will retrieve the reporthome and properties from your implemented class when the WAR/EAR file has been deployed.
The properties returned from getServerProperties() can be the properties listed in server.properties file in the directory <install_root>\bin, JVM System properties, or self-defined ones.