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 the application server first. After you stop the server, change the system clock, and then restart the server. If you change the system clock on one system, you must ensure the clocks on all systems that communicate with each other, and have the product installed, are synchronized. Otherwise, you might experience errors, 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. The delay could be several seconds. 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

During the installation process, the product creates a default application server, named server1. If you create any additional application servers, you cannot start, stop, or manage these servers using the administrative console that is associated with the original base server. You must either use command-line tools to perform these tasks for the additional servers, set up an administrative console for each server, or configure an administrative agent to provide a single interface to all of your servers, including the original base server.

Avoid trouble Avoid trouble: If you create additional application servers, only use one server to modify and save configurations. There is no coordination of configuration setting between the different servers and if you modify and save configurations on multiple servers, your data might become corrupted.gotcha

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

Procedure

  1. In the administrative console click Servers > Server Types > WebSphere 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 monitor the default server.

  2. Click server1 to view or change the configuration settings for the default server.

    For example, if you do not need to have all of the sever components start during the server startup process, you might want to select Start components as needed, which is not selected when a new server is created. When this property is selected, server components are dynamically started as they are needed. Therefore, selecting this option can improve server startup time, and reduce the memory footprint of the server.

    Avoid trouble Avoid trouble: Before selecting this option, verify that any other WebSphere® products, that you are running in conjunction with this product, support this functionality.gotcha
  3. Click Review, select Synchronize changes with Nodes.
  4. Click Save to save any configuration changes that you made.

Results

When you click Servers > Server Types > WebSphere application servers, you can view the state of each server.

When you click Servers > Server Types > WebSphere application servers > server_name , you can view any configuration changes you made.

What to do next

You can deploy applications or components to your application servers.




In this 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 of Use | Feedback

Last updatedLast updated: Sep 19, 2011 7:16:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=trun_svr_manage
File name: trun_svr_manage.html