WAS v8.5 > Reference > SetsStartup behavior settings page
Use this page to configure when an application starts compared to other applications and to the server, and to configure whether MBeans for resources are created when an application starts.
To view this dmgr console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Startup behavior.
If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after you save the change. On multiple-server products, the application restarts after you save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.
Startup order
Order in which applications are started when the server starts. The startup order is like a starting weight. The application with the lowest starting weight is started first.
Be aware of the following limitations:
- The first application might not start completely before the application server tries to start the next application in the startup order. This scenario might cause unexpected results if the second application depends on the first application.
- For SIP applications, the <load-on-startup> tag in the sip.xml file affects the order in which servlets within applications are started. The value set for Startup order on this Startup behavior console page determines the importance or weight of an application within a composition of SIP applications. For example, for the most important SIP application within a SIP application composition, specify 1 for Startup order. For the next most important SIP application within the composition, specify 2 for Startup order, and so on. For more information, see the JSR 116 specification.
Information Value Data type Integer Default 1 Range 0 to 2147483647
Launch application before server completes startup
Whether the application must initialize fully before the server starts.
The default setting of false indicates that server startup will not complete until the application starts.
A setting of true informs the product the application might start on a background thread and thus server startup might continue without waiting for the application to start. Thus, the application might not be ready for use when the application server starts.
Information Value Data type Boolean Default false
Create MBeans for resources
Whether to create MBeans for various resources, such as servlets or JSP files, within an application when the application starts. The default is to create MBeans.
Information Value Data type Boolean Default true
Related concepts:
Enterprise (Java EE) applications
Related
Configure application startup
Configure enterprise application files
Set up SIP application composition
Reference
Enterprise application settings