| Frequently Asked Questions (Deployment/Viewer/Engine) [message #59747] |
Mon, 18 July 2005 23:38 |
Eclipse User |
|
|
|
Greeting,
I compiled the recent Q & A in the BIRT newsgroup and divided them into
categories. You could take a look at the page, perhaps it could help you
get out of stuck :). More infomation could be found in the BIRT FAQ page.
Thanks to all the BIRT community members.
Regards,
Nina
------------------------------------------------------------ --
Deployment/Viewer/Engine issues
(Note: If you got confused about the answer, you could send E-mail
directly to the person who answered the relevant question.)
Q: What is necessary in order to deploy a report that contains a chart
into an app-server based runtime engine?
(Answered by whe@actuate.com ) Deploy a report with a chart to an
appServer is the same as deploy any other reports. Chart engine is fully
integrated in the BIRT report viewer. You can use the report viewer as the
start point for your webApp to integrate with BIRT. BIRT report viewer
itself is a webapp that is deployed to an embedded tomcat engine in BIRT
designer. You can find the BIRT viewer app under
plugin/org.eclipse.birt.report.viewer_1.0.0/birt folder, which contains
all required BIRT runtime components.
For more info on BIRT integration, please refer to the following link:
http://www.eclipse.org/birt/index.php?page=deploy/viewer-dep loy.html
The design of BIRT report viewer serves two purposes:
1. Preview the report design within the BIRT designer. At which the viewer
is deployed to an embedded tomcat engine.
2. Provide a starting point for people to develop/integrate with BIRT.
You can just copy and deploy the BIRT viewer to appServer, and view your
report through browser, or simply copy the BIRT viewer into your web
application. One thing I would like to point out is, if you have added a
BIRT extension, for example, you have added a new ODA data source plugin,
you also need to copy this plugin into
plugin/org.eclipse.birt.report.viewer_1.0.0/birt/WEB-INF/plu gin folder.
BIRT viewer uses the same plugin mechanism as Eclipse workbench does.
Q: Why I got an HTTP 500 error when previewing my report?
(Answered by jzhai@actuate.com ) Several issues that may cause 500 errors:
1) Java compiler is missing or not properly configured.
2) Using certain JDK versions lower than JDK1.4.2_08, such as JDK1.4.2_04.
3) Eclipse's workspace is on a remote file system.
4) Installing the new BIRT version without clear out the old one.
Q: Why importPackage does not work?
(Answered by swang@actuate.com ) Try to use
importPackage(Packages.java.util); instead of
importPackage(java.util);.
Q: How to program a Servlet to open a BIRT report to the browser?
(Answered by Jun Zhai) You can either refer to the BIRT engine online doc
or check the BIRT viewer's source code at org.eclipse.birt.report.viewer
plugin. All you need is the logic inside file
" /birt/WEB-INF/classes/org/eclipse/birt/report/viewer/aggrega tion/layout/EngineFragment.java ".
Q: Is it possible to access objects in the session context through
scripting?
(Answered by swang@actuate.com) The engine API has a function in the
IEngineTask interface:
public void addScriptableJavaObject(String jsName, Object obj);
This allows you to register an object (i.e., sesion context) and give it a
name (say, myContext), so that you can write myContext.foo() in your
scripting code.
Q: Why I got an Engine Exception when running the sample application
RunReport from the 'integrating BIRT' guide?
(Answered by swang@actuate.com and Bazinou) The problem is that you did
not set engine home directory correctly. Make sure you called
org.eclipse.birt.report.eninge.EngineConfig.setEngineHome(). The
"setEngineHome" must point at:
SDK: - eclipse/plugins/org.eclipse.birt.report.viewer_1.0.0/birt/WE B-INF,
or
Runtime: - birt-runtime-1_0/Report Engine
Q: How can I set the log level for the output of the viewer?
(Answered by swang@actuate.com and jzhai@actuate.com ) Please find out
setLogConfig method, which is defined for
org.eclipse.birt.report.engine.EngineConfig in Viewer code. Furthermore,
we will have a parameter defined in web.xml to specify the log level so
that you don't need to change it in your code.
The chart component's log should finally be directed to the engine's
logger and log info should be written into the engine log file, we already
cut off the link between the engine's root logger and default tomcat
logger.
|
|
|
Powered by
FUDForum. Page generated in 0.23699 seconds
Home