<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
AS7 Deployment Terms
</h3>
<span style="margin-bottom: 10px;">
modified by <a href="http://community.jboss.org/people/ssilvert">Stan Silvert</a> in <i>JBoss AS7 Development</i> - <a href="http://community.jboss.org/docs/DOC-16804">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>AS7 adds a lot of new functionality to the world of deployments.  Consequently, there is a need to add new terms and define some old terms more strictly.  This document provides a means to define deployment-related terms and explain a bit about AS7 deployments along the way.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><table border="1" cellpadding="3" cellspacing="0" class="jiveBorder" height="472" style="border: 1px solid #000000; width: 856px;"><tbody><tr><th align="center" style="background-color: #6690bc;;border: 1px solid #000000;background-color: #6690bc;" valign="middle"><span style="color: #ffffff;"><strong>Term<br/></strong></span></th><th align="center" style="background-color: #6690bc;;border: 1px solid #000000;background-color: #6690bc;" valign="middle"><span style="color: #ffffff;"><strong>Definition<br/></strong></span></th><th align="center" style="background-color: #6690bc;;border: 1px solid #000000;background-color: #6690bc;" valign="middle"><span style="color: #ffffff;"><strong>Notes<br/></strong></span></th></tr><tr><td style="border: 1px solid #000000;">deployment</td><td style="border: 1px solid #000000;">The bits that make up an application.  A deployment consists of one or more content archives.</td><td style="border: 1px solid #000000;">Examples are WAR, EAR, JAR, RAR</td></tr><tr><td style="border: 1px solid #000000;">deploy</td><td style="border: 1px solid #000000;">This is what happens when a deployment starts to initalize and become available for use.  Note that "deploy" is not something you do directly.  It is what happens when a deployment is ready to run.</td><td style="border: 1px solid #000000;">Actions that might cause a deployment to deploy might be a server starting, or enabling a disabled deployment.</td></tr><tr><td style="border: 1px solid #000000;">undeploy</td><td style="border: 1px solid #000000;">This is what happens when a running deployment shuts down and executes its uninitialization process.  The deployment will then cease to respond to user requests.</td><td style="border: 1px solid #000000;">Actions that might cause an undeploy would be to disable a deployment or remove a deployment.</td></tr><tr><td style="border: 1px solid #000000;">redeploy</td><td style="border: 1px solid #000000;">This is what happens when a running deployment does an undeploy followed by an immediate deploy.</td><td style="border: 1px solid #000000;">Actions that might cause a redeploy would be to sucessively disable and enable a running deployment.  In some cases a redeploy would happen when the deployment's content bundle is updated.</td></tr><tr><td style="border: 1px solid #000000;">content bundle / content archive / content</td><td style="border: 1px solid #000000;">Sub-archives that make up a deployment are content archives.  The archives together may be referred to as a content bundle or just content.</td><td style="border: 1px solid #000000;">For example, an EAR deployment might consist of a WAR, an ejb JAR, and a RAR.  Altogether, the EAR is a content bundle.  Each of its parts are content archives.</td></tr><tr><td style="border: 1px solid #000000;">managed content</td><td style="border: 1px solid #000000;">A content bundle that is uploaded to a standalone AS7 instance or an AS7 domain.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">content store</td><td style="border: 1px solid #000000;">The place where managed content is kept and managed by a standalone AS7 instace or an AS7 domain</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">upload</td><td style="border: 1px solid #000000;">Copy a deployment's bits into the content store.  <span style="color: #ff0000;"><em>Should the CLI change the name of the "deploy" command to "upload"?  Right now the console uses the term "upload".</em></span></td><td style="border: 1px solid #000000;">Depending on the tool used and the options chosen, an upload may or may not cause the deployment to immediately deploy.</td></tr><tr><td style="border: 1px solid #000000;">unmanaged content</td><td style="border: 1px solid #000000;">Content that exists on a file system.  It can be referenced and deployed by AS7, but its bits are managed manually on a file system.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">exploded content</td><td style="border: 1px solid #000000;">unmanaged content that is not in jar format.  Instead, it is "unzipped" onto a file system.</td><td style="border: 1px solid #000000;">Any deployment or content bundle can be exploded onto a file system.  The root of the exploded content bundle should be a directory that mimics an archive file name such as /foo.ear/ or /bar.war/</td></tr><tr><td style="border: 1px solid #000000;">unexploded content</td><td style="border: 1px solid #000000;">unmanaged content that is in a jar format.  It exists on the file system with a well-known extension such as .war, .ear, or .jar</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">deployment name</td><td style="border: 1px solid #000000;">The name of the deployment.  In an AS7 domain, this name must be unique across the entire domain.  The name must also be unique in a standalone server.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">runtime name</td><td style="border: 1px solid #000000;">The EE application/module name.  This name must be unique in a standalone server.  In a domain, it must be unique within a server group.</td><td style="border: 1px solid #000000;"><span style="color: #ff0000;"><em>I think this needs some better explanation and a better definition.  For instance in the case of an EAR does it always correspond to a name in application.xml?<br/></em></span></td></tr><tr><td style="border: 1px solid #000000;">enable</td><td style="border: 1px solid #000000;">Enable a deployment to deploy.  If there are no errors, the deployment will complete its initialization process and make itself available as an application.</td><td style="border: 1px solid #000000;">In the case of a domain, a deployment can be enabled or disabled for each individual server group.</td></tr><tr><td style="border: 1px solid #000000;">disable</td><td style="border: 1px solid #000000;">Stop a deployment from running.  The deployment will start its uninitialization process and stop taking user requests.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">assign</td><td style="border: 1px solid #000000;">Assign a deployment to a server group.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">unassign</td><td style="border: 1px solid #000000;">Unassign a deployment from a server group.</td><td style="border: 1px solid #000000;"><br/></td></tr><tr><td style="border: 1px solid #000000;">remove</td><td style="border: 1px solid #000000;">Make the deployment unknown to the standalone server or domain.  In the case of managed content, the content <strong>will</strong> be removed from the content store.  In the case of unmanaged content, the content <strong>will not</strong> be removed from the file system.</td><td style="border: 1px solid #000000;"><br/></td></tr></tbody></table></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="http://community.jboss.org/docs/DOC-16804">going to Community</a></p>
<p style="margin: 0;">Create a new document in JBoss AS7 Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>