During this tutorial, you will deploy the J2EE application that you assembled during the Application assembly tutorial. Deployment involves configuring the server and supporting resources (you will use the existing default server), and installing the application. Installing the application means configuring the settings pertaining to this application in the server runtime. The runtime settings include choices such as whether to automatically load servlets, or to precompile JSP files.
Before performing this tutorial, either:
If you completed the Application assembly tutorial, you simply need to know the location of the simpleSession.ear file that you assembled, including generating code for deployment. It should be located in the directory:
product_installation_root/temp/tutorial/assembly/Deployed_simpleSession.ear
If you did not perform the assembly tutorial, and thus plan to use the already assembled .ear file:
product_installation_root/temp
product_installation_root/temp/tutorial
First, start the product using:
<product_installation_root>/startServer
Leave the command window open, as you will use it again later to start the server.
Plan to use the default
server configuration file for this tutorial.
Other configurations are available, including those that you customize.
Starting the server from a system command prompt is
a method available on all supported operating systems. There are other ways to start the server,
as well as variations of the startServer command.
This tutorial assumes that the
commands to start the product and tooling can be issued at a system command
window, opened anywhere on your machine. If you have any trouble, change
directory to:
product_installation_root/binand try the command again.
To open the administrative console:
http://your_host_name:9090/adminwhere your_host_name is localhost if the Web console is on the local machine. On Windows 2000, it has been found that localhost is not always recognized. In such a case, use the actual host name.
Even if you have not secured the console yet,
you will be prompted to log in. The login area explains this somewhat. For more information
about the use of this ID, see the help for starting and logging
into the console. It will also contain any additions, corrections, and details
pertaining to the above instructions.
For the purposes of the tutorial, use the WebSphere runtime environment "as is." The default application server and other resources are everything you need to deploy the simpleSession application.
The application is now displayed in the list of installed applications.
The administrative console is good at prompting you to take action
when you need to do so. In this case, it will now remind you to save your
server configuration file and regenerate
the configuration of the WebSphere plug-in for the Web server you are using. The
prompts are displayed directly below the console menu bar.
If that does not work, in the tree view of the console, click:
Nodes -> your_host_name -> Enterprise Applications
The server will issue a confirmation message in the launch window when it has started successfully.
Because adding a new application requires
a change to the server configuration file, the server must be stopped and started
again to pick up the change. However, there are some types of changes you can
make to an installed application that do not require stopping the server and
starting it again. See the dynamic reloading and hot
deployment documentation for more information.
Now that you have your application deployed, it is time to verify that users will be able to access it, using either a Web client or Java client. The next steps are described in the Application testing tutorial.