InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.3a: Starting, stopping, and logging into the Web administrative console

6.6.0.3a: Starting, stopping, and logging into the Web administrative console

Starting the console

To start the Web administrative console:

  1. Ensure that the Web server is running on the machine containing the console.
  2. Ensure that the application server is also running.
  3. In a Web browser, type:
    http://your.server.name:9090/admin
    where your.server.name is localhost if the Web console is on the local machine. On Windows 2000, it has been found that localhost is not always recognized. In such a case, use the actual host name.

    If the console is on a remote machine, enter the short or fully qualified host name for the machine containing the administrative server.

  4. Wait for the console to load into the browser.

Logging into the console

A Login screen is displayed whenever you open the console.

  1. Enter your user ID. (See below for some notes).
  2. If you have done the following, then the console has been secured, meaning you must enter a password:

    1. Specified security user IDs and passwords
    2. Enabled global security
  3. Click Submit.
Notes about the user ID for logging in

Even if you have not secured the console, you will be prompted for an ID. The server configuration file will be saved under the user ID if there is a session timeout. If you do not specify an ID, a default username called "User" will be assigned to the session.

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 will be prompted to do one of the following:

  • Force the existing user ID out of session. The configuration file that was being used by the existing user ID will be saved in the temp area. See the session timeout description for further details.
  • Wait for the existing user ID to log out or timeout of the session.
  • Specify a different user ID.

Logging out

When you are logged in, a Logout option is available in the menu on the Web console home page.

  1. Select Logout from the menu.
  2. If you already saved your changes, you are logged out right away. Otherwise, if you need to save your changes, the Logout panel is displayed.
  3. Save your changes to the same file that you were editing or save it to another file.

  4. Click OK to log out.

Stopping the console

To stop the console, simply close the browser.

Notes to Linux users

If you have difficulty using the Web-based administrative console on Linux with a Netscape browser, one of the following workarounds could help:

  • If the tree on the left side of the console is not being displayed, configure Netscape preferences to Enable Java and Enable JavaScript using these steps:
    1. Start your Netscape browser
    2. Select Edit > Preferences
    3. Select Advanced, and then select the Enable Java and Enable JavaScript check boxes
    4. Click OK
    5. Start the administrative console from the URL:
      http://your_machine_name:9090/admin
  • Try the Blackdown 1.2.2 JDK plug-in for Linux
  • Use a Web browser on a different operating system or machine to access the Linux machine remotely
  • Try Mozilla with the JDK 1.3 plug-in on Linux

Specifically, problems have been encountered on SuSe 6.4 and SuSe 7.1 using Netscape Communicator Version 4.72 and 4.76. (Other Linux systems are susceptible, as testing suggests that the problem is partially or wholly attributable to the JDK plug-in of the Web browser.)

Symptom generally experienced: When you start the console, the left frame freezes while loading, with the message "View no script tree" at the top. Enabling Java and JavaScript via the steps listed previously should display the entire console properly.

Go to previous article: Working with server configuration files, using the Web administrative console Go to next article: Overview of editing property files by hand

 

 
Go to previous article: Working with server configuration files, using the Web administrative console Go to next article: Overview of editing property files by hand