Administrative console buttons

This page describes the button choices available on various pages of the administrative console, depending on which product features we enable.

• Select all items. Selects each resource listed on the administrative console panel, in preparation for performing an action against the selected resources.

• Deselect all items. Removes all the listed resources from each selection so that no action is performed against any of the resources.

• Show filter function. Produces a dialog box for specifying the resources to view in the table on this administrative console page.

  Hide filter function. Hides the dialog box for specifying the resources to view in the table on this administrative console page.

  When we produce the dialog box, select the column to filter and enter the filter criteria.

  Column to filter

  Select the column to filter from the drop-down list. When we apply the filter, only those items in the selected column that meet the filter criteria are displayed.

  For example, select Names to enter criteria by which to filter application server names.

  Filter criteria

  Enter a string that must be found in the name of a collection entry to qualify the entry to display in the collection table. The string can contain percent sign (%), asterisk (*), or question mark (?) symbols as wildcard characters. For example, enter *App* to find any application server whose name contains the string App.

  Prefix each of the following characters ( ) ^ * % { } \ + $ with a backslash (\) so that the regular expression engine performing the search correctly matches the search criteria. For example, to search for all Java DataBase Connectivity (JDBC) providers containing (XA) in the provider name, specify: *\(XA\)

• Clear filter value. Clears your filter changes and restores the most recently saved values.

• Abort. Stops a transaction that is not yet in the prepared state. All operations that the transaction completed are undone.

• Activate. Activates a group member.

• Add. Adds the selected or typed item to a list, or produces a dialog for adding an item to a list.

• Add Node. Displays the Add Node page, in which we specify the host name and SOAP connector port for a node that we want added to a cell.

• Apply. Saves our changes to a page without exiting the page.

• Back. Display the previous page or item in a sequence. The administrative console does not support using the Back and Forward options of a browser, which can cause intermittent problems. Use Back or Cancel on the administrative console panels instead.

• Balance. Balances active members in high availability groups across servers that host the high availability groups. The administrator must first determine which groups have active members and select those groups before selecting Balance.

• Browse. Opens a dialog that enables us to look for a file on the system.

• Calculate groups. Calculates the number of high availability groups that are returned based on the match set.

• Cancel. Exits the current page or dialog, discarding unsaved changes. The administrative console does not support using the Back and Forward options of a browser, which can cause intermittent problems. Use Cancel on the administrative console panels instead.

• Change. In the context of security, we can search the user registry for a user ID for an application to run under. In the context of container properties, we can change the data source that the container is using.

• Clear. Clears our changes and restores the most recently saved values.

• Clear selections. Clears any selected cells in the tables on this tabbed page.

• Close. Exits the dialog.

• Collapse all. Collapses all the expanded items.

• Commit. Releases all locks that are held by a prepared transaction and forces the transaction to commit.

• Copy. Creates copies of the selected application servers.

• Create. Saves our changes to all the tabbed pages in a dialog and exits the dialog.

• Create tables. Develops scheduler database tables.

• Deactivate. Deactivates a group member. The group member must be in the active state to be deactivated. The deactivate option causes the group member to move to the idle state. The group policy overrides which members are activated and deactivated for a group. The policy is enforced for every member state change. If the deactivate option conflicts with the group policy, the policy resets who is the active member of the group.

• Delete. Removes the selected instance.

• Details. Shows the details about a transaction.

• Disable.

  Group or group members:

  Disables a group or group member. When we disable a group or group member, the active group or group member is first deactivated. If the deactivate option is successful, the group or group member moves to the disable state. A disabled group or group member cannot be activated.

  Java Management Extensions (JMX) connectors:

  Disables a connector.

• Disable Auto Start. Requires you to start the application manually.

• Discard. Discards the local changes instead of saving them to the master configuration.

• Done. Saves our changes to all the tabbed pages in a dialog and exits the dialog.

• Down. oves through a list.

