How to Redeploy an Application Without Interrupting Service to Existing Clients
Last updated on DECEMBER 19, 2017
Applies to:Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2017***
Sometimes in a production environment, it is necessary to redeploy a new version of an application without interrupting service to existing clients. That is, while redeployment is taking place, one version of the application is "active," while the other version is "retiring." The active application version receives all new client connection requests for the application, while the retiring application version processes only those client connections that already existed when redeployment took place.This is commonly referred to as a "hot" or "rolling" redeployment.
This procedure is covered comprehensively by the documentation. This article is not intended to replace that documentation, only to supplement it by providing simple instructions on how to accomplish this.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms