What is Ripplestart?

This option is available in Clustered Environments. In general Cluster is consisting of logical grouping
multiple servers. What exactly RippleStart do is (while check the cluster and say Ripplestart) Restarting
the available servers in sequential manner without stopping the application requests.
Ex: if first server stops, until start the remaining servers will take care about requests of clients.
(Or)
1. Ripplestart combines stopping and starting operations. It first stops and then restarts each member of
the cluster. F(or) example, your cluster contains 3 cluster members named server_1, server_2 and
server_3. When you click Ripplestart, server_1 stops and restarts, then server_2 stops and restarts, and
finally server_3 stops and restarts.
2. Use the Ripplestart option instead of manually stopping and then starting all of the application servers
in the cluster.
Application options:
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:
1. Saves the updated application configuration.
2. Stops all of the cluster members on one node.
3. Updates the application on the node by synchronizing the configuration.
4. Restarts the stopped cluster members.
5. 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 application server without clusters, use Update and then save and synchronize the node instead.
For a standalone application server, 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
rollout 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.
ExportDDL Accesses the Export Application DDL files page, which you use to ExportDDL files (Table.ddl)
in the EJB modules of an enterprise application to a location of your choice.
ExportFile 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 File > Save as and specify a location
to save the file that is shown in the browser.