Enterprise application collection
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.
From the admin console, 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 us 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:
- Saves the updated application configuration.
- Stops all of the cluster members on one node.
- Updates the application on the node by synchronizing the configuration.
- Restarts the stopped cluster members.
- Repeats steps 2 through 4 for all of the nodes that have cluster members.
- If an application is deployed with 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 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.
| 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 we deploy an application or a module such as a .jar, .war, .sar or .rar file onto a server or a cluster. |
| Uninstall | Delete 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 for updating 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. |
| Rollout Update | Sequentially update an application installed on multiple cluster members across a cluster. After updating 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:
Use Rollout Update if the application is deployed on one or more clusters spread across multiple nodes. This action reduces the amount of time any single cluster member is unavailable to serve requests to the smallest interval possible. Pending IIOP transactions will complete before a cluster member stops; in-flight HTTP and JMS transactions might be lost while the cluster member is stopping. For an application server without clusters, use Update and then save and synchronize the node instead. For a stand-alone application server, simply update and save. |
| Remove File | Delete 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 | Export an enterprise application to an EAR file at a location of our choice. Use the Export action to back up a deployed application and to preserve its binding information. |
| Export DDL | Export DDL files (Table.ddl) in the EJB modules of an enterprise application to a location of our choice. |
| Export File | Export a a file in an enterprise application or module. Examples include MANIFEST.MF, application.xml, and ibm-application-bnd. 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. 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:
|
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 our 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.
| 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.
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.
Related: