Controlling Deployment File Copying with Staging Modes in WebLogic

Hi All,

The deployment staging mode determines how deployment files are made available to target servers that must deploy an application or stand-alone module. WebLogic Server provides three different options for staging files: stage mode, nostage mode, and external_stage mode.

stage

The Administration Server first copies the deployment unit source files to the staging directories of target servers. (The staging directory is named stage by default, and it resides under the target server’s root directory.)

The target servers then deploy using their local copy of the deployment files.

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

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password weblogic -name mydeploymentname
-targets myserver1,myserver2,myserver3 -stage
-deploy c:\localfiles\myapp.ear


nostage

The Administration Server does not copy deployment unit files. Instead, all servers deploy using the same physical copy of the deployment files, which must be directly accessible by the Administration Server and target servers.

With nostage deployments of exploded archive directories, WebLogic Server automatically detects changes to a deployment’s JSPs or Servlets and refreshes the deployment. (This behavior can be disabled if necessary.)

  • Deploying to a single-server domain.
  • Deploying to a cluster on a multi-homed machine.
  • Deploying very large applications to multiple targets or to a cluster where deployment files are available on a shared directory.
  • Deploying exploded archive directories that you want to periodically redeploy after changing content.
  • Deployments that require dynamic update of selected Deployment Descriptors via the Administration Console.


To use nostage mode, specify -nostage as an option to weblogic.Deployer, as in:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
-password weblogic -name mydeploymentname
-targets myserver1,myserver2,myserver3 -nostage
-deploy c:\localfiles\myapp.ear

external_stage

The Administration Server does not copy deployment files. Instead, the Administrator must ensure that deployment files are distributed to the correct staging directory location before deployment (for example, by manually copying files prior to deployment).

With external_stage deployments, the Administration Server requires a copy of the deployment files for validation purposes. Copies of the deployment files that reside in target servers’ staging directories are not validated before deployment.

You can use the -noversion option to turn off the requirement that deployment files be on the Administration Server, but the -noversion option causes versioning information to be ignored; therefore, you cannot use the -noversion option with versioned applications. For information, see Common Arguments.

  • Deployments where you want to manually control the distribution of deployment files to target servers.
  • Deploying to domains where third-party applications or scripts manage the copying of deployment files to the correct staging directories.
  • Deployments that do not require dynamic update of selected Deployment Descriptors via the Administration Console (not supported in external_stage mode).
  • Deployments that do not require partial redeployment of application components.

Changing the Default Staging Behavior for a Server

The server staging mode specifies the default deployment mode for a server if none is specified at deployment time. For example, the server staging mode is used if you deploy an application or stand-alone module using weblogic.Deployer and you do not specify a staging mode.

Notes: You can only change the server staging mode by using the Administration Console or by directly changing the ServerMBean via JMX.
Note: Changing the server staging mode does not affect existing applications. If you want to change the staging mode for an existing application, you must undeploy the application deployment and then redeploy it with the new staging mode.


Source URL : http://download.oracle.com/docs/cd/E11035_01/wls100/deployment/deploy.html#wp174377

Thanks

R Vashi



One thought on “Controlling Deployment File Copying with Staging Modes in WebLogic

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s