Why and when to perform this task
To access the administrative console, you must start it and then log in. After you finish working in the console, save your work and log out.Steps for this task
For a listing of supported Web browsers, see WebSphere Application Server detailed system requirements .
If you cannot start the administrative console because the console port conflicts with an application already running on the machine, change the port number in the
install_root/config/cells/cell_name/ nodes/node_name/servers/server_name/server.xmland install_root/config/cells/cell_name/virtualhosts.xml files. Change all occurrences of port 9090 (or whatever port was selected during installation of WebSphere Application Server) to the desired port for the console. Alternatively, shut down the other application that uses the conflicting port before starting the WebSphere Application Server product.
Note: The directory path for the server.xml file appears on two lines for printing purposes.
Changes made to server configurations are saved to the user ID. Server configurations also are saved to the user ID if there is a session timeout.
A user ID lasts for the duration of the session for which it was used to log in. If you enter an ID that is already in use (and in session), you are prompted to do one of the following:
Note that if you close the browser before saving your work, when you next log in under the same user ID, you can recover any unsaved changes.
What to do next
Note to Linux users:
If you have difficulty using the administrative console on Linux, try using the Netscape Communicator 7.1 browser based on Mozilla 1.0. The browser release is not officially supported by the WebSphere Application Server product but users have been able to access the console successfully with it.