Download the benefits.war file to the machine where your WebLogic Server domain and servers are. This is a sample Java web application archive to deploy.

If the administration server of the domain is not already running, it needs to be started. To start it, in a Terminal window, navigate to the domain directory, and enter the command:

$ ./startWebLogic.sh

When prompted for a username and password enter the credentials of the domain administrator.

The managed server dizzy1 should also be running. If it is not already running, start it. In another Terminal window, navigate to the domain directory, then cd into the bin subdirectory. Enter the command:

$ ./startManagedWebLogic.sh dizzy1 http://host01.example.com:8001

This runs the script to start the managed server named dizzy1. Also notice the argument that gives the URL of the domain's administration server:
http://host01.example.com:8001.

Note: Use the host name and port of the administration server of your domain.

When prompted for a username and password enter the credentials of the domain administrator.

After the servers are up and running, access the WebLogic Server administration console. Open a web browser and enter the URL of the domain's administration console:
http://hostname:port/console

In this tutorial, that is: http://host01.example.com:8001/console

Note: Use the host name and port of the administration server of your domain.

On the Welcome screen, log in using the Username and Password entered to start the servers.

Deploying an application is a change to the domain's configuration, so it must first be locked. In the Change Center, click the Lock & Edit button.

Under Domain Structure, click Deployments.

On the right, under Deployments, click the Install button.

Find the Current Location field. Use the links to browse to the location in which you placed the downloaded benefits.war file. There you will see benefits.war with a radio button next to it. Select that radio button. By using the links and the radio button, the console fills in the Path field for you.

Alternatively, you can type in the path and file name in the Path field yourself.

Then click Next.

On the next screen, ensure that Install this deployment as an application is selected.

Then click Next.

On the next screen, select dizzy1.

Then click Next.

On the next screen, keep all the default values and click Next.

On the next screen, select No, I will review the configuration later. Then click Finish.

Notice the messages that the deployment was installed, but changes must be activated. Also notice the benefits application listed in the Deployments table.

In the Change Center click the Activate Changes button.

Notice the message that the changes have been activated. Also notice the benefits application listed in the Deployments table is now in the "Prepared" state.

Select the check box to the left of the benefits application in the Deployments table. Then use the Start drop-down list to select Servicing all requests.

Click Yes to continue.

A message is displayed indicating a start request was sent. Momentarily you will see the State of the benefits application become "Active." This means that the application is available to those that have access to the server.

In another web browser, enter the host and port for the dizzy1 managed server, followed by /benefits.

In this tutorial, the URL entered is:
http://host01.example.com:8003/benefits

Select one or more of the check boxes and click the Get Information button.

Then click the Back To Home Page link.

Download an updated version of the web application, the benefits2.war file. The web application's deployment descriptors have been modified to use a different context root (path) to access the application.

After it has been downloaded, rename benefits2.war to benefits.war. Replace the current benefits.war file with this new one.

Return to the Deployments page of the administration console.

If needed, in the Change Center, click the Lock & Edit button.

Select the check box to the left of the benefits application in the Deployments table.

Then click the Update button.

On the next screen, click the Finish button.

In the Change Center click the Activate Changes button.

In another web browser, enter the host and port for the dizzy1 managed server (do not put /benefits on the end of the URL).

In this tutorial, the URL entered is:
http://host01.example.com:8003

The new version of the benefits application has the context root of / rather than the context root of benefits, as the previous version had. In other words, the benefits application is now the default application of the dizzy1 server.

Return to the Deployments page of the administration console.

Select the check box to the left of the benefits application in the Deployments table. Then use the Stop drop-down list to select Force Stop Now.

Click Yes to continue.

The benefits application has now been stopped and is no longer available. In a web browser when its URL is entered the server returns a 404 error.

Note: The web browser may have cached pages. If the benefits application does appear, click the refresh button of the web browser.

Return to the Deployments page of the administration console.

If needed, in the Change Center, click the Lock & Edit button.

Select the check box to the left of the benefits application in the Deployments table.

Then click the Delete button.

Click Yes to continue.

Messages will be displayed indicating the deployment was deleted, but the changes must be activated. In the Change Center click the Activate Changes button.

The benefits application is no longer in the domain configuration. The archive file still exists, however, and the application could be deployed again.