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

Staging Mode Descriptions and Best Practices

The following table describes the behavior and best practices for using the different deployment staging modes.

Deployment Staging Mode Behavior When to Use
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.
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 WebLogic Server Administration Console.
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 WebLogic Server Administration Console (not supported in external_stage mode).
  • Deployments that do not require partial redeployment of application components.

More details here on – https://docs.oracle.com/

Deployment Staging Modes