Deploying to WildFly 17.0.1.Final
This topic introduces how to deploy Logi JReport Server to WildFly. The example directory paths listed below are based on 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
It is assumed that:
- WildFly 17.0.1.Final is installed in the
- The Logi JReport Server WAR file jreport.war is located in the
/opt/JReport/Server/bin/distributedirectory. To create the WAR file refer to the instructions in Building a WAR/EAR File to Include a Self-contained Logi JReport Server.
Note: Before creating the WAR, you need to change JRPatternLayout to PatternLayout all over the LogConfig.properties file in
/opt/JReport/Server/bin. After jreport.war is generated, create a file named jboss-deployment-structure.xml as follows in the jreport.war/META-INFO folder:
<?xml version="1.0" encoding="UTF-8"?>
To deploy Logi JReport Server to WildFly 17.0.1.Final:
- Start WildFly 17.0.1.Final by running the standalone.sh script in
- By default WildFly 17.0.1.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 using the
add-user.shscript in the bin folder. You will then be prompted to set the user name and password for the new user.
- Log onto the WildFly 17.0.1.Final Administration Console with the specified user name and password using the URL
- In the Deployments tab, select Add. In the Create Deployment dialog, browse to select the file jreport.war. Then select Next.
- In the step 2 of the Create Deployment dialog, check the Enable option and then select Save.
- Upon the successful deployment of the Logi JReport Server WAR file jreport.war, access Logi JReport Server using the following URLs:
If you run into problems when using Logi JReport Server in WildFly, send the log files of Logi JReport Server to email@example.com. The following procedure illustrates how to generate the log files:
- Modify the file standalone.sh in
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 "$@"
- After editing standalone.sh, start WildFly using the modified file.
- After reproducing the problem, send firstname.lastname@example.org the log files in
The WildFly log files may also help to identify the problem. The most useful one is /opt/wildfly/server/default/log/server.log.
Note: If you encounter the issue that WildFly 17.0.1.Final cannot locate jrenv.jar when building a WAR/EAR to deploy to WildFly 17.0.1.Final, add -Djbossas7=true in makewar.bat/sh.