Getting Started with WebSphere Application Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
172 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Community Edition<br />
prefix (for example org/apache/geronimo) of the organization that supplies<br />
the library.<br />
- Artifact is the file name prefix of the library.<br />
- Version is the version identifier of the library.<br />
- Type is the type of file, typically jar.<br />
When you package your application, you have to prepare a deployment plan (for example,<br />
for a Web application, a geronimo-web.xml under WEB-INF directory). The<br />
Community Edition server can look into the plan and the deployment descriptor (for<br />
example, for a Web application, a web.xml under WEB-INF directory) to find<br />
information about the application. If your application uses the library that you have just<br />
installed, you have to add a element under in the<br />
element in the application's deployment plan. Listing 9.4 provides an<br />
example of an application deployment plan showing dependencies.<br />
<br />
…<br />
<br />
<br />
<br />
Group<br />
Artifact<br />
Version<br />
Type<br />
<br />
<br />
<br />
<br />
…<br />
<br />
Listing 9.4 - Dependency snippet<br />
9.6 Administering applications<br />
This section describes how to administer applications, such as managing their deployment,<br />
and stopping and starting them.<br />
9.6.1 Deploying and undeploying applications<br />
When you finish packaging an application, you can deploy the application to the<br />
Community Edition server using the administrative console. For example, if you have a<br />
Web application cviewer-2.1.1.2.war under the directory<br />
usr/local/wasce_samples/cviewer/target, and the deployment plan under the
Change language