Verified on JBoss 5.1.0 GA through JBoss AS 7.1.1 and JBoss EAP 7.1. Verified on Wildfly 8.1.0 through Wildfly 11.0.0
Refer to the general notes for installing KonaKart on all Application Servers .
For JBoss and Wildfly we recommend that you deploy KonaKart as an exploded EAR file, or exploded WAR files so that you can guarantee the full path names of the various configuration files. This is useful so that you can define these full path names and subsequently edit these files from within the comfort of the KonaKart Admin Application.
Use the make_ear ANT target as follows: "make_ear -Djboss=true" or "make_ear -Dwildfly=true" to produce your EAR for JBoss and Wildfly respectively.
For JBoss EAP 7.1 use the additional EAP71 flag : "make_ear -Djboss=true -DvEAP71=true".
The JAXWS interfaces are disabled under JBoss and Wildfly.
The KonaKart applications can be deployed in the 'server configuration' directory of your choice. In this example we will use the 'default' configuration. In this example we also assume a Windows installation in the C:\jboss-4.2.2.GA directory.
Here we follow the procedure for the 3 WAR installation (but for the exploded EAR procedure follow an almost identical path). Create three new directories under C:\jboss-4.2.2.GA\server\default\deploy :
konakart.war
konakartadmin.war
birtviewer.war
Expand konakart.war into the konakart.war directory and do the same for konakartadmin and birtviewer.
Start JBoss.
Check the JBoss log to ensure that there are no errors.
If you do not deploy as 3 separate exploded WAR files, JBoss generates its own temporary directories to hold these deployments. This wouldn't be so bad except that JBoss creates new temporary directories every time you restart JBoss.
It's still possible to deploy KonaKart into JBoss using an "unexploded" konakart.ear file but you will not be able to use the "Edit Config Files" functionality in the KonaKart Admin Application. If you wish to deploy using the EAR file you simply drop it into the deploy directory of your JBoss installation for automatic deployment. Check your JBoss server log; there should be no errors during this deployment.
Set the port numbers (8080) for reporting as required (set these using the KonaKart Admin App under the Configuration > Reports section)
Set the HTTP (8080) and HTTPS (8443) port numbers as required (set these using the KonaKart Admin App under the Configuration > HTTP/HTTPS section). You will also have to setup SSL in JBoss if you haven't already done so (refer to JBoss documentation to find out how to do this). A quick way to do this if you don't have a keystore already (and for development purposes only) is to copy the conf/.keystore file from your KonaKart installation to the C:\jboss-4.2.2.GA\server\default\conf directory of JBoss, then edit your C:\jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml file as follows:
<!-- Define a SSL HTTP/1.1 Connector on port 8443
This connector uses the JSSE configuration, when using APR, the
connector should be using the OpenSSL style configuration
described in the APR documentation -->
<Connector port="8443"
protocol="HTTP/1.1"
SSLEnabled="true"
clientAuth="false"
sslProtocol="TLS"
keystoreFile="conf/.keystore"
keystorePass="kkpassword" />
Set the memory parameters to suit your environment (eg. I set JAVA_OPTS=-XX:PermSize=256m -XX:MaxPermSize=256m -Xms512m -Xmx1024m ).