Deploying Server to WildFly 20.0.1
This topic describes how you can deploy Logi Report Server to WildFly.
In the example we use directory paths based on Unix. The instructions are applicable to both Unix and Windows installations. However, the format of the paths for Windows should use the Windows format, that is,
C:\LogiReport\Server instead of
- You installed WildFly 20.0.1 in the
- The Logi Report Server WAR file jreport.war is in the
/opt/LogiReport/Server/bin/distributedirectory. To create the WAR file, refer to the instructions in Building a WAR/EAR File to Include a Self-contained Logi Report Server.
Before creating the WAR, you need to change JRPatternLayout to PatternLayout all over the LogConfig.properties file in
/opt/LogiReport/Server/bin. After you generate jreport.war, 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 Report Server to WildFly 20.0.1:
- Start WildFly 20.0.1 by running the standalone.sh script in
- By default, WildFly 20.0.1 is distributed with security enabled for the management interfaces. It means that before you connect using the administration console you need to add a new user. You can achieve this using the
add-user.shscript in the bin folder. You will then need to set the user name and password for the new user.
- Log onto the WildFly 20.0.1 Administration Console with the specified user name and password using the URL
- In the Deployments tab, select Add.
- In the Create Deployment dialog box, browse to select the file jreport.war.
- Select Next.
- In the step 2 of the Create Deployment dialog box, select the Enable option and then select Save.
- Upon the successful deployment of the Logi Report Server WAR file jreport.war, access Logi Report Server using the following URLs:
If you run into problems when using Logi Report Server in WildFly, send the log files of Logi Report Server to email@example.com. The following procedure illustrates how to generate the log files:
- Modify the file standalone.sh in
/opt/wildfly/bin, by adding -Dlogall=true after the reporthome definition:
"$JAVA" $JAVA_OPTS \ -classpath "$WILDFLY_CLASSPATH" -Dreporthome=/opt/LogiReport/Server \ -Dlogall=true \ org.wildfly.Main "$@"
- Start WildFly using the modified file standalone.sh.
- 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.
If you encounter the problem that WildFly 20.0.1 cannot locate jrenv.jar when building a WAR/EAR to deploy to WildFly 20.0.1, add -Djbossas7=true in makewar.bat/sh.