• Drop tables. Removes scheduler database tables.

• Dump. Activates a dump of a traced application server.

• Edit. Lets you edit the selected item in a list, or produce a dialog box for editing the item.

• Enable.

  Group or group members:

  Enable a group or a group member.

  Java Management Extensions (JMX) connectors:

  Enable a connector.

• Enable Auto Start. Starts an application automatically when the server on which the application resides starts.

• Expand all. Expands all the collapsed items.

• Export. Accesses a page for exporting EAR files for an enterprise application.

• Export DDL. Accesses a page for exporting data definition language (DDL) files for an enterprise application.

• Export Keys. Exports LTPA keys to other domains.

• Export route table. Exports the route table information for a selected cluster to a binary file in the configuration.

• Filter. Produces a dialog box for specifying the resources to view in the tables on this tabbed page.

• Finish. Forces a transaction to finish, regardless of whether its outcome has been reported to all participating applications.

• First. Display the first record in a series of records.

• Force delete. Forces the removal of a node that is not removed properly from the cell in the master repository. The Remove node action is preferred over the Force delete action to delete a node from the configuration. If we click Force delete, but the node still exists in the configuration, uninstall the node or run the removeNode command using the -force parameter on that node. Force delete action is equivalent to running the cleanupNode command at the deployment manager.

• Full resynchronize. Synchronizes the user's configuration immediately. Click full resynchronize on the Nodes page if automatic configuration synchronization is disabled, or if the synchronization interval is set to a long time, and a configuration change is made to the cell repository that needs to be replicated to that node. Clicking this option clears all synchronization optimization settings and performs configuration synchronization again, so no mismatches occur between node and cell configuration after this operation is performed. This operation can take awhile to perform.

• Generate keys. Generates new LTPA keys. When security is turned on for the first time with LTPA as the authentication mechanism, LTPA keys are automatically generated with the password entered in the panel. To generated new keys, use this option after the server is up with security turned on. Clicking this option generates the keys and propagates them to all active servers (cell, node, and application servers). The new keys can be used to encrypt and decrypt the LTPA tokens. Click Save on the console taskbar to save the new keys and the password in the repository.

• Immediate stop. Stops the server, but bypasses the normal server quiesce process that supports in-flight requests to complete before shutting down the entire server process. This shutdown mode is faster than the normal server stop processing, but some application clients can receive exceptions.

• Import keys. Imports new LTPA keys from other domains. To support single sign-on (SSO) in WebSphere Application Server across multiple WebSphere domains (cells), share LTPA keys and a password among the domains. After exporting the keys from one of the cells into a file, click this option to import the keys into all the active servers (cell, node, and application servers). The new keys can be used to encrypt and decrypt the LTPA token. Click Save on the console taskbar to save the new keys and the password in the repository.

• Install. Display the Preparing for application installation page, which you use to deploy an application, an enterprise bean, or a web component onto an application server.

• Install RAR. Opens a dialog used to install a J2EE Connector Architecture (JCA) connector and to create a resource adapter.

• Manage state. Display a list of MBeans that corresponds to the previous selection of data source or connection factory configurations. We can apply JCA lifecycle management operations to these MBeans to control the runtime status of the corresponding resources.

• Manage transactions. Display a list of active transactions running on a server. We can forcibly finish any transaction that has stopped processing because a transactional resource is not available.

• Modify. Opens a dialog used to change a specification.

• Move. oves the selected application servers to a different location in the administrative cell. When prompted, specify the target location.

• Move down. Moves downward through a list.

• Move up. Moves upward through a list.

• New. Display a page used to define a new instance. For example, clicking New on the Application Servers page displays a page on which we can configure a new application server.

• Next. Display the next page, frame, or item in a sequence.

• OK. Saves our changes to the local configuration and exits the page.

• Pause. In the context of JCA lifecycle management, stops all outbound communication that is conducted through a resource on a specified server to a backend.

