#154

CONTENTS INCLUDE:

n Jetty Architecture n Configuring Jetty n Basic Usage Jetty n Advanced Usage n Using with Web Frameworks A Lightweight, Open-Source Web Server and Servlet Container n Running Standalone By Jos Dirksen n Integration with Maven and more... Visit refcardz.com

SelectChannelConnector Uses NIO buffers with a non-blocking threading ABOUT JETTY model. Threads are only allocated to connec- tions with requests. Use when there are many connections that have idle periods. Jetty, an open-source web server hosted by the Eclipse foundation, is a full-fledged HTTP server and Servlet container that can be easily SslSocketConnector SSL version of the SocketConnector configured to serve static and dynamic content. You can very easily SslSelectChannelConnector SSL version of the SelectChannelConnector embed Jetty into your own applications using Java or XML-based AJPConnector Use for connections from Apache modules: configuration or run Jetty directly from Maven. Additionally, you can use mod_proxy_ajp and mod_jk. Jetty in many different high-demand areas such as Yahoo Hadoop Cluster, HTTPSPDYServerConnector Supports the SPDY protocol and performs SPDY Google AppEngine, and Yahoo! Zimbra. to HTTP conversion. If SPDY is not negotiated, This RefCard refers primarily to Jetty 8; however, most of the configuration falls back to HTTPS.

Get More Refcardz! Refcardz! Get More discussed will work on Jetty 7. Handler JETTY ARCHITECTURE The handler is the component that deals with requests received by a connector. There are three types of handlers in Jetty.

It’s important to understand the architecture behind Jetty. The main • Coordinating handlers route requests to other handlers. architecture of Jetty consists out of the following four components. • Filtering handlers modify a request and pass it on to other handlers. • Generating handlers create content.

• Jetty provides the following handlers.

Name Description

ConnectHandler Implements a tunneling proxy that supports HTTP CONNECT.

DebugHandler Writes details of the request and response to an outputstream.

GzipHandler Will gzip the response

IPAccessHandler Provides access control using white/black lists on IP addresses and URLs.

RequestLogHandler Allows logging of requests to a request log.

ResourceHandler Serves static content and handles If-Modified-Since headers. Doesn’t handle 404 errors.

RewriteHandler Allows you to rewrite the URL, cookies, headers, and status codes based on a set of rules.

Server The server is the container class for all the other components of the architecture. A server contains a number of connectors that listen on a specific port and accepts connections (e.g., HTTP, HTTPS, or AJP13) from clients. A server also contains a set of handlers that process the client requests from the connectors and produce responses that are returned to the client. Threads retrieved from the configured threadpool do this processing.

Connector Jetty provides a number of connectors that accept requests from clients to be processed by the handlers. Jetty comes with the following set of default connectors.

Connector Description and Usage

SocketConnector Uses blocking IO and normal JRE sockets. One thread is allocated per connection. Only use when NIO connector isn’t available.

BlockingChannelConnector Uses NIO buffers with a blocking thread model. One thread is allocated per connection. Use when there are few very active connections. Core Jetty Core

DZone, Inc. | www.dzone.com 2 Jetty

ConstraintSecurity- Enforces security constraints based on Servlet specification 2.4. Public class JettyExample { Handler public static void main(String[] args) throws Exception { Resource fileCfg = Resource.newSystemResource(“example.xml”); StatisticsHandler Collects statistics on requests and responses. XMLConfiguration config = new XMLConfiguration(fileCfg.getInputStream()); Server.start(); WebSocketHandler Provides support for the websockets protocol. Server.join(); } HandlerCollection Contains a collection of handlers. Handlers are called in order. }

ContextHandlerCol- Contains a collection of handlers. Handlers are called based on The following elements can be used to configure Jetty. lection the provided context and virtual host.

HandlerList Like HandlerCollection, but calls each handler in turn until an XML Element Description exception is thrown, the response is committed, or a positive status is set. Configure The root element that specifies the class to be configured. Attribute “id”: reference to created object. ServletHandler Maps requests to servlets that implement the HttpServlet API. Attribute “class”: FQN to instantiate. Can contain: , , , , , , , ServletContextHan- See ServletHandler. Allows you to specify the context the servlet

Threadpool Get Maps a call to a getter method. Attribute “name”: getter to call The threadpool provides threads to the handlers, the work done by the Attribute “class”: if present, make a static call to the specified class. connnectors and the handlers. Jetty comes with the following threadpools. Attribute “id”: reference to returned object Can contain: , , , , , , ,

Call Makes an arbitrary call to the current object. CONFIGURING JETTY Attribute “name”: method to call Attribute “class”: if present, make a static call to the specified class. Attribute “id”: reference to returned object When you configure Jetty, you create and configure a set of connectors Can contain: , , , , , , , and handlers. You can do this using XML or plain Java. ,

Arg Specifies an argument for and XML configuration Attribute “type”: force type of value Jetty provides an XML-based configuration language based on the Java Can contain: , , , , ,

DZone, Inc. | www.dzone.com 3 Jetty

Java configuration Call name=”addConnector”> Using Java for the configuration of your Jetty server is very simple and is done in the same manner as we’ve shown for the XML configuration. Instead of using the XML elements to instantiate the objects, you can now etc/keystore do this directly from Java. You can rewrite the previous XML configuration OBF:1vny1zlo1x8e1vnw1 OBF:1u2u1wml1z7s1z/Set> to the following piece of Java. /etc/keystore OBF:w11x8g1zlu1vn4 true public static void main(String[] args) throws Exception { Server server = new Server(); 8443 QueuedThreadPool pool = new QueuedThreadPool(); pool.setMinThreads(10); pool.setMaxThreads(10); server.setThreadPool(pool);

SelectChannelConnector connector = new SelectChannelConnector(); connector.setPort(8080); server.addConnector(connector); The following properties are used:

HandlerList handlers = new HandlerList(); Property Description ResourceHandler resourceHandler = new ResourceHandler(); resourceHandler.setDirectoriesListed(true); resourceHandler.setResourceBase(“./files”); keystore Keystore for the server keypair DefaultHandler defaultHandler = new DefaultHandler(); handlers.setHandlers(new Handler[] keystorepassword Password for the keystore {resourceHandler, defaultHandler}); server.setHandler(handlers); keymanagerpassword Password for the private key server.start(); server.join(); truststore Keystore for trusted certificates } truststorepassword Password for truststore

needClientAuth True, if clients must use a certificate Since Jetty components are simple POJOs, you can also use your Hot dependency injection framework of choice to set up the Jetty server. Tip An example with Spring is shown here: http://wiki.eclipse.org/Jetty/ There are more advanced properties available. For these, see the Howto/Spring Javadocs for the SslContextFactory.

BASIC USAGE Jetty provides a utility that you can use to secure passwords in Hot configuration files. By using the org.eclipse.jetty.http.security.Passwd Tip class, you can generate obfuscated, checksummed, and encrypted This section describes how to use Jetty for a number of basic use cases. passwords. Serving static content When running Jetty as an embedded web server in your own application, Servlets and the ServletContextHandler it can be useful to be able to serve static content (e.g., documentation). The easiest way to server static content is by using a ResourceHandler: Jetty allows you to easily configure servlets without having to use a web. xml. To do this, you can use a ServletContextHandler, which allows for easy construction of a context with a ServletHandler. The following properties true can be set on a ServletContextHandler. ./files Property Description The ResourceHandler can be configured with the following properties:

Property Description contextPath The base context path used for this ServletContextHandler.

aliases Boolean; if true symlinks are followed. allowNullPathInfo If “false”, then /context is redirected to /context/.

directoryListed Boolean; if true show directory listings. compactPath If “true”, replace multiple ‘/’s with a single ‘/’.

welcomeFiles String[]; a welcome file is shown for a directory if it matches an errorHandler An “ErrorHandler” determines how error pages are handled. item from the supplied String[].

resourceBase String: The path from where to serve content. securityHandler The “SecurityHandler” to use for this ServletContextHandler.

sessionHandler The “SessionHandler” to use for this ServletContextHandler If you want the ResourceHandler to listen on a specific context, you can wrap this Handler in a ContextHandler: welcomeFiles List of welcomeFiles to show for this context. /documentation ... A servlet on this context can be added using the addServlet operation (which can also be done through XML).

addServlet(String className,String pathSpec) addServlet(Class servlet,String pathSpec) SSL configuration addServlet(ServletHolder servlet,String pathSpec) To configure Jetty to use HTTPS, you can use one of the SSL-enabled connectors: SslSelectChannelConnector or SSLSocketConnector. The Using existing WAR files and layout following listing defines two-way ssl (client authentication): Jetty allows you to directly use existing WAR files (and exploded WAR files) through the WebAppContext. This is especially useful during development.

DZone, Inc. | www.dzone.com 4 Jetty

