Posted on

Deploying applications with Oracle WLS

 

Configuring Oracle Weblogic Staging mode

The deployment staging mode determines how a module’s archive files are made available to target servers. WebLogic Server provides three different options for staging archive files: stage mode, nostage mode, and external_stage mode. You can set the staging mode either at application level or at server level.

When you deploy an application or module using the Administration Console, the staging mode is set at the application level. The application staging mode always overrides any deployment mode specified for the target server itself.

The following picture shows how you can set up the staging mode from the Administration Console, through the Deployment optional settings:

 

The following table describes the difference between the three kinds of staging modules which you can select:

Mode

Description: The Administration Server does not copy the archive files from their source location. Instead, each targeted server must access the archive files from a single source directory for deployment

(e.g. via a shared directory).

When to use:

Deploying to a single-server domain or to a cluster on a multi-homed machine.

Deploying very large applications available on a shared directory.

Deploying exploded archive directories that you want to periodically redeploy after changing content.

Description:

Indicates that the Administration Server copies the deployment files from their original location to the staging directories of each targeted server.

When to use:

Deploying small or moderate-sized applications to multiple WebLogic Server instances/cluster.

Description:

Similar to stage mode, in that the deployment files must reside locally to each targeted server. However, the Administration Server does not automatically copy the deployment files to target servers; instead, you must ensure that the files are copied to the staging directory of each targeted server

When to use:

Deployments where you want to manually control the distribution of deployment files to target servers.

Deployments that do not require partial redeployment of application components.

How to set the Staging mode at Server level

The server staging mode specifies the default deployment mode for a server if none is specified at deployment time. In order to configure it, perform the following steps:

  1. In the left pane of the Console, expand Environment | Servers.
  2. From the central panel, click on the name of the server instance that you want to configure and select Configuration | Deployment to display the current staging mode, as depicted by the following screen:

 

 

Select the Staging Mode (follow the indications contained in the earlier section) and enter the Staging Directory Name field, which is the path to store staged deployment files.

Overriding the context root of your web application

Besides from setting the Web context root in application.xml, (if you are deploying an EAR archive) Oracle WebLogic server allows another way to override the default context of a Web appplication, that, is by using its specific deployment descriptor for web applications:  weblogic.xml

<weblogic-web-app

        xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”

        xsi:schemaLocation=”http://www.bea.com/ns/weblogic/weblogic-web-app

            http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd”

        xmlns=”http://www.bea.com/ns/weblogic/weblogic-web-app”>

           <context-root>InitialCtxRoot</context-root>

</weblogic-web-app>

As you can see from the above snippet, just specify a value for the context-root element and WLS will assign that Web context to your applications.