The example directory paths listed below are based on Solaris or Linux (referred to as UNIX). The instructions are applicable to both UNIX and Windows installations; however, the format of the paths for Windows would use the Windows format, i.e. C:\JReport\Server instead of /opt/JReport/Server.
It is assumed that:
/opt/jakarta-tomcat-4.1 directory./opt/JReport/Server/bin/distribute directory. To create the WAR file refer to the instructions in Building a WAR/EAR file to include a self-contained JReport Enterprise Server.To deploy JReport Enterprise Server to Tomcat 4.1:
startup.sh script.http://localhost:8080/index.jsp. If you are accessing the server remotely, replace localhost with the appropriate host name for your server.http://localhost:8080/manager/html. You will be challenged for user name and password to login. By default Tomcat does not have a manager and administrator login defined. If you have not already done so, you must edit the /opt/jakarta-tomcat-4.1/conf/tomcat-users.xml file to add a user with admin and manager roles. The line should look something like this <user username="admin" password="admin" roles="admin,manager"/>. You can now use your new user to login into the manager's web page.http://localhost:8080/jreport/jrserver
http://localhost:8080/jreport/admin/index.jsp
http://localhost:8080/jreport/jinfonet/index.jsp
You can also access JReport by selecting the /jreport link on the Tomcat Manager web page.
If you run into problems when using JReport Enterprise Server in Tomcat, send the log files of JReport Enterprise Server to support@jinfonet.com. The following procedure illustrates how to generate the log files:
/opt/jakarta-tomcat-4.1/bin.
In the file catalina.sh, add -Dlogall=true after the reporthome definition:
|
http://localhost:8080/jreport/admin/info.jsp?cmd=info.reporthome/logs.
The Tomcat log files may also help to identify the problem. The most useful one is /opt/jakarta-tomcat-4.1/logs/catalina.out.