Directly from a WAR: Configure id=”wac” class=”org.eclipse.jetty.webapp.WebAppContext”> Server server = new Server(8080); org.eclipse.jetty.webapp.WebInfConfiguration WebAppContext webapp = new WebAppContext(); org.eclipse.jetty.webapp.WebXmlConfiguration webapp.setContextPath(“/”); org.eclipse.jetty.webapp.MetaInfConfiguration webapp.setWar(jetty_home+”/webapps/test.war”); org.eclipse.jetty.webapp.FragmentConfiguration server.setHandler(webapp); org.eclipse.jetty.plus.webapp.EnvConfiguration org.eclipse.jetty.plus.webapp.PlusConfiguration org.eclipse.jetty.webapp.JettyWebXmlConfiguration From an exploded WAR (e.g. during development): org.eclipse.jetty.webapp.TagLibConfiguration Server server = new Server(8080); location/of/webapp WebAppContext context = new WebAppContext(); context.setDescriptor(webapp+”/WEB-INF/web.xml”); context.setResourceBase(“../test-jetty-webapp/src/main/webapp”); context.setContextPath(“/”); context.setParentLoaderPriority(true); server.setHandler(context); You can now use , , and entries in your web.xml to point to resources stored in the JNDI context. You can also configure a WebAppContext in jetty.xml using the XML- based configuration or in a context.xml file. Binding objects to JNDI Jetty allows you to bind POJOs, a java.naming.Reference instance, an Security Realms implementation of Java.naming.Referenceable, and a link between a name in the web.xml and one of these other objects. These objects can Security Realms allow you to protect your web applications. Jetty provides be configured from Java or in the jetty.xml configuration files. a number of standard LoginServices you can use to secure your web application. scope name to bind as the object to bind Name Description

HashLoginService A simple implementation that stores users and roles in memory and loads them from a properties file. The scope defines where the object is visible. If left empty, the scope is set JDBCLoginService Retrieves users and roles from a database configured with JDBC. to the Configure context this entry is defined in. This scope can also be set to point to a specific server of webapplication.

DataSourceLogin- Retrieves users and roles from a Javax.sql.DataSource. Service

JAASLoginService Delegates the login to JAAS. Jetty provides the following JAAS The following environment types are supported: modules: Type How to bind from Jetty • DBCLoginModule • PropertyFileLoginModule • DataSourceLoginModule env-entry • LdapLoginModule mySpecialValue 4000 To use a LoginServices, you configure it in the jetty.xml file. true resource-ref resource- env-ref RefCardRealm jdbc/myds etc/realm.properties 0 test create The real-name defined in the jetty.xml can now be referenced from the web.xml. Link With a Link you can link a resource from the web.xml to a resource in the containter context. FORM jdbc/datasourceInWeb RefCardRealm jdbc/nameInContainer /login/login /login/error Jetty-env.xml You can store environment settings in a jetty.xml file that is stored in your WEB-INF directory.

JNDI usage Jetty has support for Java:comp/env lookups in web applications. Setup JNDI The JNDI feature isn’t enabled by default. To enable JNDI, you have to set the following configurationClasses on your WebAppContext or ADVANCED USAGE WebAppDeployer: This section describes a couple of advanced configurations for Jetty. Integration with CDI When creating applications, it’s very useful to use context and dependency injection (CDI). With JEE6, this is a standard feature of an application server. You can also use CDI with Jetty. The following configuration can be used to configure Weld (the CDI reference implementation) for a specific web application on Jetty.

DZone, Inc. | www.dzone.com 5 Jetty

Besides the JDBC-based managers, you can also use MongoDB for Hot session clustering. For this clustering solution, you configure the BeanManager Tip MongoDBSessionIDManager and the MongoSessionManager”. javax.enterprise.inject.spi.BeanManager org.jboss.weld.resources.ManagerObjectFactory SPDY support SPDY is an experimental protocol whose goal it is to reduce the latency of web pages. Jetty can support this protocol through the HTTPSPDYServerConnector class. The beanmanager is available on java:comp/env/BeanManager. Running Jetty behind a reverse proxy your_keystore.jks Jetty can be configured to run behind a reverse proxy, such as Apache storepwd TLSv1 with mod_proxy or mod_proxy_ajp. The preferred way is to use mod_ proxy with a normal HTTP connector. However, it’s also possible to create a connector for the AJP protocol used by the mod_proxy_ajp modules. 8443 8009

For more information on running Jetty as a reverse proxy, see: http:// wiki.eclipse.org/Jetty/Howto/Configure_mod_proxy

