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
Install your Java™ Platform, Enterprise Edition (Java EE) application 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:
- Administrative console
- startApplication and stopApplication attributes of the
AdminControl object with the wsadmin tool
- startApplication and stopApplication administrative jobs
of the AdminTask.submitJob -jobType object with the wsadmin tool
- Java programs that use ApplicationManager or AppManagement MBeans
The steps describe how to use the administrative console to start or stop an application.
避免困難: The steps apply to applications that do not contain Java Application
Programming Interface (API) for XML-Based Web Services (JAX-WS) service providers. To stop or start
applications that contain JAX-WS service providers, use the Service providers page accessed by
clicking . To start a service provider application, select a service and click
Start
Application. To stop a service provider application, select a service and click
Stop Application. Then, on the Stop application page, click
OK to stop all modules in the application, including other services such as
enterprise beans and servlets.
gotcha
Procedure
- Go to the Enterprise applications page. Click in the console navigation tree.
- Select the check box for the application you want started or stopped.
- 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 is displayed.
If an application server on which the application is deployed
synchronizes configuration with the deployment manager during server startup, then the application
might not start and a DeploymentDescriptorLoadException might be written to the server
SystemErr.log file. Stop and restart the server, and then try starting the
application again.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
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 topic.
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:
- Click .
- Specify a different value for Startup order.
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.
- Specify a different value for Launch application before server completes
startup.
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.
- 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 the changes to the application configuration.