Enterprise application collection

WAS v8.5 > Reference > Sets
Enterprise application page

Use this page to view and manage enterprise applications.
This page lists installed enterprise applications. System applications, which are central to the product, are not shown in the list because users cannot edit them. Examples of system applications include isclite, managementEJB and filetransfer.
To view this dmgr console page, click...
Applications > Application Types > WebSphere enterprise applications

To view the values specified for an application's configuration, click the application name in the list. The displayed application settings page shows the values specified. On the settings page, we can change existing configuration values and link to additional console pages that assist you in configuring the application.
To manage an installed enterprise application, enable the Select check box beside the application name in the list and click a button:
Button descriptions. Use the buttons to manage enterprise applications.

Button Resulting action
Start Attempts to run the application. After the application starts up successfully, the state of the application changes to Started if the application starts up on all deployment targets, else the state changes to Partial Start.
Stop Attempts to stop the processing of the application. After the application stops successfully, the state of the application changes to Stopped if the application stops on all deployment targets, else the state changes to Partial Stop.
Install Opens a wizard that helps you deploy an application or a module such as a .jar, .war, .sar or .rar file onto a server or a cluster.
Uninstall Deletes the application from the product 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.
Update Opens a wizard that helps you update application files deployed on a server. We can update the full application, a single module, a single file, or part of the application. If a new file or module has the same relative path as a file or module already existing on the server, the new file or module replaces the existing file or module. If the new file or module does not exist on the server, it is added to the deployed application.
Remove File Deletes a file of the deployed application or module. Remove File deletes a file from the configuration repository and from the file system of all nodes where the file is installed.
Export Accesses the Export Application EAR files page, which we use to export an enterprise application to an EAR file at a location of your choice. Use the Export action to back up a deployed application and to preserve its binding information.
Export DDL Accesses the Export Application DDL files page, which we use to export DDL files (Table.ddl) in the EJB modules of an enterprise application to a location of your choice.
Export File Accesses the Export a file from an application page, which we use to export a file of an enterprise application or module to a location of your choice.
If the browser does not prompt for a location to store the file, click File > Save as and specify a location to save the file that is shown in the browser.
We can use the com.ibm.websphere.management.application.client.EnvEntry_processBindings JVM custom property to specify how an environment entry value is handled during an application deployment. However:

If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a pre-v8.0 environment, the environment entry value in the XML bindings are not recognized by both the deployment and runtime environments.
If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a v8.0 or 8.0.0.1 environment, the environment entry value in XML bindings are not be recognized by the deployment environment but are recognized by the runtime environment.

These buttons are not available when we access this page from an application server settings page. When this page is accessed from an application server settings page, it is entitled the Installed applications page.
When security is enabled, a separate application list is shown for each of your administrative roles. Supported roles include monitor, configurator, operator, administrator, deployer, and administrative security manager. For example, when we have the administrator role, the statement "We can administer the following resources" is shown followed by a list of applications that we can administer.

Name

Name of the installed (or deployed) application. Application names must be unique within a cell and cannot contain an unsupported character.

Application Status

Indicates whether the application deployed on the application server is started, stopped, or unknown.
Application status. The status indicates whether the application is running.

Icon Application status Description
Started Application is running.
Partial Start Application is in the process of changing from a Stopped state to a Started state. Application is starting to run but is not fully running yet. Or, it cannot fully start because a server mapped to one or more application modules is stopped.
Stopped Application is not running.
Partial Stop Application is in the process of changing from a Started state to a Stopped state. Application has not stopped running yet.
Unknown Status cannot be determined.
An application with an unknown status might, in fact, be running but have an unknown status because the server running the dmgr console cannot communicate with the server running the application.
Pending Status is temporarily unknown pending an event that a user did not initiate, such as pending an asynchronous call.
Not applicable Application does not provide information as to whether it is running.

The status of an application on a web server is always Unknown.

Startup order

Order in which applications are started when the server starts. The application with the lowest startup order is started first.
This table column is available only when this page is accessed from an application server settings page; thus when this page is entitled the Installed applications page.

Subtopics

Enterprise application settings
Use this page to configure an enterprise application.

Related concepts:

Enterprise (Java EE) applications
System applications
Administrative roles and naming service authorization

Related

Fine-grained administrative security
Create a fine-grained administrative authorization group
Deploy enterprise applications

Reference:

Object names: What the name string cannot contain
Enterprise application settings

+
Search Tips | Advanced Search

Button	Resulting action
Start	Attempts to run the application. After the application starts up successfully, the state of the application changes to Started if the application starts up on all deployment targets, else the state changes to Partial Start.
Stop	Attempts to stop the processing of the application. After the application stops successfully, the state of the application changes to Stopped if the application stops on all deployment targets, else the state changes to Partial Stop.
Install	Opens a wizard that helps you deploy an application or a module such as a .jar, .war, .sar or .rar file onto a server or a cluster.
Uninstall	Deletes the application from the product 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.
Update	Opens a wizard that helps you update application files deployed on a server. We can update the full application, a single module, a single file, or part of the application. If a new file or module has the same relative path as a file or module already existing on the server, the new file or module replaces the existing file or module. If the new file or module does not exist on the server, it is added to the deployed application.
Remove File	Deletes a file of the deployed application or module. Remove File deletes a file from the configuration repository and from the file system of all nodes where the file is installed.
Export	Accesses the Export Application EAR files page, which we use to export an enterprise application to an EAR file at a location of your choice. Use the Export action to back up a deployed application and to preserve its binding information.
Export DDL	Accesses the Export Application DDL files page, which we use to export DDL files (Table.ddl) in the EJB modules of an enterprise application to a location of your choice.
Export File	Accesses the Export a file from an application page, which we use to export a file of an enterprise application or module to a location of your choice. If the browser does not prompt for a location to store the file, click File > Save as and specify a location to save the file that is shown in the browser. We can use the com.ibm.websphere.management.application.client.EnvEntry_processBindings JVM custom property to specify how an environment entry value is handled during an application deployment. However: If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a pre-v8.0 environment, the environment entry value in the XML bindings are not recognized by both the deployment and runtime environments. If an application is deployed with com.ibm.websphere.management.application.client.EnvEntry_processBindings enabled and is then exported to be deployed on a v8.0 or 8.0.0.1 environment, the environment entry value in XML bindings are not be recognized by the deployment environment but are recognized by the runtime environment.

Icon	Application status	Description
	Started	Application is running.
	Partial Start	Application is in the process of changing from a Stopped state to a Started state. Application is starting to run but is not fully running yet. Or, it cannot fully start because a server mapped to one or more application modules is stopped.
	Stopped	Application is not running.
	Partial Stop	Application is in the process of changing from a Started state to a Stopped state. Application has not stopped running yet.
	Unknown	Status cannot be determined. An application with an unknown status might, in fact, be running but have an unknown status because the server running the dmgr console cannot communicate with the server running the application.
	Pending	Status is temporarily unknown pending an event that a user did not initiate, such as pending an asynchronous call.
	Not applicable	Application does not provide information as to whether it is running.