There are a few caveats to take into consideration. If your
BIRT report hits a database, the appropriate drivers will need to be included in the
ReportEngine\plugins folders. For example, if the report uses JDBC to connect,
the JDBC drivers will need to be installed under the ReportEngine\plugins\org.
eclipse.birt.report.data.oda.jdbc_
folder. Also, you will need to
copy the iText.jar file (as indicated in the BIRT Runtime installation instructions)
to the appropriate plug-ins directory.
From this exercise, I learned a few interesting things. I was unaware that Java classes
could be invoked from the command line. For example, if I set an environment
variable called BIRTClassPath like the following:
SET BIRTCLASSPATH=%BIRT_HOME%\ReportEngine\lib\commons-cli-1.0.jar;%BIRT_
HOME%\ReportEngine\lib\commons-codec-1.3.jar;%BIRT_HOME%\ReportEngine\
lib\com.ibm.icu_3.4.4.1.jar;%BIRT_HOME%\ReportEngine\lib\coreapi.
jar;%BIRT_HOME%\ReportEngine\lib\dteapi.jar;%BIRT_HOME%\ReportEngine\
lib\engineapi.jar;%BIRT_HOME%\ReportEngine\lib\js.jar;%BIRT_HOME%\
ReportEngine\lib\modelapi.jar;%BIRT_HOME%\ReportEngine\flute.jar;%BIRT_
HOME%\ReportEngine\lib\sac.jar;
I can run the following command from the DOS prompt and get the parameters that
the ReportEngine class is expecting:
java -cp "%BIRTCLASSPATH%" org.
Pages:
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212