You 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 you begin
This topic assumes that your application or module is already deployed on a server.
This topic also assumes that your 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.
About this task
This topic describes how to change the settings of an application or module using the
administrative console.
Attention: 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.
Procedure
-
Click in the console navigation tree.
The Startup behavior settings page is displayed.
-
Specify the startup order for the application.
If your 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 that you want started first, specify 2
for
applications to be started next, and so.
Best practices: 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 that you 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.
-
Specify whether the application must initialize fully before its server is considered
started.
If your 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.
-
Specify whether to create MBeans for resources such as servlets or JavaServer Pages (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
If the application or module is deployed on a cluster and you have no more
configuration changes to make, click Rollout Update on the Enterprise
applications page to propagate the changed configuration on all cluster members of the cluster on
which the application or module is deployed. Rollout Update sequentially
updates the configuration on the nodes that contain cluster members.
Save changes to your administrative configuration.
The application binaries are transferred to nodes when the configuration changes
on the deployment manager synchronize with configurations for individual nodes on which the
application will run.