Enterprise application collection

Enterprise application collection

+
Search Tips | Advanced Search

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
filetransfer

To view this console page, click...
Applications | 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, 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 beside 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 or .rar file onto a server or a cluster.
Uninstall Deletes the application from the WAS 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. 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.
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:

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.

Use Rollout Update if the application is deployed on one or more clusters spread across multiple nodes. This action reduces the amount of time that 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 appserver without clusters, use Update and then save and synchronize the node instead. For a standalone appserver, simply update and save.
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.

These buttons are not available when this page is accessed from an appserver settings page. When this page is accessed from an appserver settings page, it is entitled the Installed applications page.

Name

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

Application Status

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

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.

Unavailable Status cannot be determined.

Not applicable Application does not provide information as to whether it is running.

The status of an application on a Web server is always Unavailable.

Startup order

Specify 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 appserver settings page; thus when this page is entitled the Installed applications page.

Sub-topics

Enterprise application settings

Related concepts
Enterprise (J2EE) applications System applications

Related tasks
Deploying and administering J2EE applications

Related Reference

Object names: What the name string cannot contain

Reference topic

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 or .rar file onto a server or a cluster.
Uninstall	Deletes the application from the WAS 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. 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.
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: 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. Use Rollout Update if the application is deployed on one or more clusters spread across multiple nodes. This action reduces the amount of time that 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 appserver without clusters, use Update and then save and synchronize the node instead. For a standalone appserver, simply update and save.
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.

	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.
	Unavailable	Status cannot be determined.
	Not applicable	Application does not provide information as to whether it is running.