76 lines
5.2 KiB
HTML
76 lines
5.2 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Deploy and start a new application</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h2><a name="guidplyapp"></a>Deploy and start a new application</h2>
|
||
|
|
|
||
|
|
<p>Before you can deploy and start a new application, you must create and configure an application server instance. If you have not already done so, see <a href="guicrtapp.htm">Create a new application server</a> for information.</p>
|
||
|
|
|
||
|
|
</p>An application can consist of one or more Web modules packaged in an Enterprise Archive (EAR) file, or a single Web module packaged as a stand-alone Web Archive (WAR) file. A Web module is a logical piece of an application, containing objects like Java servlets, JavaServer Pages (JSP) files, and HTML pages. The file must exist in the location specified before the wizard can proceed.</p>
|
||
|
|
|
||
|
|
<p>To deploy a new application, follow these steps:</p>
|
||
|
|
<ol>
|
||
|
|
<li><p><a href="../../../rzaie/rzaiegetstarted.htm">Start the HTTP Server Administration interface</a>.</p></li>
|
||
|
|
<li><p>Click the <strong>Manage</strong> tab.</p></li>
|
||
|
|
<li><p>Expand <strong>Tasks and Wizards</strong>.</p></li>
|
||
|
|
<li><p>Click <strong>Install New Application</strong>.</p></li>
|
||
|
|
<li><p>Select one of these options:</p>
|
||
|
|
<ul>
|
||
|
|
<li><strong>Application is contained in an EAR file</strong>
|
||
|
|
<ol type="a">
|
||
|
|
<li>Click <strong>Browse</strong> or specify the fully qualified path name of the EAR file.<br>
|
||
|
|
<p><strong>Note:</strong> It is not necessary to specify the context root for an EAR file. The context root is specified in the EAR file.</p></li>
|
||
|
|
</ol></li>
|
||
|
|
<li><strong>Application is contained in a WAR file</strong>
|
||
|
|
<ol type="a">
|
||
|
|
<li>Click <strong>Browse</strong> or specify the fully qualified path name of the WAR file.</li>
|
||
|
|
<li>Specify the root of the context in the <strong>Context root</strong> field. The context root is the path used in a client request to access the application resources.</li>
|
||
|
|
</ol></li>
|
||
|
|
</ul></li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>Specify a name for the application in the <strong>Application name</strong> field. The default value is the name of the file.
|
||
|
|
<p><strong>Note:</strong> The application name value is specified within the file application. If not specified, the application name value defaults to the name of the application file.</p></li>
|
||
|
|
<li><strong>Optional:</strong> Select <strong>Pre-compile JSPs</strong> to compile JSP files into Java servlet code during the installation of the application. If the JSP file is pre-compiled, the application runs faster the first time you start it. However, depending on the number of JSP files in the application and the size of your system, pre-compiling all JSP files can cause the install of the application to take a significant amount of time.</li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>Select a virtual host to map to a Web module from the <strong>Map web modules to virtual hosts</strong> table. The virtual host determines the IP Address or hostname that is used to access your application. See <a href="guimngvhsts.htm">Manage virtual hosts for your application server</a> for information on creating new virtual hosts.</li>
|
||
|
|
<li>Click <strong>Next</strong>.</li>
|
||
|
|
<li>The summary page lists all of the choices you have made in the wizard. If any of the information displayed is incorrect, click <strong>Back</strong> until you reach the wizard form with the incorrect information and make your corrections. Click <strong>Finish</strong> to complete the wizard.</li>
|
||
|
|
<li>After you deploy the application,
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="guimngapp.htm">Manage installed applications</a></strong><br>
|
||
|
|
This topic describes how to start and stop applications, and how to enable and disable applications.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="acappinst.htm">Install and uninstall applications with the WebSphere administrative console</a></strong><br>
|
||
|
|
This topic describes how to use the administrative console to install and uninstall applications in your application server.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsaappinst.htm">Install and uninstall applications with wsadmin</a></strong><br>
|
||
|
|
This topic describes how to use wsadmin to install and uninstall applications in your application server.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="acappstr.htm">Start and stop applications with the WebSphere administrative console</a></strong><br>
|
||
|
|
This topic describes how to use the administrative console to start and stop applications.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsaappstr.htm">Start and stop applications with wsadmin</a></strong><br>
|
||
|
|
This topic describes how to use wsadmin to start and stop applications.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="qshearexp.htm">Use the EARExpander script to work with applications</a></strong><br>
|
||
|
|
This topic describes how to use the EARExpander script in Qshell to expand and collapse applications in EAR files.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="appadv.htm">Advanced application configuration</a></strong><br>
|
||
|
|
This topic describes advanced application settings that you can configure.</p>
|
||
|
|
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|