Starting and stopping the administrative console

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.

Why and when to perform this task

To start the console and log in, use the following procedure.

Steps for this task

  1. Start the administrative console:
    1. Enable cookies in the Web browser that you plan to use to access the administrative console.
    2. Optional: Enable JavaScript. JavaScript enablement is recommended so that all the features of the administrative console are available to you.
    3. In your cookie-enabled Web browser, type the following:

      http://your_fully_qualified_server_name:portNumber/ibm/console

      where your_fully_qualified_server_name specifies the fully qualified host name for the machine that contains the administrative server and portNumber 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:secure_portNumber/ibm/console, where your_fully_qualified_server_name is the fully qualified host name for the machine that contains the administrative server and secure_portNumber is the administrative console secure port number.

      Note: The default port number for an unsecure administrative console is port 9060, and for a secure administrative console the default port number is 9043. 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.
    4. Check the System.Out.log file of the server that runs the console application to verify that the console application has started successfully. A successful start produces the message CWWSR0221I: Application started: isclite.
      If you are unable to start the console because the console port conflicts with an application that is already running on the machine, change the port number in the following files:
      • install_root/profiles/profile_name/config/cells/cell_name/nodes/node_name/serverindex.xml
      • install_root/profiles/profile_name/config/cells/cell_name/virtualhosts.xml
      Change all occurrences of the port selected during profile creation (by default, 6090) to the port for the console. Alternatively, shut down the other application that uses the conflicting port before starting the administrative console.
    The administrative console loads in the browser, displaying a login page.
  2. Log into the console:
    1. In the User ID field, enter your user name or user ID.
      Note: If you enter an ID that is already in use (and in session) you are prompted to do one of the following:
      • Log out the other user with the same user ID. You can recover changes made during he other user's session.
      • Return to the login page and enter a different user ID.

      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.

    2. If security is enabled for the console, you must also enter a password in the Password field.
    3. Click OK.

      The administrative console now displays the Welcome page.

  3. Log off the console:
    • To save the work you have done during this session, click System administration > Save changes to master repository > Save, and then click Logout to exit the console.
    • To exit the console without saving your changes to the repository, click Logout.

    If you close the browser before saving your work, you can recover any unsaved changes the next time that you log in with the same user ID.


Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)