WebLogic 11g: Managing Deployed Applications

* Use -appversion to specify an app version to stop.
* Force stop the active version of the application:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
   -password weblogic -name mymodule -stop -adminmode

* Graceful stop an application:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
   -password weblogic -name mymodule -stop -adminmode -graceful

* To restart an application:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
   -password weblogic -name mymodule -start

* Does not delete actual files.
* Forceful undeploy:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
   -password weblogic -name mymodule -undeploy

* Graceful undeploy:

java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic
   -password weblogic -name mymodule -undeploy -graceful

* Undeploy all referencing applications first.

* Add newmodule.war to deployed myapp.ear:
– Don’t forget to update application.xml to include newmodule.war.

java weblogic.Deployer -username myname -password mypassword 
   -name myapp.ear -deploy -targets newmodule.war@myserver 
   -source /myapp/myapp.ear

* JDBC system modules
* JMS system modules
* J2EE Libraries and optional packages
* Applications and standalone modules
* Startup classes

* By setting the AppDeploymentMBean DeploymentOrder attribute in the Administration Console
* Or programmatically using the AppDeploymentMBean.
* Can NOT changed DeploymentOrder values usinig weblogic.Deployer.
* Lower DeploymentOrder values get deployed earlier.
* Same DeploymentOrder values get deployed by alphabetical order.
* DeploymentOrder defaults to 100.

* The modules contained in an Enterprise application are deployed in the order in which they are declared in the application.xml deployment descriptor.

[mv_include id=”3569″]
* Managing Deployed Applications