Manage appservers
Overview
You can use either the console or command line tools to manage your application servers.
If you plan to change the system clock, stop all the appservers, 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 WAS installed are synchronized. Otherwise, you might experience issues, such as security tokens no longer being valid.
If you are migrating from a previous version of WAS, 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 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 appserver from the console.
Procedure
- In the console click Servers > Application servers. The Application servers page lists the appservers in your environment and the status of each of these servers. You can use this page to change the status of a listed appserver.
- Click the name of a listed appserver to view or change the configuration settings for that appserver.
- Save any configuration changes that you make.
- Start the appserver, or stop and restart the appserver if it is already running.
- Monitor running appservers.
- Stop an appserver.
- Delete an appserver.
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.
- In the console, click Servers > Application servers to access the Application Servers page.
- Select an appserver to delete.
- Click Delete.
- Click OK to confirm the deletion.
Results
Your configuration changes appear when you click Servers > Application servers > server in the 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
- You can make additional configuration changes.
- You can create additional appserver as required.
- You can deploy applications or components to your appservers.
Server collection
Environment entries collection
Start an appserver
Running an appserver from a non-root user and the node agent from root
Running an Application Server and node agent from a non-root user
Running appservers from a non-root user
Detecting and handling problems with runtime components
Stopping an appserver
Core group service settings
Setting the time zone for a single appserver
Web module or appserver stops processing requests
Related tasks
Creating appservers
Getting started with scripting
Hot deployment and dynamic reloading
Restarting an appserver in recovery mode
Considering security specific to a multi-node or process ND environment
Administering appservers
Related Reference
Application server settings
Related information
Creating clusters