Testing the installation

  1. Start the WebSphere Administrative Server by running the startupServer script in the /opt/WebSphere/AppServer/bin directory as follows:
    # ./startupServer.sh
    
  2. If the server is slow to start or does not start successfully, look at the tracefile log in the /opt/WebSphere/AppServer/logs directory. If the trace file says server is open for e-business, the server has started.
  3. Start the administrative console by running the adminclient script in the /opt/WebSphere/AppServer/bin directory as follows:
    # ./adminclient.sh
  4. Wait until you see the console message Console Ready. Then administer the server by doing the following:
    1. When the Administrative Console opens, the Topology tree view is displayed. Click the plus sign (+) next to the WebSphere Administrative Domain entry to expand the view.
    2. Find your host name and expand the view of that node.
    3. Find the Default Server entry and expand the view.
    4. Find the default container and servletEngine entries.
    5. Select Default Server. If the Current State of the DefaultServer parameter is Stopped, click the Start icon on the tool bar. After an information window opens stating that the server is running, click OK. Note that the current state changes from Stopped to Running.

      After the server starts, the configuration database is automatically updated to ensure that the server is always running. If the server stops, or if you reboot the machine, the administrative server will automatically restart it. Even if the administrative server fails, it will continue to run.

  5. Test the server. Ensure that the IBM HTTP Web Server is running. If the IBM HTTP Web Server is not running, start the server by entering the following command in the /opt/IBMHTTPD/bin directory:
    # ./apachectl start

    Then, open a browser and go to http://localhost/servlet/snoop, which is a standard sample servlet installed by default. You should see information on /servlet/snoop.


    Snoops Servlet browser