Manage application servers
Use either the administrative console or command-line tools to manage the application servers.
To change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, and the job manager server first. After stopping the servers, change the system clock, and then restart the servers. If we 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, we might experience errors, such as security tokens no longer being valid.
(ZOS) To change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, the job manager server, and the location service daemon first. After stopping the servers and location service daemon, change the system clock, and then restart the servers and location service daemon. If we 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, we might experience errors, such as security tokens no longer being valid.
(iSeries) 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.
For transitioning users: If we are migrating from a previous version of the product, we can upgrade a portion of the nodes in a cell, while leaving others at the previous release level. This means that, for a period of time, we might be managing servers running at different release levels in the same cell. In this mixed environment, some restrictions exist for what we can do with servers running at a previous release level. No restrictions exist for what we can do with the servers running on the newest release level.trns
Manage an application server from the administrative console
- From the admin console, click...
Servers > Server Types > WebSphere application servers
The Application servers page lists the application servers in the environment and the status of each of these servers. Complete the following actions:
- Create additional servers.
- Monitor running servers.
- Control the status of a server.
- Create a server template
- Delete a server.
If the server we are deleting has mapped applications/modules, and the server is not part of a cluster with two or more cluster members, before deleting either remap the modules to another server or delete the applications/modules. Clusters with two or more members automatically install the application on all of the other servers in the cluster. If we did not remap the modules to another server before deleting, uninstall all of the modules that were mapped to this server.
- Click appserver to...
- Change the configuration settings for the selected server.
For example, select Start components as needed. When is selected, server components are dynamically started as needed.
- View the status of applications running on the selected server
Applications > Installed Applications
- Click Custom properties to add new custom properties, update existing custom properties, or modify the timer settings if the current settings are causing timeout problems.
- Click Review, select Synchronize changes with Nodes.
- Click Save to save any configuration changes that we made.
- If we made any configuration or custom property changes, start the application server, or stop and restart the application server if it is already running.
When we click Servers > Server Types > WebSphere application servers, we can view the state of each server.
When we click Servers > Server Types > WebSphere application servers > server, we can view any configuration changes we made.
What to do next
We can deploy applications or components to the application servers.
Subtopics
- Create application servers
- Server collection
- Application server settings
- Create clusters
- Prepare to host applications
- Stop an application server
- Java SDK collection
- Ports collection
- Ports settings
- Custom property collection
- Custom property settings
- Environment entries collection
- Environment entries settings
- Native processes
- Server component collection
- Server component settings
- Thread pool collection
- Thread pool settings
- Server instance settings
- Core group service settings
- Update resources for an application server
- Starting an application server
- Directory conventions
- Restarting an application server in recovery mode
- Problems with runtime components
- Reject work requests when no servant is available
- Converting a 7-character server short name to 8 characters
- Changing time zone settings
- Web module or application server stops processing requests
- Setting a time limit for the completion of RMI/IIOP enterprise bean requests
- Single network interface
- UCS Transformation Format
- wsadmin scripting
- Hot deployment and dynamic reloading
- Restarting an application server in recovery mode
- Security considerations when in a multi-node WAS WAS ND environment
iSeries
- (iSeries) Run application servers under specific user profiles
- (iSeries) Changing the ports associated with an application server
ZOS