This topic describes how to set up the administrative console environment,
to access the administrative console, and to log out of the administrative
console.
Before you begin
To access the administrative console, you must first install WebSphere® Application
Server and the administrative console.
About this task
You
start the administrative console, access the console through a Web browser,
and then log into the administrative console. After you finish working in
the administrative console, save your work and log out.
Procedure
- Start the desired administrative console by starting the server
process that runs the console application.
You
can start an application server or an administrative agent server.
Check the SystemOut.log file
of the server that runs the console application to verify that the console
application starts successfully. If the console application starts successfully,
you see the WSVR0221I: Application started: isclite message.
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 the console port to a new port number. Alternatively,
shut down the other application that uses the conflicting port before starting
the WebSphere Application
Server product.
- Access the administrative console.
- Enable cookies in the Web browser that you use to access the
administrative console.
- Enable JavaScript™.
Enablement
of JavaScript is
required. You must enable JavaScript so that all the features
of the administrative console are available.
- In the same Web browser, type http://your_fully_qualified_server_name:port_number/ibm/console, where your_fully_qualified_server_name is the fully
qualified host name for the machine that contains the administrative server,
and port_number is the administrative console port number. 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:port_number/ibm/console,
where your_fully_qualified_server_name is the fully qualified host
name for the machine that contains the administrative server, and port_number is
the administrative console secure port number.
The
administrative consoles for the application server and the administrative
agent use 9060 as the default port number for an unsecure administrative console
and 9043 as the default port number for a secure administrative console. Each
new administrative console that you deploy during profile creation is assigned
a new unsecure port number, and, if you enable security during profile creation,
a new secure port number. Whichever unsecure administrative console you create
first is assigned port 9060, as long as the port is available. Likewise, whichever
secure administrative console you create first is assigned port 9043, as long
as the port is available.
For a listing of supported
Web browsers, see WebSphere Application Server system requirements.
- Wait for the administrative console to load into the browser.
A login page displays after the administrative
console starts.
- Log into the administrative console.
The
administrative console can be for an application server or an administrative
agent.
- If you are logging into the administrative console for the administrative
agent, and you have registered at least one node with the administrative agent,
select the node to administer, and click Continue.
The
node can be the administrative agent node or a node for one of the application
servers registered to the administrative agent. After you select a node, the
login procedure is the same as that for the other server types, and for administrative
agents with no nodes registered.
- Enter your user name or user ID.
The user ID lasts
only for the duration of the session for which it is 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:
- Log out the other user with the same user ID. You can recover changes
made during the other user's session.
- Return to the login page and enter 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:
- Specified security user IDs and passwords
- Enabled global security
- 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, you can recover any unsaved changes the next time that you log
in under the same user ID.
Results
You have set up the administrative console environment, accessed
the administrative console, and logged out of the administrative console.
What to do next
Use the administrative console to manage the product.