InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.1: Using the Java administrative console >
6.6.0.1.1: Starting and stopping Java administrative consoles

6.6.0.1.1: Starting and stopping Java administrative consoles

Preconditions

The WebSphere administrative server must be running before you start the Java administrative console. By default, the server does not start automatically when you start the machine.

The Java administrative console (also known as the WebSphere Administrative Console) is a Java process. As such, it must be able to locate a JDK supported by IBM WebSphere Application Server, as specified on the prerequisites Web page.

If you are operating the Java console on a machine that does not contain the WebSphere runtime and its JDK, you might need to set JAVA_HOME or other environment variables used to help Java processes find the JDK.

Also, ensure that the Java console and WebSphere administrative server with which it is communicating are using the same supported JDK (and ORB) level.

Instructions for AIX, HP-UX, Linux, and Solaris

  1. Start the administrative server, or ensure it is already running.
  2. Start the administrative console:
    1. Change directory to the bin directory under the product installation root.
      cd product_installation_root/bin
    2. Ensure that the DISPLAY variable is set in the shell from which the administrative client script will be run:
      $ export DISPLAY=localMachineName:0.0
    3. Run the administrative client script:
      ./adminclient.sh

To stop the console, use the Console -> Exit option on the console menu bar.

Instructions for Windows NT and 2000

From the Start menu, select Programs -> IBM WebSphere -> Application Server 3.5 -> Administrator's Console.

To stop the console, use the Console -> Exit option on the console menu bar.

Go to previous article: Using the Java administrative console Go to next article: Configuring new resources from the Topology tree

 

 
Go to previous article: Using the Java administrative console Go to next article: Configuring new resources from the Topology tree