Application change deployment in production mode of Weblogic

Application change deployment in production mode of Weblogic

Scenario overview

The next AdminSever in production mode allows WebLogic to manage multiple managedsevers. When deploying an application for the first time, you can select multiple managedservers for Synchronous deployment. However, there is a bug in the update function of the WebLogic console interface when you make an application change. In a production environment, you must ensure that at least one application server is running. If you use the WebLogic console to delete an application under a node (such as default) and redeploy default, duplicate application names will occur, and the Application name involves changes to the external directory, therefore, this solution cannot be used.

 

 

Solution:

1: Stop the application process of the backup Managed Application Server

Eg: DOMAIN_HOME/bin/stopManagedWebLogic. sh BPMRTServer01 t3: // ip: port $

2: manually copy the new application (default. war) to the stage directory of the ManagedServer.

Eg: cp default. war DOMAIN_HOME/servers/ManagedServer01/stage/default
3: restart the application

Eg: DOMAIN_HOME/bin/startManagedWebLogic. sh BPMRTServer01 t3: // ip: port

This change can solve the above problems, and automate the deployment of change scripts to simplify operations.

Manage managed servers by configuring Node Manager in WebLogic 12c

WebLogic reset Administrator account and password

Install and configure Weblogic 10 in CentOS 6.3

Oracle WebLogic 11g installation and deployment documentation PDF

Deploying Weblogic11g in Linux

Oracle basic tutorial-installing and configuring a single Weblogic instance

Uninstall Weblogic in Linux

Configuration of Weblogic multi-machine Cluster

Weblogic installation and configuration