Managing application servers

You can use either the administrative console or command-line tools to manage your application servers.

Before you begin

If you plan to change the system clock, stop all the application servers, the node agent servers, and the deployment manager server first. Once you stop the servers, change the system clock, and then restart the servers. If you change the system clock on one system, you must ensure the clocks on all systems that communicate with each other and have WebSphere Application Server installed are synchronized. Otherwise, you might experience issues, such as security tokens no longer being valid.

If an application server is running on an operating system when the time zone setting for the operating system is updated, the application server updates its internal time stamp. Because of a delay between the change for the time zone and the change to the application server internal time stamp, an incorrect time stamp could be posted for a file if the file is touched during this delay. Starting with Version 6 Release 1 of the operating system, the delay could be several seconds. If your application server is on an earlier version of the operating system, the delay could be as much as an hour. If the file is part of an application, this incorrect time stamp would cause the application to stop and then restart because the application server thinks that the application has been updated.

About this task

Avoid trouble Avoid trouble: If you are migrating from a previous version of the product, you can upgrade a portion of the nodes in a cell, while leaving others at the older release level. This means that, for a period of time, you might be managing servers that are running at different release levels in the same cell. In this mixed environment, there are some restrictions on what you can do with servers that are running the older release level. There are no restrictions on what you can do with the servers that are running on the newer release level.gotcha

You can perform the following steps to view and manage an application server from the administrative console.

Procedure

  1. In the administrative console click Servers > Application servers.
    The Application servers page lists the application servers in your environment and the status of each of these servers. You can use this page to:
    • Create additional servers.
    • Monitor running servers.
    • Stop a server.
    • Delete a server. When you select a server for deletion, you must click Delete and OK before the server is deleted.
      Tip: If the server you are deleting has applications or modules mapped to it and is not part of a cluster, remap the modules to another server, or create a new server and remap the modules to the new server, before deleting the old server. After a server to which modules are mapped is deleted, you cannot remap these modules to another server. Therefore, if you do not remap the modules to another server before deleting the old one, you must uninstall all of the modules that were mapped to the old server, and then reinstall them on a different server.

      If the server you are deleting is part of a cluster, any application that is installed on this server is also automatically installed on all of the other servers in the cluster. Therefore, deleting one cluster member does not affect the other cluster members, and the application remains install in the cluster. Similarly when a new member is added to an existing cluster, any applications that are installed on the servers in that cluster are automatically installed on the new cluster member.

  2. Click the name of a listed server to view or change the configuration settings for that server.
    You can use this administrative console page to:
    • Change the configuration settings for the selected server.
    • View the status of applications running on the selected server. To view the status of applications running on this server click Installed Applications under Applications.
  3. Click Review, select Synchronize changes with Nodes, and then click Save to save any configuration changes that you made.
  4. If you made any configuration or custom property changes, start the application server, or stop and restart the application server if it is already running.

Results

When you click Servers > Application servers > server_name, you should see any configuration changes you made, and when you click Servers > Application servers each server should be in the appropriate start or stop state.

What to do next

You can deploy applications or components to your application servers.



In this information ...


Related reference
Related information

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=trun_svr_manage
File name: trun_svr_manage.html