Enterprise application collection
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 administrative console page, click
.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, you 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 for the application name in the list and click a button:
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. When an application is uninstalled, any existing application analysis report generated for the application is deleted and not recoverable even if a configuration save is not performed. |
Update | Opens a wizard that helps you update application files deployed on a server. You 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. When a full application update is performed, the application analysis report is deleted and not recoverable even if a configuration save is not performed. |
Rollout Update | Sequentially updates an application installed on multiple cluster members
across a cluster. After you update an application's files or configuration, click Rollout
Update to install the application's updated files or configuration on all cluster
members of a cluster on which the application is installed. Rollout Update
does the following for each cluster member in sequence:
|
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. If the application or module is deployed on a cluster, after removing a file click Rollout Update to roll out the changes across the entire cluster. |
Export | Accesses the Export Application EAR files page, which you 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 you 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 you 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 and specify a location to save the file that is shown in the browser.Avoid trouble: You 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:
|
Analyze | Provides migration report options:
|
These buttons are not available when you 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 you have the administrator role, the statement
You can administer the following resources
is shown followed by a list of applications that
you can administer.
Name
Specifies the 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.
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. | |
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.
Liberty Report
Indicates the state of the application analysis scan. Upon successful completion, a Report link is available to navigate to the detailed results of the scan. The detailed results provide the information about how to migrate the application to the Liberty server.
Icon | Scan Status | Description |
---|---|---|
Unavailable | No scan is available for the application. | |
Scan submitted | The scan was submitted. | |
Done | The scan completed and found no issues. | |
Recommendations | The number of recommendations found in the application during the scan. | |
Warnings | The number of warnings found in the application during the scan. | |
Severe issues | The number of severe issues found in the application during the scan. | |
Scan error | An error occurred during the scan. Details are available in server logs. |
Startup order
Specifies the 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.