Managing application servers

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

Before you begin

[AIX Solaris HP-UX Linux Windows]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.

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: 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.

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 that 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: Before selecting this option, verify that any other WebSphere® products, that you are running in conjunction with this product, support this functionality.
  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.