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.
Before you begin
The administrative console runs in a Web browser, and requires the
use of cookies. Before starting the console, ensure that your Web browser
is configured to enable cookies.
Before starting the administrative console,
ensure that the WebSphere ESB server
process is running. For a stand-alone server profile, that one server must
be running. For a deployment manager cell, the deployment manager must be
running. For more information about starting the WebSphere ESB server
process, see Starting or stopping the WebSphere ESB server.
Why and when to perform this task
You can start the administrative console in a variety of ways,
including from the Windows Start menu and from the First steps console.
Perform
the following steps to start and stop the console:
Steps for this task
- Start the administrative console and connect it to the deployment
manager or stand-alone server:
Option |
Description |
Use the Windows Start programs menu |
Select
the program where profile_name is
the name of the profile; for example, default for a stand-alone
profile created by the Complete installation procedure, or Dmgr01 for a deployment
manager profile. |
Use the First steps console |
- Start the First steps
console
- Click Administrative console
|
Use the console address |
- Start a Web browser
- Type the console address, of the form: http://server_name:port/ibm/console
Where server_name is the name of the deployment manager
or stand-alone server. You might need to use the fully-qualified name. On
Windows, if the server is on the local machine, you can use localhost unless
security is enabled. |
The administrative console loads in the browser, displaying a
login page.
- Log into the console:
- In the User ID field, type your user
ID.
Note: If you enter a user ID that is being used
in an existing console session, you are prompted to take one of the following
choices:
- Force the existing user out of the session. The configuration file for
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.
The user ID lasts only for the duration of the session for
which it was used to log in. Any changes made to server configurations are
saved to the user ID. Server configurations are also saved to the user ID
if a session times out.
- If the console uses global security, you must also enter a password
in the Password field.
- Click OK.
The administrative console now displays the Welcome page.
What to do next
Now, you can use the administrative console to work with
WebSphere ESB;
for example, to list the runtime state of servers, and to change the configuration
of message reliability for service requests.
If you want to stop using the
console, then complete the following steps:
- Save any changes to the master configuration. In the navigation pane,
click to
save all work you have done during this session.
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.
- To exit the console, click Logout at the top of
the console window.
- If you do not need the browser for other reasons,
you can close the browser window.