This is an application to both learn and showcase the power of Java EE 6, JBoss Seam 3 / CDI and also Twitter's Bootstrap for looking nice :-) It is supposed to be run on JBoss AS 7.1, since it is utilizing a little more than the EE6 web-profile currently has to offer.
The application itself will be monitoring JMX-Applications and will be able to use both attributes
or methods to determine the status of a certain defined check.
Its web-interface should be mainly used as an adminsitration-frontend and there will be a
dashboard-view to put it on to big screens at the office to always see what's going on.
There is currently no plan to put in alerts or any other fancy stuff that the handful of
commercial apps are providing, but let's see where this project will take us.
All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.
The application this project produces is designed to be run on a JBoss AS 7.
NOTE: This project retrieves artifacts from the JBoss Community Maven repository, a superset of the Maven central repository.
With the prerequisites out of the way, you're ready to build and deploy.
First you need to start JBoss AS 7. To do this, run
$JBOSS_HOME/bin/standalone.sh
or if you are using windows
$JBOSS_HOME/bin/standalone.bat
To deploy the application, you first need to produce the archive to deploy using the following Maven goal:
mvn package
You can now deploy the artifact to JBoss AS by executing the following command:
mvn jboss-as:deploy
This will deploy target/jboss-javaee6-webapp-src.war.
The application will be running at the following URL http://localhost:8080/jboss-javaee6-webapp-src/.
To undeploy from JBoss AS, run this command:
mvn jboss-as:undeploy
You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 Getting Started Guide for Developers for more information.
By default, tests are configured to be skipped. The reason is that the sample test is an Arquillian test, which requires the use of a container. You can activate this test by selecting one of the container configuration provided for JBoss AS 7 (remote).
To run the test in JBoss AS 7, first start a JBoss AS 7 instance. Then, run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
If you created the project using the Maven archetype wizard in your IDE (Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should already have an IDE project.
If you created the project from the commandline using archetype:generate, then you need to import the project into your IDE. If you are using NetBeans 6.8 or IntelliJ IDEA 9, then all you have to do is open the project as an existing project. Both of these IDEs recognize Maven projects natively.
Detailed instructions for using Eclipse with JBoss AS 7 are provided in the JBoss AS 7 Getting Started Guide for Developers.
If you want to be able to debug into the source code or look at the Javadocs of any library in the project, you can run either of the following two commands to pull them into your local repository. The IDE should then detect them.
mvn dependency:sources
mvn dependency:resolve -Dclassifier=javadoc