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 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.
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. Starting with Version 6 Release 1 of the operating system, the delay could be several seconds. If your application server is on an earlier version of the operating system, the delay could be as much as an hour. 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.
During the installation process, the product creates a default application server, named server1. You can use either the administrative console or command-line tools to manage this application server. However, if you create additional application servers, then you must use command-line tools to manage those other application servers.
You can perform the following steps to view and manage the default application server from the administrative console.
In this information ...Subtopics
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |