Restart enterprise applications
We can start an application that is not running (has a status of Stopped) or stop an application running (has a status of Started).
Install the Java EE application on a server. By default, the application starts automatically when the server starts.
We 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 JAX-WS service providers. To stop or start applications that contain JAX-WS service providers, use the Service providers page accessed by clicking Services > Service providers. 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
Tasks
- Go to the Enterprise applications page. Click Applications > Application Types > WebSphere enterprise applications in the console navigation tree.
- Select the check box for the application you want started or stopped.
- Click a button:
To restart a running application, select the application you want to restart, click Stop and then click Start.
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.
The status of the application changes and a message stating that the application started or stopped is displayed.
(ZOS) 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.
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the LogViewer .
What to do next
We 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 we want the application to start automatically when its server starts, we can adjust values that control how quickly the application or its server starts:
- Click Applications > Application Types > WebSphere enterprise applications > application_name > Startup behavior.
- Specify a different value for Startup order.
This setting specifies the order in which applications are started when the server starts. The default 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, we 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.
Subtopics
- Disable automatic starting of applications
We can enable and disable the automatic starting of an application. By default, an installed application starts automatically when the server on which the application resides starts.- Target specific application status
View mappings of deployed applications or modules to servers.
Deploy and administer enterprise applications Install enterprise application files Starting applications Stopping applications Administrative job types Use High Performance Extensible Logging to troubleshoot applications File synchronization service settings Enterprise application collection Service providers collection at the application level