How to change deployment order in WebLogic?

Question

According to this documentation, you can change the deployment order in WebLogic: http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/deployment/ChangeTheServerDeploymentOrder.html

For example, I have two web applications app1.war and app2.ear .
I set the Deployment Order to 1 for app1.war.
And "Deployment Order" 100 for app2.ear. Does this mean that app1.war will be up and running before WebLogic starts up the app2.ear application?

Unfortunately, this does not work for me. WebLogic starts to run app1.war, but then starts to run app2.ear when app1.war is not yet included in STATE_ACTIVE.

Answer 1

I think it will begin and then complete the launch in accordance with this order. I tested on my server

It performs the following sequence.

One thread goes through all the applications in deployment order and translates them all to PREPARED, then to ADMIN, then to ACTIVE

In my example below, dms.war set to 50, and portletapp set to 100 as the deployment order.

Thread 0 works to make everything ready and admin

Thread 1 starts to make them ACTIVE

 ####<04-Feb-2011 17:02:05 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296819125939> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server DefaultServer.> ####<04-Feb-2011 17:02:19 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296819139834> <BEA-149060> <Module portletapp of application wsrp-samples [Version=11.1.1.2.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server DefaultServer.> ####<04-Feb-2011 17:03:25 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296819205627> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server DefaultServer.> ####<04-Feb-2011 17:03:33 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296819213183> <BEA-149060> <Module portletapp of application wsrp-samples [Version=11.1.1.2.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server DefaultServer.> ####<04-Feb-2011 17:04:57 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <00e884cc3b492be0:-20717040:12df0741b5b:-8000-0000000000000006> <1296819297757> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server DefaultServer.> ####<04-Feb-2011 17:04:57 > <Info> <Deployer> <DefaultServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <00e884cc3b492be0:-20717040:12df0741b5b:-8000-0000000000000006> <1296819297767> <BEA-149060> <Module portletapp of application wsrp-samples [Version=11.1.1.2.0] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server DefaultServer.> 

Answer 2

In your example, thread 1 puts two applications, " dms.war " and "portletapp" in ACTIVE at the same time. If the second application really depends on the first application, the second application will fail. Maybe in your testing, it happens that there is no such dependence?

Answer 3

If you have not already done so, in the Change Center of the Administration Console, click "Block" and "Change" (see Using the Change Center). In the left pane of the Administration Console, select "Deployments". The right pane displays all the modules configured for deployment in the domain, listed in their current deployment order.

In the right pane, click the name of the module for which you want to change the deployment order. On the Overview tab that appears, enter a new value in the Deployment Order box and click Save to apply the changes. To change the deployment order of the Startup class, follow the instructions in the Configure Startup Classes section.

To activate these changes, in the Change Center of the Administration Console, click "Activate Changes". Not all changes take effect immediately - some require a reboot (see Using the Change Center).