As of CARGO 1.0.3, the way CARGO supports remote deployments on the JBoss Application Server has drastically evolved. This document explains how to configure this support.
JBoss 4.0.x and 4.2.x
In JBoss 4.x, the JMX-based remote deployer can accept URLs that point to another machine. For example:
In this case, our JBoss server on
10.156.216.127 will connect to
10.156.220.90 via HTTP and download the
paruemas-1.0-SNAPSHOT.war file. Once the file is downloaded, JBoss will automatically deploy it.
The CARGO JBoss container uses this principle to expose your Java EE application to JBoss using an HTTP server that is started on the machine where CARGO is currently running. That HTTP server is controlled using two parameters:
cargo.jboss.remotedeploy.hostname): sets the hostname that the JBoss server will attempt to connect to. By default, the CARGO JBoss container will automatically resolve the current machine's network name or IP address and fill this accordingly.
cargo.jboss.remotedeploy.port): sets the port number on which the HTTP server will be started on the machine running CARGO. By default, that one is set to 1 + the HTTP port for JBoss. For example, if JBoss is running on HTTP port
8080, then the default for
The obvious limitation you should be aware of is that JBoss needs to have direct access to the machine running CARGO.
JBoss 5.0.x, 5.1.x, 6.0.x and onwards
Starting from JBoss 5.x, JBoss has a Deployment Manager that can be used for deploying things on the JBoss server. If you really want to know how it works under the hood, you can read about this feature on the JBoss Website. If you only want to remotely deploy applications using CARGO to your JBoss server, you can of course ignore that document.
To connect to the JBoss Deployment Manager, CARGO uses JBoss' JMX RMI port; and that's what makes things get a bit complicated. For the connection to succeed, the following JARs need to be in the container classpath or in the current Java Thread's context classloader:
- The CARGO JBoss remote deployer for your version of JBoss
- JBoss deployment manager JARs
- JBoss remoting client JARs
Here is an example code for the users of the Java API:
Here is an example Maven2 plugin configuration:
Starting from CARGO 1.1.0, it is also possible to remotely deploy to JBoss farms versions 5.x and newer. To do so, use these two properties:
true, deployment is done in the
cargo.jboss.configuration: JBoss profile name, default name is