Deploying to WildFly 8.2.0.Final

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, that is, C:\JReport\Server instead of /opt/JReport/Server.

It is assumed that:

• WildFly 8.2.0.Final is installed in the /opt/wildfly directory.
• The JReport 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 Server.

To deploy JReport Server to WildFly 8.2.0.Final:

1. Start WildFly 8.2.0.Final by running the standalone.sh script in /opt/wildfly/bin.
2. By default WildFly 8.2.0.Final is now distributed with security enabled for the management interfaces, this means that before you connect using the administration console you need to add a new user, this can be achieved by using the add-user.sh script in the bin folder. You will then be prompted to set the user name and password for the new user.
3. Log onto the WildFly 8.2.0.Final Administration Console with the specified user name and password using the URL http://localhost:9990/console.
4. In the Deployments tab, click Add. In the Create Deployment dialog, browse to select the file jreport.war. Then click Next.
5. In the step 2 of the Create Deployment dialog, check the Enable option and then click Save.
6. Upon the successful deployment of the JReport Server WAR file jreport.war, access JReport 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 Server in WildFly, send the log files of JReport Server to support@jinfonet.com. The following procedure illustrates how to generate the log files:

1. Modify the file standalone.sh in /opt/wildfly/bin.

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

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

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

   The WildFly log files may also help to identify the problem. The most useful one is /opt/wildfly/server/default/log/server.log.