Deploying to Jboss-as-7.1.1.Final or JBoss EAP 7.0
This topic introduces how to deploy Logi JReport Server Guide v15 Server to Jboss-as-7.1.1.Final or JBoss EAP 7.0. 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:\Logi JReport\Server instead of
The following takes JBoss EAP 7.0 as an example.
It is assumed that:
- JBoss EAP 7.0 is installed in the
/opt/JBoss EAP 7.0directory.
- The Logi JReport Server WAR file Logi JReport.war is located in the
/opt/Logi 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
To deploy Logi JReport Server to JBoss EAP 7.0:
- 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:
- After file Logi JReport.war is generated, extract it with your zip tool.
Create a file named jboss-deployment-structure.xml in the Logi JReport.war/META-INF directory. The file should contain the following contents:
<?xml version="1.0" encoding="UTF-8"?>
<module name="org.apache.log4j" />
- Compress the extracted Logi JReport.war back to a single file.
- 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 Logi JReport.war and enable it.
- Access Logi JReport Server using the following URLs:
If you run into problems when using Logi JReport Server in JBoss, send the log files of Logi JReport Server to [email protected]. The following procedure illustrates how to generate the log files:
- Modify the file standalone.conf in
/opt/JBoss EAP 7.0/bin.
In the file standalone.conf, add
- After editing standalone.conf, start JBoss using the modified file.
- After reproducing the problem, send [email protected] the log files in
The JBoss log files may also help to identify the problem. The most useful one is