Message-ID: <169414832.25982.1406963204477.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_25981_745722058.1406963204477" ------=_Part_25981_745722058.1406963204477 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document explains how to configure Cargo remote deployment = support on a Jetty container.
By default, Jetty does not come with possibilities for remote deployment= . In order to add such a support to Jetty, Cargo uses a "Jetty remote = deployer" Web application.
This application is a simple servlet-based application which exposes met= hods such as deploy or undeploy on standard HTTP POST URLs. When thse HTTP = methods are called, the servlet implementing these methods connects to the = Jetty Server implementation and does deployment related actions on the serv= er; this Web application can therefore be seen as a kind of remote administ= ration proxy.
Being a standard Web application, the Cargo Jetty remote deployer applic= ation can be secured using Jetty users and roles.
Two versions of the Jetty remote deployer WAR are available on the Cargo downloads page (scroll down to th= e Tools section):
cargo-jetty-7-and-onwards-deployer: The Deployer Web appli= cation for the Jetty remote containers, which must have been deployed to Je= tty before using the CARGO remote deployer. Designed to work with Jetty 7.x= and later (Jetty from Eclipse.org)
cargo-jetty-6-and-earlier-deployer: The Deployer Web appli= cation for the Jetty remote containers, which must have been deployed to Je= tty before using the CARGO remote deployer. Designed to work with Jetty 6.x= and earlier (Jetty from Mortbay.org)
Please make sure to download and install the correct flavour for your Je= tty version.
By default, the Cargo Jetty remote deployer comes with no security.
In order to activate security, follow these steps:
WEB-INF/web.xmlfile of the Cargo Jetty remote de= ployer WAR
Uncomment in order to activate secur= ity. By default, that configuration is as follows:
login-config<= /code> set to
Add, for example, the following definition
To try the security settings, you can try to visit the
y-deployer context on your server, for example http://production27:8080/cargo-jetty-deployer, using any Web browser=
. If security is configured well, it should:
Command / is unknown= code>
Here is an example Maven2 plugin configuration that:
somepasswor= dis defined as
To run the given Maven2 plugin configuration on a simple Maven2 WAR proj= ect, simply execute: