Stopping an Application to Restrict Client Access

9 Managing Deployed Applications 9-1 9 Managing Deployed Applications The following sections describe how to perform common maintenance tasks on applications and modules that are currently deployed to a WebLogic Server domain: ■ Section 9.1, Taking a Production Application Offline ■ Section 9.2, Undeploying Shared Libraries and Packages ■ Section 9.3, Adding a New Module to a Deployed Enterprise Application ■ Section 9.4, Changing the Order of Deployment at Server Startup ■ Section 9.5, Changing the Target List for an Existing Deployment ■ Section 9.6, Removing Files from a Web Application Deployment ■ Section 9.7, Managing Long-Running Deployment Tasks ■ Section 9.8, On-demand Deployment of Internal Applications

9.1 Taking a Production Application Offline

WebLogic Server provides two different ways to take an application offline for testing or maintenance purposes: ■ Section 9.1.1, Stopping an Application to Restrict Client Access —Makes an application unavailable for processing client requests, but does not remove the deployment from the WebLogic Server domain. Stopping an application places the deployment in Administration mode, which allows you to perform internal testing using a configured Administration channel. ■ Section 9.1.2, Undeploying an Application or Module —Makes an application unavailable for processing client requests and removes WebLogic Server-generated deployment files from the domain.

9.1.1 Stopping an Application to Restrict Client Access

As described in Section 6.10, Distributing Applications to a Production Environment , distributing an application and starting it in Administration mode, restricts access to an application to a configured Administration channel. You can also stop a running application to client requests and place it in Administration mode. In a production environment, you may want to stop an application to confirm a reported problem, or to isolate the application from external client processing in order to perform scheduled maintenance. Use the -stop command to place a running application into Administration mode, as in: 9-2 Deploying Applications to Oracle WebLogic Server java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -name mymodule -stop -adminmode By default, WebLogic Server immediately stops the application, without regard to pending HTTP sessions or in-process work. If you want to wait for pending HTTP sessions to complete their work before stopping the application to client requests and placing it in Administration mode, add the -graceful option: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -name mymodule -stop -adminmode -graceful To restart an application that was previously stopped, making it available to external clients, use the -start command and specify the deployment name. You do not need to redeploy a stopped application to make it generally available: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -name mymodule -start For detailed command information, see Section A, weblogic.Deployer Command-Line Reference.

9.1.2 Undeploying an Application or Module