Deploying to JBoss 3.2

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:

• JBoss 3.2 is installed in the /opt/jboss-3.2.7 directory.
• The JReport Enterprise Server WAR file jreport.war is located in the /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 JBoss 3.2:

1. Ensure that JBoss is shut down by running the script /opt/jboss-3.2.7/bin/shutdown.sh -S.
2. Copy the Web Application Archive file jreport.war to /opt/jboss-3.2.7/server/default/deploy.
3. Start JBoss by running the run.sh script.
4. Access JReport Enterprise Server using the following URLs:

   http://localhost:8080/jreport/jrserver
http://localhost:8080/jreport/admin/index.jsp
http://localhost:8080/jreport/jinfonet/index.jsp

Troubleshooting

If you run into problems when using JReport Enterprise Server in JBoss, send the log files of JReport Enterprise Server to support@jinfonet.com. The following procedure illustrates how to generate the log files:

1. Modify the batch file run.sh in /opt/jboss-3.2.7/bin.

   In the file run.sh, add -Dlogall=true after the reporthome definition:

   "$JAVA" $JAVA_OPTS \ -classpath "$JBOSS_CLASSPATH" \ -Dreporthome=/opt/JReport/Server \ -Dlogall=true \ org.jboss.Main "$@"

2. After editing run.sh, start JBoss using the modified batch file.
3. After reproducing the problem, send support@jinfonet.com the log files in reporthome/logs.

   The JBoss log files may also help to identify the problem. The most useful one is /opt/jboss-3.2.7/server/default/log/server.log.