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 article assumes that the application is installed on a server. By default, the application starts automatically when the server starts.Why and when to perform this task
You can start and stop applications manually using the following:This article describes how to use the administrative console to start or stop an application.
Steps for this task
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. |
Result
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.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.
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
Related tasks
Deploying and administering applications