Starting or stopping J2EE applications

You can start an application that is not running (has a status of Stopped) or stop an application that is running (has a status of Started).

Before you begin

This topic assumes that the J2EE application is installed on a server. By default, the application starts automatically when the server starts.

About this task

You can start and stop applications manually using the following:

This topic describes how to use the administrative console to start or stop an application.

Procedure

  1. Go to the Enterprise Applications page. Click Applications > Enterprise Applications in the console navigation tree.
  2. Select the check box for the application you want started or stopped.
  3. Click a button:
    Option Description
    Start Runs the application and changes the state of the application to Started. The status is changed to partially started if not all servers on which the application is deployed are running.
    Stop Stops the processing of the application and changes the state of the application to Stopped.
    To restart a running application, select the application you want to restart, click Stop and then click Start.

Results

The status of the application changes and a message stating that the application started or stopped displays at the top the page.

What to do next

You can configure an application so it does not start automatically when the server on which it resides starts. You then start the application manually using options described in this article.
If you want your application to start automatically when its server starts, you can adjust values that control how quickly the application or its server starts:
  1. Go the settings page for your enterprise application. Click Applications > Enterprise Applications > application_name.
  2. Specify a different value for Starting weight.

    This setting specifies the order in which applications are started when the server starts. The default value is 1 in a range from 0 to 2147483647. The application with the lowest starting weight is started first.

  3. Specify a different value for Background application.

    This setting specifies whether the application must initialize fully before its server starts. The default value of false prevents the server from starting completely until the application starts. To reduce the amount of time it takes to start the server, you can set the value to true and have the application start on a background thread, thus allowing server startup to continue without waiting for the application

  4. 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.
  5. Save the changes to the application configuration.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=trun_app_startstop
File name: trun_app_startstop.html