Deploying to JBoss EAP 7.2
This topic introduces how to deploy Logi JReport Server to JBoss EAP. 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 /opt/JReport/Server
.
The following takes JBoss EAP 7.2 as an example.
It is assumed that:
- JBoss EAP 7.2 is installed in the
/opt/JBoss EAP 7.2
directory. - The Logi 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 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"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<system>
<paths>
<path name="org/w3c/dom/css"/>
</paths>
</system>
</dependencies>
</deployment>
</jboss-deployment-structure>
To deploy Logi JReport Server to JBoss EAP 7.2:
- To avoid the issue that JBoss EAP 7 cannot locate jrenv.jar, when building 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 if it is not started.
- Add a management user to JBoss EAP 7 by running the add-user.sh script. Then you need to access the JBoss Management Console to deploy jreport.war and enable it.
- Access Logi JReport Server using the following URLs:
http://localhost:8080/jreport/jrserver
http://localhost:8080/jreport/jinfonet/index.jsp
Troubleshooting
If you run into problems when using Logi JReport Server in JBoss, send the log files of Logi JReport Server to support@jinfonet.com. The following procedure illustrates how to generate the log files:
- Modify the file standalone.conf in
/opt/JBoss EAP 7.2/bin
.In the file standalone.conf, add
-Dlogall=true
like this: - After editing standalone.conf, start JBoss using the modified file.
- After reproducing the problem, send support@jinfonet.com the log files in
reporthome/logs
.The JBoss log files may also help to identify the problem. The most useful one is /opt/jboss-eap-7.2/standalone/log/server.log.