This topic describes how to set up the administrative console environment,
to access the administrative console, and to log out of the administrative
console.
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
- Start the administrative console.
- Distributed
platforms: Verify that the
administrative console runs on the server1 application server for
the WebSphere base product. Verify that the administrative
console runs on the deployment manager for the Network Deployment product.
Use the wasadmin startManager command to
start the deployment manager.
- Enable cookies in the Web browser that you use to access the
administrative console for the administrative console to work correctly.
- Distributed
platforms: In the same Web browser, type http://your_fully_qualified_server_name:9060/ibm/console,
where your_fully_qualified_server_name is the fully qualified host
name for the machine that contains the administrative server. When the
administrative console is on the local machine, your_fully_qualified_server_name can
be localhost unless security is enabled. On Windows platforms, use
the actual host name if localhost is not recognized. If security
is enabled, your request is redirected to https://your_fully_qualified_server_name:9043/ibm/console,
where your_fully_qualified_server_name is the fully qualified host
name for the machine that contains the administrative server.
For
a listing of supported Web browsers, see
WebSphere Application Server system requirements at
http://www.ibm.com/software/webservers/
appserv/doc/latest/prereq.html
The Web address appears on two lines
for printing purposes. Enter the Web address on one line in your browser.
- Wait for the console to load into the browser. A Login page is
displayed after the console starts.
If you cannot start
the administrative console because the console port conflicts with an application
that is already running on the machine, change the port number in the installation
root/profiles/profile name/config/cells/cell_name/nodes/node_name/serverindex.xml file
and the installation root/profiles/profile name/config/cells/cell_name/virtualhosts.xml files.
Change all the occurrences of port 9060 (or the port that is selected during
profile creation for WebSphere Application Server) to the port for the console.
Alternatively, shut down the other application that uses the conflicting port
before starting the WebSphere Application Server product.
- Log into the console.
- Enter your user name or user ID.
The user ID lasts
only for the duration of the session for which it was used to log in.
Changes
made to server configurations are saved to the user ID. Server configurations also are saved to the user ID
if a session timeout occurs.
If you enter an ID that is already in use
(and in session), you are prompted to do one of the following actions:
- Force the existing user ID out of session. The configuration file that
is used by the existing user ID is saved in the temporary area.
- Wait for the existing user ID to log out or time out of the session.
- Specify a different user ID.
- If the console is secure, you must also enter a password for
the user name. The console is secure if someone has taken the following actions
for the console:
- Click OK.
- Log off the administrative console. Click System administration
> Save changes to Master Repository > Save to save work. Then click Logout
to exit the console.
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.