• Ping. Attempts to contact selected application servers.

• Previous. Display the previous page, frame, or item in a sequence.

• Quit. Exits a dialog box and discards any unsaved changes.

• Reference shared libraries. Opens the collection of shared library references available for use by the application or module. If no references are available, a message is displayed stating that there are no references.

• Refresh. Refreshes the view of data for instances that are currently listed on this tabbed page.

• Remove. Deletes the selected item.

• Remove file. Removes the specified file from the selected application or module.

• Remove node. Deletes the selected node.

• Reset. Clears our changes on the tab or page and restores the most recently saved values.

• Restart. Stops the selected objects and starts them again.

• Restart all servers on node. Stops all application servers on the node and starts them again. The node agent for the node is also stopped and restarted.

• Resume. In the context of JCA lifecycle management, restarts the activity of a data source or a connection factory that was paused by a previous JCA lifecycle management operation.

• Retrieve new. Retrieves a new record.

• Rollout update. Sequentially updates an application installed on multiple cluster members across a cluster. After you update application files or a configuration, click Rollout update to install the configuration or the updated files for an application on all the cluster members of a cluster on which the application is installed. The Rollout update option applies the following steps to each cluster member in sequence:

  1. Saves an updated configuration.

  2. Stops the cluster member.

  3. Updates the application on the node by synchronizing the configuration.

  4. Restarts the cluster member.

  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. For a single node environment, use Update and then save and synchronize the node instead.

• Save. Saves the changes in the local configuration to the master configuration.

• Select. For resource analysis, lets we select a scope in which to monitor resources.

• Set. Saves our changes to settings in a dialog.

• Settings. Display a dialog for editing servlet-related resource settings.

• Settings in use. Display a dialog showing the settings in use.

• Show groups. Display a collection of high availability groups, based on the match set.

• Show servers. Display a collection of servers contained in the high availability groups that match the match set.

• Start. In the context of application servers, starts selected application servers. In the context of data collection, starts collecting data for the tables on this tabbed page.

• Stop. In the context of server components such as application servers, stops the selected server components. In the context of a data collection, stops collecting data for the tables on a tabbed page. In the context of nodes, stops servers on the selected nodes. In the context of deployment managers, stops the deployment manager server.

• Synchronize. Synchronizes the user configuration immediately. Click Synchronize on the Nodes page if automatic configuration synchronization is disabled, or if the synchronization interval is set to a long time, and a configuration change is made to the cell repository that needs replicating to that node. A node synchronization operation is performed using the normal synchronization optimization algorithm. This operation is fast, but might not fix problems from manual file edits that occur on the node. It is possible for the node and cell configuration to be out of synchronization after this operation is performed. If problems persist, use Full Resynchronize.

• Terminate. Deletes the Application Server process or another process that cannot be stopped by the Stop or Immediate Stop commands. Some application clients can receive exceptions. Always attempt an immediate stop before using this option.

• Test connection. After defining and save a data source, we can select this option to ensure that the parameters in the data source definition are correct. On the Collection panel, we can select multiple data sources and test them simultaneously.

• Uninstall. Deletes a deployed application from the WebSphere Application Server configuration repository. Also deletes application binary files from the file system.

• Update. For applications, replaces an application that is deployed on a server with an updated application. As part of the updating, we might need to complete steps on the Preparing for application installation and Update application pages.

  For clusters, changes the configured weight or runtime weight assigned to a cluster member.

• Update resource list. Updates the data on a table. Discovers and adds new instances to the table.

• Use cell CSI. Enables Object Management Group (OMG) Common Secure Interoperability (CSI) protocol.

• Use cell SAS. Enables IBM Secure Authentication Service (SAS).

• Use cell Security. Enables cell security.

• Verify tables. Validates the mapping between the table names, scheduler resource, and data sources.

• View. Opens a dialog on a file.

Use the administrative console