WAS v8.5 > Administer applications and their environment > Deploy enterprise applications

Start or stop enterprise applications

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

Before beginning

This topic assumes the Java EE application is installed 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 wsadmin
• startApplication and stopApplication administrative jobs of the AdminTask.submitJob -jobType object with wsadmin
• Java programs that use ApplicationManager or AppManagement MBeans

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

This topic applies to applications that do not contain Java Application Programming Interface (API) for XML-Based Web Services (JAX-WS) or SCA service providers. To stop or start applications containing JAX-WS or SCA 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.

1. Go to the Enterprise applications page. Click Applications > Application Types > WebSphere 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 to restart, click Stop and then click Start.

Results

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

IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.

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 you want the application to start automatically when its server starts, we can adjust values that control how quickly the application or its server starts:

1. Click Applications > Application Types > WebSphere enterprise applications > application_name > Startup behavior.

2. Specify a different value for Startup order.

   This setting specifies the order in which applications are started when the server starts. Default 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 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.

4. 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
  Use this page to view mappings of deployed applications or modules to servers.
• 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
  Use this page to view mappings of deployed applications or modules to servers.

Related

Deploy enterprise applications
Install enterprise application files
Start applications using wsadmin.sh
Stopping applications using wsadmin.sh
Troubleshoot applications with HPEL

Reference

Enterprise application page
Service providers collection at the application level

+

Search Tips   |   Advanced Search