InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.1: Administering applications (overview) >
6.6.1.3: Administering applications with the Web console >
6.6.1.3.2: Starting, stopping, and restarting applications with the Web console

6.6.1.3.2: Starting, stopping, and restarting applications with the Web console

During this task, you will manage applications or individual modules within applications. To start, stop, or restart an application or its modules:

  1. Click Nodes -> hostname -> Enterprise Applications to display the applications that are installed in the current server configuration.

    Each application is in one of the following states, as indicated by a graphic next to each application name:

    • Running - at least one of the modules in the application is running
    • Stopped - all of the modules in the application are stopped
    • Cannot be run - the server must be stopped and started again with the current configuration before further management operations can be performed on the application (see below for discussion)
    • Unknown - the administrative application cannot determine the current application state (see below for discussion)

    (If the server is stopped, then all of the applications or modules will be in the state in which they cannot be run. Start the server before proceeding.)

  2. Select the check boxes next to one or more applications or modules in the list.
  3. Click the button corresponding to the action that you want to perform on the selected applications or modules:
    • Start
    • Stop
    • Restart (stop and start again)

    Starting or stopping an application or module also sets the execution state to match. The execution state determines the initial state of the application the next time the server is started with the current configuration.

A "please wait" page will be displayed until all of actions (starting, stopping, or restarting) against the selected applications again, and the console message area will contain a message that the operation has been completed. If there was a problem, the message area will display an error message instead.

Details and troubleshooting

This remainder of this article discusses the behavior of applications or modules in various states as you try to start, stop, or restart them. It includes guidelines for recognizing and correcting error situations.

Handling of simultaneous requests

The administrative application will serialize simultaneous requests issued by users engaged in separate administration sessions. One administrator might perceive a delay while another administrator's command is completing.

Possible causes that an application cannot be managed, or has an unknown state

An application or module can be in an unknown state if:

  • The trace service diagnostic port is set to -1
  • The trace service is disabled for the server in which the applications are installed
  • The administrative application encounters an error when querying the status of the application
  • The administrative application is unable to connect to the server at all

You might not be able to manage an application if:

  • The trace diagnostic port for the server is configured, but the administrative application cannot connect to the specified port
  • The application or module being managed is not defined in the configuration of the running server. This can happen if the server is not stopped and started again after installing a new application.
Go to previous article: Mapping roles to users with the Web console Go to next article: Uninstalling applications with the Web console

 

 
Go to previous article: Mapping roles to users with the Web console Go to next article: Uninstalling applications with the Web console