This topic describes how you can deploy Logi Report Server to JBoss EAP 7.4.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 JBoss EAP 7.4.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:
<?xml version="1.0" encoding="UTF-8"?>
To deploy Logi Report Server to JBoss EAP 7.4.0:
- To avoid the problem that JBoss EAP 7 cannot locate jrenv.jar, when you build a WAR/EAR to deploy to JBoss EAP 7, add -Djbossas7=true in makewar.bat/sh like this:
- Start JBoss by running the standalone.sh script.
- Add a management user to JBoss EAP 7 by running the add-user.sh script.
- Access the JBoss Management Console to deploy jreport.war and enable it.
- Access Logi Report Server using the following URLs:
If you run into problems when using Logi Report Server in JBoss, 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.conf file in
/opt/JBossEAP/binto add -Dlogall=true.
- Start JBoss using the modified file standalone.conf.
- After you reproduce the problem, send Customer Service the log files in
The JBoss log files may also help to identify the problem. The most useful one is /opt/jbosseap/standalone/log/server.log.