In this OBE tutorial, you will use the WebLogic Server administration console to deploy a simple JavaEE Web application. After testing the application, you will then redeploy an updated version of it. Finally, you will use the console to undeploy the application.
Place the cursor over this icon to load and view all
the screenshots for this tutorial. (Caution: Because this action loads
all screenshots simultaneously, response time may be slow depending on
your Internet connection.)
Alternatively, you can
place the cursor over each individual icon in the following steps to
load and view only the screenshot associated with that step.
Overview
Interactive Web sites are developed and packaged in JavaEE as Web applications. Web applications, like any JavaEE application, can be deployed as an archive file. Web application archives use the file extension .war. JavaEE applications can include XML files called deployment descriptors to enable or configure JavaEE and WebLogic-specific features. For example, a Web application may use a deployment descriptor to specify the URL path that clients will use to access it from a Web browser.
All JavaEE application types are deployed in the same fashion on WebLogic Server using the administration console, the WebLogic Scripting Tool (WLST), or other available tools. All WebLogic Server applications go through two main phases during deployment. First, in the "prepared" phase, they are installed to your domain's administration server and distributed to target managed servers. Next, a prepared application can be "activated" so that it is accessible to clients on the target servers. When an updated version of your application is available, the application must essentially complete these same two phases again.
Start your administration server and dizzy1 managed server, if not already started. If prompted, enter your domain's administrative username and password.
2.
Download the benefits.zip file that contains the sample Web application benefits.war file.
3.
Launch a Web browser and access your domain's administration console. The default port is 7001:
http://localhost:7001
4.
Log into the console using your domain's administrative username and password.
5.
In the Change Center panel, click the Lock & Edit button:
6.
In the Domain Structure panel, click Deployments:
7.
In the main content panel, click the Install button:
8.
Find the Current Location field. Use the supplied links to browse to the location in which you placed the downloaded benefits.war file. Then select the radio button for benefits.war, and click Next:
9.
On the next page, accept the default option, and click Next.
10.
Under Servers, select the dizzy1 checkbox, and click Next:
11.
On the next page, accept the default options, and click Finish .
12.
In the Change Center panel, click Activate Changes:
13.
In the Domain Structure panel, click Deployments once again.
14.
Select the checkbox for the benefits application, and click the Start button:
15.
From the drop down list, select the Servicing All Requests option. Click Yes when prompted:
16.
Confirm that under the State column, the benefits application is listed as "Active".
Download an updated version of benefits.war. Replace the current file. The Web application's deployment descriptors have been modified to use a different URL context path.
2.
Return to the Deployments page of the administration console.
3.
In the Change Center panel, click Lock and Edit.
4.
Select the checkbox for the benefits application, and click the Update button:
5.
Click Finish.
6.
Click Activate Changes in the Change Center panel.
7.
Direct your Web browser to the URL:
http://localhost:7003
The benefits application should now be available at this new URL path.
Bookmark
Place the cursor over this icon to load and view all
the screenshots for this tutorial. (Caution: Because this action loads
all screenshots simultaneously, response time may be slow depending on
your Internet connection.)
