BackPrevious Page Next PageNext

Deploying 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:\JReport\Server instead of /opt/JReport/Server.

The following takes JBoss EAP 7.0 as an example.

It is assumed that:

To deploy JReport Server to JBoss EAP 7.0:

  1. 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:

    Add -Djbossas7=true

  2. After file jreport.war is generated, extract it with your zip tool.
  3. Create a file named jboss-deployment-structure.xml in the jreport.war/META-INF directory. The file should contain the following contents:

    <?xml version="1.0" encoding="UTF-8"?>

    <jboss-deployment-structure>

    <deployment>

    <exclusions>

    <module name="org.apache.log4j" />

    </exclusions>

     

    <dependencies>

    <system>

    <paths>

    <path name="com/sun/org/apache/xml/internal/security/utils"/>

    </paths>

    </system>

    </dependencies>

    </deployment>

    </jboss-deployment-structure>

  4. Compress the extracted jreport.war back to a single file.
  5. Start JBoss by running the standalone.sh script if it is not started.
  6. 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.

    JBoss Management Console

  7. Access JReport Server using the following URLs:

    http://localhost:8080/jreport/jrserver
    http://localhost:8080/jreport/admin/index.jsp
    http://localhost:8080/jreport/jinfonet/index.jsp

Troubleshooting

If you run into problems when using JReport Server in JBoss, send the log files of JReport Server to support@jinfonet.com. The following procedure illustrates how to generate the log files:

  1. Modify the file standalone.conf in /opt/JBoss EAP 7.0/bin.

    In the file standalone.conf, add -Dlogall=true like this:

    Add -Dlogall=true

  2. After editing standalone.conf, start JBoss using the modified file.
  3. 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.0/standalone/log/server.log.

BackPrevious Page Next PageNext