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, the deployment manager server, the administrative
agent server, and the job manager server first. After you stop the
servers, change the system clock, and then restart the servers. If
you change the system clock on one system, you must ensure the clocks
on all systems that communicate with each other and have WebSphere® Application Server installed
are synchronized. Otherwise, you might experience errors, such as
security tokens no longer being valid.
If
you plan 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 you stop the servers and location service daemon, change
the system clock, and then restart the servers and location service
daemon. If you change the system clock on one system, you must ensure
the clocks on all systems that communicate with each other and have WebSphere Application Server installed
are synchronized. Otherwise, you might experience errors, such as
security tokens no longer being valid.
You can perform the following steps to view and manage an application server from the administrative console.
When you click
, you can view the state of each server.When you click
server_name, you can view any configuration changes you made.You can deploy applications or components to your application servers.
In this information ...Subtopics
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |