| products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 

WebLogic Server Frequently Asked Questions

 Previous Next Contents View as PDF  

FAQs: Deployment

Q. How can I set deployment order for applications?

A. WebLogic Server 8.1 allows you to select the load order for applications. See the ApplicationMBean LoadOrder attribute in Application. WebLogic Server deploys server-level resources (first JDBC and then JMS) before deploying applications. Applications are deployed in this order: connectors, then EJBs, then Web Applications. If the application is an EAR, the individual components are loaded in the order in which they are declared in the application.xml deployment descriptor.

Q. Can I refresh static components of a deployed application without having to redeploy?

A. Yes. You can use weblogic.Deployer to specify a component and target a server, using the following syntax:

java weblogic.Deployer -adminurl http://admin:7001 -name appname -targets server1,server2 -activate jsps/*.jsp

Q. When should I use the -nostage option?

A. Set the staging mode to -nostage using weblogic.Deployer or the Administration Console if you don't want it copied anywhere and want to run it from its present location.

Q. When should I use the external_stage option?

A. Set -external_stage using weblogic.Deployer if you want to stage the application yourself, and prefer to copy it to its target by your own means.

Q. Can I generate deployment descriptor files automatically?

A. Yes, WebLogic Builder automatically generates deployment descriptor files for your J2EE applications. See WebLogic Builder Online Help.

Q. Can I set the deployment order for application components? For types of components?

A. You can change the deployment order of components within a class (making this EJB load before that EJB) using ComponentMBean DeploymentOrder attribute, but not the deployment order of different classes (making startup classes load before EJBs).

It looks like startup classes load after the J2EE deployment units, which load in this order: JDBC, JMS, Connectors, EJBs, Web Applications.

If your application is an EAR and you are using the two-phase deployment protocol, you can set the application deployment order using the ApplicationMBean LoadOrder attribute.

Q. What is the difference between the WL_HOME/config/examples/applications folder and the WL_HOME/config/examples/stage folder?

A. The applications folder is intended for applications that are not yet ready for a production environment. WebLogic Server dynamically deploys the contents of the applications folder. The stage folder (or a folder that you create for the same purpose) is for applications that are ready for deployment in a production environment. To deploy applications in the stage folder, you use the Administration Console to install the application and then browse to it.

Configuration changes you make to applications that are not in the config.xml file, but reside in the applications folder will not be persisted to config.xml. Configuration changes you make to applications that reside in the stage folder will be persisted.

Q. How do I turn the auto-deployment feature off?

A. The auto-deployment feature checks the applications folder every three seconds to determine whether there are any new applications or any changes to existing applications and then dynamically deploys these changes. The auto-deployment feature is on by default. When WebLogic Server is in production mode, this feature should be turned off.

To disable the auto-deployment feature using the console, click mydomain, click Applications and then uncheck the Auto Deployed Enabled checkbox.

To disable this feature on the command line, include the following argument:


Q. Where can I learn more about WebLogic 8.1 deployment?

A. Here: Deployment.


Back to Top Previous Next