WAS v8.5 > Administer applications and their environment > Deploy enterprise applications > Configure enterprise application filesConfigure application startup
We can configure the startup behavior of an application. The values set affect how quickly an application starts and what occurs when an application starts.
Before beginning
This topic assumes the application or module is already deployed on a server.
This topic also assumes the application or module is configured to start automatically when the server starts. By default, an installed application starts when the server on which the application resides starts. This topic describes how to change the settings of an application or module using the dmgr console.
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.
- Click Applications > Application Types > WebSphere enterprise applications > application_name > Startup behavior in the console navigation tree.
The Startup behavior settings page is displayed.
- Specify the startup order for the application.
If the application starts automatically when its server starts, the value for Startup order on the Startup behavior settings page specifies the order in which applications are started when the server starts. The application with the lowest startup order, or starting weight, is started first. For example, specify 1 for Startup order for applications you want started first, specify 2 for applications to be started next, and so.
Best practice: For Session Initiation Protocol (SIP) applications, the <load-on-startup> tag in the sip.xml file affects the order in which applications are started. The value set for Startup order on the Startup behavior settings 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.best-practices
- Specify whether the application must initialize fully before its server is considered started.
If the application starts automatically when its server starts, Launch application before server completes startup specifies whether the application must initialize fully before its server is considered started. Background applications can be initialized on an independent thread, thus allowing the server startup to complete without waiting for the application. This setting applies only if the application is run on a v6.0 or later application server.
- Specify whether to create MBeans for resources such as servlets or JSP files within an application when the application starts.
The default for Create MBeans for resources is to create MBeans.
Results
The application or module configuration is changed. The application or stand-alone web module is restarted so the changes take effect.
What to do next
Save changes to your administrative configuration.
Subtopics
- Startup behavior settings
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.- Startup behavior settings
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.
Related
Install enterprise application files
Disable automatic starting of applications
Configure enterprise application files
Set up SIP application composition
:
Enterprise application page
Enterprise application settings