Using JBoss 5.1, you can clone your JasperReports Server install by copying an existing JRS WAR file to a new JBoss instance. While this method isn’t strictly supported, some users have experienced good results.
The question is this: will the same method work when JasperReports Server 5.1 is hosted by JBoss AS7/EAP6?
1 Answer:
The short answer is no.
This procedure does not work for JBoss AS7/EAP6 because, in addition to the JasperReports Server web application and the repository contents, Jaspersoft’s buildomatic creates a new module (jaspersoft.org.apache.batik) under the JBoss modules directory. If this module is not present, deployment will fail.
(Please note that JBoss AS7/EAP6 is not supported with JasperReports Server versions earlier than 5.1.)
in addition to copying the module <jboss-install>/modules/jaspersoft/org/apache/batik to the target server, you should also merge the configuration file:
4. Merge the source <JBoss-install-dir>/standalone/configuration/standalone.xml descriptor with the corresponding descriptor on the target host. It is not advised to overwrite the existing descriptor if the target host is not a freshly installed JBoss instance as you may lose any special settings that are present in the existing target descriptor.
The new lines that you want to merge are under the <profile><subsystem xmlns="urn:jboss:domain:logging:1.1"> section and look like:
<!-- 2013-03-20 thorick JasperSoft
silence innocuous deployment warnings
per
https://community.jboss.org/thread/198349?_sscc=t
-->
<logger category="org.jboss.as.server.deployment">
<level name="ERROR"/>
</logger>
<logger category="org.jboss.as.connector.deployers.jdbc">
<level name="ERROR"/>
</logger>
Thanks for the further info!