All applications

Use this page to view and manage all the applications in your environment. The applications can include both Java Platform, Enterprise Edition (Java EE) applications, and application types that run on other server types.

To view this administrative console page, click Applications > All applications.

To manage an installed middleware application, enable the Select check box in the list and click a button:

Table 1. Application buttons
Button	Resulting action
Add...	Opens a wizard that helps you deploy an application or a module, such as a `.jar`, `.zip` , `.tar`, `.ear`, `.war`, `.rar`, `tar.gz`, `tar.tgz`, or `.gzip` file to a deployment target. You can specify setup scripts to run after the application is installed, or a clean up script to run before you uninstall the application. For Liberty profile, Tomcat, JBoss, Weblogic, and Geronimo servers, you can add a representation of the application to the administrative environment. You must deploy the application outside of the administrative console.
Remove	Deletes the application or representation of the application from the configuration repository and deletes the application binaries from the file system of all nodes where the application modules are installed after the configuration is saved and synchronized with the nodes.
Submit action	Performs the action that you select for a particular application. Enable the Select check box for each middleware application on which you want to perform an action, choose an appropriate Action, and click Submit action.

Name

Specifies the name of the installed or deployed application. The application name must be unique among all the applications within a cell. You cannot specify the same name for two different applications, even if they have different application types.

Edition

Specifies the current edition of the application.

Edition State

Specifies if the application edition is active.

Type

Specifies the type of application that is deployed.

Table 2. Application types
Category	Application types	Description
Managed middleware applications	Managed middleware applications include the following types: PHP WebSphere® Application Server Community Edition	Some middleware applications, such as PHP applications, consist of an archive file and optional setup or clean up scripts. The supported archive types include: `.jar`, `.tar`, `.tgz`, `.tar.gz`, or `.zip`. The setup or cleanup scripts are run for each server on which the application is deployed. The setup script runs after the application is installed, and before the application starts. The cleanup script is called when you uninstall the application to remove any residual artifacts of the application. Actions that you can include in your scripts include setting file permissions or creating and deleting directories. WebSphere Application Server Community Edition applications consist of external deployment plans instead of setup or clean up scripts. The supported archive types include: `.car`, `.ear` , `.jar`, `.rar`, or `.war`. The external deployment plan is a WebSphere Application Server Community Edition and Apache Geronimo artifact. Define these deployment plans the same way you define the deployment plan for a standalone WebSphere Application Server Community Edition environment.
Unmanaged Java EE applications	Java EE applications that run on the following servers: Apache Tomcat BEA WebLogic Apache Geronimo Liberty profile server	The ODR can route requests to these servers, but the life cycles of unmanaged Java EE applications are not managed in any way by the autonomic managers. You can only add a representation of the application in the administrative console. You must deploy the application outside of the administrative console.
Managed Java EE applications	Java EE applications that run in WebSphere Application Server application servers, including the following application types: Any typical Java EE application	These applications are installed with the existing Java EE installation wizard.

Status

Indicates whether the application deployed on the middleware server is started, stopped, or unavailable.

Table 3. Status
Icon	Status	Description
	Started	The application is running.
	Partial Start	The application is in the process of changing from a Stopped state to a Started state. The application is starting to run but is not fully running yet. The application cannot fully start, because a server mapped to one or more application modules is stopped.
	Stopped	The application is not running.
	Partial Stop	The application is in the process of changing from a Started state to a Stopped state. The application has not stopped running yet.
	Unavailable	The status cannot be determined. An application with an unavailable status might, in fact, be running but have an unavailable status because the server running the administrative console cannot communicate with the server running the application.
	Not applicable	The application does not provide information as to whether it is running.

For other middleware applications only, the following table indicates the overall deployment status of an application only when there is a problem.

Table 4. Middleware application status
Icon	Status	Description
	Partially deployed	The application successfully deployed on at least one of the servers, but at least one server status is unknown.
	Partial deployment error	The application did not deploy successfully on at least one of the servers.
	Deployment error	The application did not deploy successfully on any of the servers.
	Unknown deployment	The status cannot be determined on any of the servers.

Action

Specifies a specific action to perform on the selected middleware application.

You can perform the following actions:

Table 5. Middleware application actions
Action	Result
Start	Starts the server on which is application is deployed.
Stop	Stops the server on which is application is deployed.

File name: middlewareapps_collection.html