Enterprise application collection

Enterprise application collection

+
Search Tips | Advanced Search

To manage enterprise apps...

Applications | Application Types | WebSphere enterprise apps

System applications are not shown in the list because users cannot edit them. Examples of system applications include...

isclite
managementEJB
filetransfer

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 start the application. If the app starts on all deployment targets, the state of the application changes to Started, else the state changes to Partial Start.
Stop Attempts to stop the processing of the application. If the app stops on all deployment targets, the state of the application changes to Stopped, else the state changes to Partial Stop.
Install Opens a wizard for deploying .jar, .war, .sar or .rar files.
Uninstall Deletes the application from WAS configuration repository. After synchronization, deletes the application binaries from the file system of all nodes where the application modules are installed.
Update 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 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 Delete 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, for exporting an enterprise application to an EAR file at a location of your choice. Used for backups and preserving binding information.
Export DDL Accesses the Export Application DDL files page, for exporting DDL files (Table.ddl) in the EJB modules of an enterprise application to a location of the choice.
Export File Accesses the Export a file from an application page, for exporting a file of an enterprise application or module to a location of the 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.

These buttons are not available when you access this page from an appserver settings page. When this page is accessed from an appserver settings page, it is entitled the Installed applications page.
When security is enabled, a separate application list is shown for each of the admin roles...

monitor
configurator
operator
administrator
deployer
admin 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 application. Application names must be unique within a cell and cannot contain an unsupported character.

Application Status

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

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

Subtopics
Enterprise application settings

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

Related tasks
Fine-grained admin security
Create a fine-grained admin authorization group
Deploy enterprise apps

Related
Object names: What the name string cannot contain

Button	Resulting action
Start	Attempts to start the application. If the app starts on all deployment targets, the state of the application changes to Started, else the state changes to Partial Start.
Stop	Attempts to stop the processing of the application. If the app stops on all deployment targets, the state of the application changes to Stopped, else the state changes to Partial Stop.
Install	Opens a wizard for deploying .jar, .war, .sar or .rar files.
Uninstall	Deletes the application from WAS configuration repository. After synchronization, deletes the application binaries from the file system of all nodes where the application modules are installed.
Update	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 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	Delete 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, for exporting an enterprise application to an EAR file at a location of your choice. Used for backups and preserving binding information.
Export DDL	Accesses the Export Application DDL files page, for exporting DDL files (Table.ddl) in the EJB modules of an enterprise application to a location of the choice.
Export File	Accesses the Export a file from an application page, for exporting a file of an enterprise application or module to a location of the 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.

	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.