Before you can deploy JReport Portlet to any portal server, your JReport Server should have been deployed to an application server. You can refer to Deploying JReport Server to a Java application server for details about the deploying procedure. However, the JReport Server WAR file jreport.war used in the deployment should be packaged using the following command in this case (here it is assumed JReport Server is installed to C:\JReport\Server
):
C:\JReport\Server\bin\makewar buildWar4WS
Also, the reports you want to run in JReport Portlet should also be published to the JReport Webservice Server, in advance, so that they can be loaded to the corresponding folder in JReport Portlet automatically.
Assume that:
<server_install_root>\Demo\PortletReports
, to C:\PortalDemo
.C:\PortalDemo\font
and C:\PortalDemo\style
. These files can be found in PR_Resources.zip which locates in <server_install_root>\Demo\PortletReports
.Note: If you want to use the demo reports JReport provides in JReport Portlet, before deploying jreport.war to the web server, you need to add mysql-connector-java-5.x-bin.jar into \WEB-INF\lib, this is because the JReport demo portlet reports are based on MySQL database. You can get the database driver from PR_Resources.zip which is available in <server_install_root>\
Demo\PortletReports
.
To publish the demo reports to the JReport Webservice Server:
http://<hostname>:<webserver_port>/jreport
to access the JReport Webservice Server.C:\PortalDemo
where the portlet reports are saved.C:\PortalDemo\font
.C:\PortalDemo\style
.After the portlet reports are published to the My Reports/Public Reports folder in the JReport Webservice Server, they will also be automatically loaded to the My Portlet Reports/Public Portlet Reports folder in JReport Portlet.
Reference: You can refer to Publishing resources for more detailed instruction about the publishing steps.