Websockets USING WITH WEB FRAMEWORKS Jetty has support for websockets. You can create your own websockets servlet by extending WebSocketServlet. public class ExampleWSServlet extends WebSocketServlet { This section shows how to run an application based on a number of popular Java web frameworks using an embedded Jetty. This is especially protected void doGet(HttpServletRequest request, HttpServletResponse response) useful during development for a quick compile-build-test cycle or when throws ServletException ,IOException { you want to run your application in a debugger with hot-code replace. If getServletContext().getNamedDispatcher(“default”) .forward(request,response); your favorite web application framework isn’t listed here, these examples } should point you in the right direction to get Jetty working with your

protected WebSocket doWebSocketConnect( framework. HttpServletRequest request, String protocol) { return new ExampleWebSocket(); JSF 2.0 } JSF2 scans the WEB-INF/classes directories for beans. Before you can use class ExampleWebSocket implements WebSocket { an embedded Jetty to directly launch a JSF application, you have to make private Outbound outbound; sure you configure your project to output its class files to the WEB-INF/ public void onConnect(Outbound outbound) { classes directory in your project. After that, you can use the standard this.outbound=outbound; } WebAppContext to run your JSF 2.0 web application directly from Jetty.

public void onMessage(byte frame ,byte[] data,int offset, int length) { WebAppContext handler = new WebAppContext(); // handle binary data handler.setResourceBase(“src/main/webapp”); } handler.setDescriptor(“src/main/webapp/WEB-INF/web.xml”); handler.setContextPath(“/”); public void onMessage(byte frame, String data) { handler.setParentLoaderPriority(true); // handle String data }

public void onDisconnect() {} } Spring Web } Spring Web can be run directly from an exploded WAR file using a Session clustering standard WebAppContext (see GWT). You can also configure the Spring DispatcherServlet directly. Jetty uses two components for session management. First, a session

ID manager ensures that the session IDs are unique across all web ServletContextHanderl context = new ServletContextHandler applications. Second, a session manager handles the session lifecycle. (server, “/”, Context.SESSIONS); DispatcherServlet dispatcherServlet = new DispatcherServlet(); If you want to cluster your sessions, Jetty provides a JDBC-based dispatcherServlet.setContextClass( SessionIDManager and SessionManager. AnnotationConfigWebApplicationContext.class); ServletHolder holder = new ServletHolder(dispatcherServlet); holder.setInitOrder(1); Configure the JDBCSessionIdManager: context.addServlet(holder, “/example/*”); context.setInitParameter(“contextConfigLocation” ,”classpath*:resources/spring/*.xml”); JDBCSessionIdManager idMgr = new JDBCSessionIdManager(server); idMgr.setWorkerName(“fred”); idMgr. setDriverInfo(“com.mysql.jdbc.Driver”, “jdbc:mysql://127.0.0.1:3306/sessions?user=janb”); idMgr.setScavengeInterval(60); server.setSessionIdManager(idMgr); This context can be added as a handler to a server instance. Grails Grails already provides Jetty functionality out of the box. To run grails This JDBCSessionIdManager needs to be configured on each cluster node using an embedded Jetty container, you can use the grails run-app with a unique workerName. Once you’ve defined this ID manager, you can command. can configure the JDBCSessionManager. Wicket WebAppContext wac = new WebAppContext(); To run Wicket from Jetty, you can configure the WicketServlet with the … //configure your webapp context JDBCSessionManager jdbcMgr = new JDBCSessionManager(); jdbcMgr.setIdManager(server.getSessionIdManager()); applicationClassName you want to start. wac.setSessionHandler(jdbcMgr);

DZone, Inc. | www.dzone.com 6 Jetty

ServletContextHandler context = new ServletContextHandler webdefault.xml Set default values on a web application context that will be applied (server, “/”, Context.SESSIONS);ServletHolder ServletHolder holder = new ServletHolder(new WicketServlet()); to all web applications. This is loaded before the web.xml is pro- holder.setInitParameter( cessed. Located in ${jetty.home}/etc/webdefault “applicationClassName”,”dzone.refcard.Application”); // set init order to initialize when handler starts holder.setInitOrder(1); override-web.xml Jetty applies the configuration in this file after the web.xml from a context.addServlet(servletHolder, “/*”); web application is parsed. This file is located in the WEB-INF direc- tory of a web application This context can be added as a handler to a server instance. More information on running Jetty standalone can be found at the Jetty GWT, Vaadin and Tapestry Wiki: http://wiki.eclipse.org/Jetty/Feature/Start.jar You can directly run a GWT or a Vaadin application from an exploded WAR file using a standard WebAppContext. INTEGRATION WITH MAVEN

WebAppContext handler = new WebAppContext(); handler.setResourceBase(“./apps/TheGWTApplication”); Jetty is also often used in a maven build file to easily run and test a handler.setDescriptor(“./apps/TheGwtApplication/WEB-INF/web.xml”); webapp project. When running from Maven, you can configure Jetty using handler.setContextPath(“/”); handler.setParentLoaderPriority(true); the configuration elements provided by the plugin. XML Element Description This context can be added as a handler to a server instance. connectors List of connectors objects. If not specified, a SelectChannelCon- nector will be configured on port 8080.

RUNNING STANDALONE jettyXML Location of a jetty.xml configuration file. Use this for objects that can’t be configured from the plugin.

If you want to configure the standard Jetty distribution and not run Jetty scanIntervalSeconds Interval to check for changes to the webapp. If a change is embedded from your own application, you can configure Jetty using the detected, the webapp is redeployed. following XML files. systemProperties Sets system properties that are used during the execution of the plugin.

systemPropertiesFile Loads system properties from a file. These properties are avail- File Description able during the execution of the plugin.

jetty.xml Main configuration file. Configures a Server class. Normally located loginServices A list of LoginService implementations that are available to the in $JETTY_HOME/etc/jetty.xml webapp.

jetty-web.xml Configure a web application context. Located in the WEB-INF direc- requestLog Configures an implementation of a RequestLog. tory of a specific web application.

jetty-env.xml Allows you to configure JNDI resources for a web application. Located in the WEB-INF directory of a web application.

ABOUT THE AUTHOR RECOMMENDED RESOURCES Jos Dirksen works as Architect for JPoint. In the last Jetty provides a Web server and couple of years Jos has worked on large projects in the javax.servlet container, plus support public and private sector, ranging from very technology- for Web Sockets, OSGi, JMX, focussed integration projects to SOA/BPM projects JNDI, JASPI, AJP and many other using WS-* and REST based architectures. Jos has given integrations. These components are open source and available for many presentations on conferences such as Javaone, commercial use and distribution. Jetty is used in a wide variety of NL-JUG, Devoxx etc., and has written two books for projects and products. Jetty can be embedded in devices, tools, Manning: Open Source ESBs in Action and SOA Governance in frameworks, application servers, and clusters. See the Jetty Powered Action. He also has his own blog where he writes about interesting page for more uses of Jetty. technologies and shares his ideas about REST, API Design, Scala, Play and more. http://www.eclipse.org/jetty/

#82

CONTENTS INCLUDE: 150 ■ Browse our collection of over Free Cheat Sheets About Cloud Computing ■ Usage Scenarios Getting Started with dz.com ■ Underlying Concepts ■ Cost ... ® efcar ■ #64 Data Tier Technologies . Cloud Computing omply brought■ Platform to you Management by and more... e. C . Collaborat

isit r AldonChange By Daniel Rubio V

dz! also minimizes the needCONTENTS to make designINCLUDE: changes to support ABOUT CLOUD COMPUTING one time events. ■ HTML Basics dz.com ■ Upcoming Refcardz HTML vs XHTML Web applications have always been deployed on servers Automated growth & scalable technologies ■ Validation connected to what is now deemed the ‘cloud’. Having the capability■ to support one time events, cloud efcar

e Refcar Useful Open Sour computing platforms also facilitate the gradual growth curves ■ Page Structur #84 However, the demands and technology used on such servers ce T faced by web applications.■ ools isit r Key Structural Elementse Elements and mor has changed substantiallyBy Paul in recent M. years, Duvall especially with V Scala Collections

the entrance of service providers like Amazon, Google and Large scale growth scenarios involving specialized equipment Continuous Integration: CONTENTS INCLUDE: e... Patterns andMicrosoft. Anti-Patternse changes (e.g. loaddz! balancers and clusters) are all but abstracted away by ■ e at Every Change About Continuous Integrationns orkspace to isolat relying on a cloud computing platform’s technology. Cor ■ Build Softwar Description e in a Private W epository e HTML BASICS These companies have long deployedntrol r web applications

■ Patterns and Anti-patterol Develop softwar rging and to manag dz.com n that adapt and scale to large user bases, making them In addition, several cloud computing platforms support data e Patter fi les to a version-co ■ HTML Version Contr HTML and XHTML ar JavaFX 2.0 e... orkspaceknowledgeableCommit allin manyline aspects to minimize r meelated to cloud computing. tier technologies that exceed the precedent set by Relational ■ Build Management Private W hat utilizes multiple e Refcar HTML is used as the graphical user interface in client-side

Develop on a main Database Systems (RDBMS): Map Reduce,e the foundationweb service of APIs,all web development. efcar ■ Build Practices and mor Repository active code lines e within a system t ts of work pr TION This Refcard will introducear to you to cloud computing, with an etc. Some platformsograms support written lar gein JavaScript.scale RDBMS Server deployments. The sr By e Mainline Developing softw by task-oriented uni and Java also r c attribute describes wher Andy Harris Get Mor emphasis on these providers, so you can better understand codelines and the alt attribute describes alternate text that is displayed if ask Level Commit

isit r isit ol ce code changes as the output mechanism.eceive data The fr emer TINUOUS INTEGRA what it is a cloudganize computing sour es as aplatform T can offer your web the image is unavailable.

V Codeline Policy Or ce without -side languages like PHP e the image Opa ocess of building softwar likewise use HTML and XHTML as their visual engine. HTML Get Mor om web pages and use HTML s version contr applications.it and submit chang h unique name e from sour CLOUD COMPUTING PLATFORMS AND ABOUT CON oject’ was once a very loosely-defi Nested tags file can be found,

e.com Task-Level Comm Label the build wit es to build softwar are minimum UNDERLYING CONCEPTS

dz! dz! oblem ging Ajax technologies T standar ags can be (and fr USAGE SCENARIOSAutomate all gurationactiviti pendencies to the b dization, but as it has become mor Continuous Integration (CI) is the pr Label Build manual confi need for standar ned language with very little cannot overlap, so

zon e same deploymentonment , a solution to fectivea pr e-installed tool de equently ar target envir Amazon EC2: Industry standard software and virtualization b> with every change. committed to a pr Automated Build Reduce pr whether you chooseds tohas write become HTML mor or XHTML, understanding e) nested inside each other

ns (i.e., inef .d Pay only what you consume deployment, use th is fine. Data Warehousing epository cies AR or EAR) in each Amazon’s cloudthe curr computing platform is heavily based on r For each tagged e important, the

x” the particulare solutions problem) thatuce Web application deployment until a few years agoonment was similar ent standar e appar is not legal, but e Refcar e Minimal Dependen package (e.g. W dent libraries get envir industry standarthat willd simplifysoftwar alle and your virtualization other web coding. technology Fortunately. HTML ent. Regar HTML VS XHTML . T CI can be explained via patterns (i.e. can fi le that all tar ds will help you pr ags Binaryto Integrity most phone services:Centralize plans all depen withte alloted resources, with an and XHTML ar

Get Mor Get appear to be benefi ly, continually Every page (HTML or XHTML shar fects. They aresults when compar The various resourcesPerform consumed a Private by web applications (e.g. evelopment team individual operating system sinstances. Browser manufactur

adverse ef Staged Builds Repository tion Build periodical common.) All ar

bandwidth, memory, CPU) are tallied on a per-unit basis oduce unintended r d om CI server to d web developers came up with clever workar pr Private Build Perform an Integra edback fr extension. HTML e essentially plain text ers added many competing estandar than anybody his Refcar (starting from zero) by all major cloud computing occur platforms. As a user of Amazon’s EC2 cloud computinges certain platform, elements you inare result is a lack of standar the pattern. term Continuous Integration pr Send automated fe builds based on assignedocessor an operating systemfi in the same way as on all hosting Integration Build ors as soon as they les should not be cr The latest web standar

r documentation with e.com Continuous Integration de concepts such as While the conventionalefers to the use“build of theand test” cycle, t Generate develope expands on the notion of CI to inclu DZone, Inc. Cloud Computing 150 Preston Executive Dr. Suite 200 Cary, NC 27513 DZone communities deliver over 6 million pages each month to 888.678.0399 more than 3.3 million software developers, architects and decision 919.678.0300 makers. DZone offers something for everyone, including news, Refcardz Feedback Welcome tutorials, cheat sheets, blogs, feature articles, source code and more. [email protected]

“DZone is a developer’s dream,” says PC Magazine. $7.95 Sponsorship Opportunities Copyright © 2012 DZone, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, [email protected] Version 1.0 without prior written permission of the publisher.