This topic describes how you can deploy Logi Report Server to WildFly 26.0.0.
We use paths based on UNIX path name protocol in our example. The instruction applies to both UNIX and Windows installation. However, the path formats differ. For Windows it is in this format
C:\LogiReport\Server instead of
- You installed WildFly 26.0.0 in the
- The Logi Report Server WAR file jreport.war is in the
/opt/LogiReport/Server/bin/distributedirectory. To create the WAR file, see 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 in the jreport.war/META-INFO folder with the contents:
<?xml version="1.0" encoding="UTF-8"?>
To deploy Logi Report Server to WildFly 26.0.0:
- Start WildFly by running the standalone.sh script in
- By default, WildFly is distributed with security enabled for the management interface. It means that before you access the Administration Console you need to add a new user. You can achieve this using the
add-user.shscript in the bin folder. Set the username and password for the new user.
- Sign in to the WildFly Administration Console with the specified username and password using the URL
- In the Deployments tab, select Add.
- In the Create Deployment dialog box, browse to select the jreport.war file.
- Select Next.
- In the step 2 of the Create Deployment dialog box, select Enable.
- Select Save.
- Upon the successful deployment of the Logi Report Server WAR file jreport.war, access Logi Report Server using the following URL:
If you run into problems when using Logi Report Server in WildFly, you may have to send the log files of Logi Report Server to Customer Service. The following procedure illustrates how to generate the log files:
- Modify the standalone.sh file 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 standalone.sh.
- After reproducing the problem, send Customer Service the log files in
The WildFly log files may also help identify the problem. The most useful one is /opt/wildfly/server/default/log/server.log.
If you encounter the problem that WildFly cannot locate jrenv.jar when you are deploying a WAR/EAR to WildFly, add -Djbossas7=true in makewar.bat/sh.