Programming using the BIRT Reporting APIs : Generating reports from an application : Setting up the report engine : Configuring the report engine
 
Configuring the report engine
Optionally, set other configuration properties using methods on an EngineConfig object. Table 12-3 describes these properties and how to set them using EngineConfig methods. The EngineConfig class also provides getter methods to access these properties.
Table 12-3 EngineConfig properties
Property type
Setting the property
Configuring an emitter
To set the properties for the required report output format, call setEmitterConfiguration( ) with arguments providing the format and a IRenderOption object for that format.
Logging
To set the logging file location and level, call setLogConfig( ). To refine the logging file name and properties, use the other setLogXXX( ) methods.
OSGi (Open Services Gateway Initiative) configuration
To set specific OSGi startup parameters, call setOSGiArguments( ) or setOSGiConfig( ).
Platform context
To indicate whether the application and BIRT home are in a stand-alone environment or packaged as a web archive (.war) file, create an implementation of the IPlatformContext interface. Then, call setPlatformContext( ).
Resource files
To set the location from which the reporting application accesses resource files such as
Resource files
libraries and properties files containing localized strings, call setResourcePath( ). To change the algorithm for locating these resources, call setResourceLocator( ).
Scripting configuration
To provide external values to scripting methods, call setProperty( ). To provide additional Java resources to scripting methods, call getAppContext( ) and add the object to the application context object.
Status handling
To provide a custom status handler, create an implementation of the IStatusHandler interface. Then, call setStatusHandler( ).
Temporary file location
To set up a custom location for temporary files, call setTempDir( ).