4-6 Programming Deployment for Oracle WebLogic Server
configured to run on it. See the Section 4.3.3, Application Start
section for more detail on module level control.
The WebLogicDeploymentManager extends undeploy in support of removing files from a distribution. This is a form of in-place redeployment that is only supported in
Web applications, and is intended to allow you to remove static pages. See Section 4.4.4, Version Support
.
4.4 Production Redeployment
Standard redeployment support only applies to entire applications and employs side-by-side versioning to ensure uninterrupted session management. The
WebLogicDeploymentManager extends the redeploy method and provides the following additional support:
■
Section 4.4.1, In-Place Redeployment :
■
Section 4.4.2, Module Level Targeting
■
Section 4.4.3, Retirement Policy
■
Section 4.4.4, Version Support
■
Section 4.4.5, Administration Test Mode
4.4.1 In-Place Redeployment
The in-place redeployment strategy works by immediately replacing a running applications deployment files with updated deployment files, such as:
■
Partial redeployment which involves adding or replacing specific files in an existing deployment.
■
Updating a configuration using a redeployment of a deployment plan
4.4.2 Module Level Targeting
A DeploymentManager implements the JSR-88 specification and restricts operations to root modules. Module level control is provided by manually constructing a module
specific TargetModuleID hierarchy using WebLogicDeploymentManager.createTargetModuleID
4.4.3 Retirement Policy
When a new version of an application is redeployed, the old version should eventually be retired and undeployed. There are 2 policies for retiring old versions of
applications:
1.
Default The old version is retired when new version is active and old version finishes its in-flight operations.
2.
The old version is retired when new version is active, retiring the old after some specified time limit of the new version being active.
Note: The old version is not retired if the new version is in administration
test mode.
Performing Deployment Operations 4-7
4.4.4 Version Support
Side-by-side versioning is used to provide retirement extensions, as suggested in the JSR-88 redeployment specification. This ensures that an application can be redeployed
without interruption in service to its current clients. Details on deploying side-by-side versions can be found in Redeploying Applications in a Production Environment in
Deploying Applications to Oracle WebLogic Server.
4.4.5 Administration Test Mode
A Web application may be started in normal or administration test mode. Normal mode indicates the Web application is fully accessible to clients. Administration test
mode indicates the application only listens for requests using the admin channel. Administration test mode is specified by the DeploymentOptions argument on the
WebLogic Server extensions for start, deploy and redeploy. See DeploymentOptions Javadoc.
4.5 Progress Reporting
