Quickstart Guide to Deploying Modules

The following sections how to quickly deploy a module in a BEA WebLogic Server^TM domain:

• Step 1: Unpack the Archive File (if Necessary)
• Step 2: Start the Deployment Assistant
• Step 3: Select the Deployment Files
• Step 4: Select the Target Servers
• Step 5: Deploy the Files

 

---

Step 1: Unpack the Archive File (if Necessary)

Deploy modules using an available archive file (.EAR, .WAR, .JAR, or .RAR extension) unless:

• You are deploying a module that performs file I/O and must have a fixed directory structure.
• You are deploying a Web Application and you would like to update static files after the application is deployed.

If either of the above conditions apply, deploy the module from an exploded archive directory. To create an exploded directory, use the jar utility to unpack the archive file. Start by creating an empty directory in which you will store the files and moving to the new directory. Name the directory according the application or module you are deploying. For example:

mkdir mywebapp
cd mywebapp

Use the jar utility to unpack the archive:

jar xf c:\production\mywebapp.war

If you are unpacking an .EAR archive, the archive may contain additional archive files (.JAR and .WAR extensions). In this case, also unpack the embedded archives in the exploded directory:

jar xf mymodule1.war
jar xf mymodule2.jar

Verify that you have unpacked all archive files in the exploded directory.

 

---

Step 2: Start the Deployment Assistant

Access the Administration Console for the domain by loading its URL in your browser (for example, http://myhost:7001/console) and entering the administrator username and password.

Expand the Deployments Node in the left pane of the console, and select the type of module you want to deploy. The available module types are:

• Applications—Enterprise Applications or Web Services packaged as .ear files or directories
• EJB Modules—Enterprise JavaBean modules
• Web Application Modules—Web Applications or Web Services packaged as .war files or directories
• Connector Modules—Resource adaptors

The right pane of the Administration Console displays currently-deployed modules of the selected type. Click the Deploy a New module link in the right pane to start the Deployment Assistant for the Module.

 

---

Step 3: Select the Deployment Files

In the first page of the Deployment Assistant, use the links in the Location field to browse directories on the Administration Server machine and locate the Enterprise Application or Web Service to deploy. (If the application does not reside on the Administration Server machine, first use the upload link to upload the application.)

When the assistant detects a valid archive file or exploded archive directory in the current directory, it lists the archive or directory name as a selection beneath the Location field. Select the name of the archive or directory you want to configure for deployment.

If you are deploying an Enterprise Application and your domain contains multiple WebLogic Server instances, you have the option to deploy all modules in the application to a single server, or target different modules of the application to different server instances. Click the Target Application or Target Each Module button, respectively. For other module types, click Continue to select target servers.

 

---

Step 4: Select the Target Servers

In the second page of the deployment assistant, use the check boxes to select target servers on which you will deploy the module. To deploy to individual servers, select one or more server instances from the Independent Servers list and click Continue.

To deploy to a cluster of servers, select the name of the cluster from the Clusters list. By default, the assistant deploys an application or module to all server instances in the cluster (the All servers in the cluster option). If you want to deploy to only a subset of the servers in a cluster, select Parts of the cluster and then select the individual server instances to which you want to deploy the application or module.

If you are targeting individual modules of an Enterprise Application, your selections apply only to the module name displayed in the header of the console page (for example, Step 2 - Select targets for module "module_name"). If the application has additional modules to deploy, the console re-displays the Select Targets page after you click Continue, allowing you to target the next module to different server instances.

Click Continue when you have finished selecting target servers for the module.

 

---

Step 5: Deploy the Files

On the final page of the deployment assistant, you review your selection of target servers, choose a deployment staging mode, and define a deployment name for the module. Review the entries under the Deployment Targets heading. If you need to change a target, click your browser's Back button.

The Source accessibility header displays the selected staging mode for deploying the archive file or exploded archive directory:

• Copy this application onto every target for me—This option is selected by default if you targeted the module to a cluster or to multiple server instances. This corresponds to "stage" mode where the Administration Server copies the application files to each targeted server; the targeted servers then deploy the application using their copy of the source files.
• I will make the application accessible from the following location—This option is selected by default if you targeted the module to a single server instance. This corresponds to "nostage" mode where the server deploys a module from a single directory; all targeted servers must be able to access the directory to deploy the application. Select this option if you are deploying to a cluster that resides on a single physical machine.

In the Identity header, the Name field specifies a unique name to refer to this deployment in the Administration Console. Accept the default name or enter a new name to describe the application or module.

Click Deploy to accept the values on this page and deploy the module to the listed server instances.