Operating Systems: i5/OS
             Personalize the table of contents and search results

 

Manage application servers

 

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

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

 

Overview

If you are migrating from a previous version of WebSphere Application Server, 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.

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 change the status of a listed application server.

  2. Click the name of a listed application server to view or change the configuration settings for that application server.

  3. Save any configuration changes that you make.

  4. Start the application server, or stop and restart the application server if it is already running.

  5. Monitor running application servers.

  6. Stop an application server.

  7. Delete an application server.

    If the server you are deleting has applications or modules mapped to it, 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, uninstall all of the modules that were mapped to the old server, and then reinstall them on a different server.

    1. In the administrative console, click Servers > Application servers to access the Application Servers page.

    2. Select an application server to delete.

    3. Click Delete.

    4. Click OK to confirm the deletion.

 

Results

Your configuration changes appear when you click Servers > Application servers > server_name in the administrative console. You can also click Servers > Application servers to verify that each server is in the appropriate start or stop state.

 

What to do next




}
Server collection

Environment entries collection

Starting an application server

Running application servers under specific user profiles

Detecting and handling problems with runtime components

Stopping an application server

Core group service settings

Setting the time zone for a single application server

Changing the ports associated with an application server

Web module or application server stops processing requests

 

Related tasks


Creating application servers
Getting started with scripting
Hot deployment and dynamic reloading
Restarting an application server in recovery mode
Considering security specific to a multi-node or process Network Deployment environment
Administering application servers

 

Related Reference

Application server settings

 

Related information


Creating clusters