Testing the installation

  1. Start the WebSphere Administrative Server by running the startupServer script in the /opt/WebSphere/AppServer/bin directory: ./startupServer.sh
  2. Wait patiently. If the server is slow to start or does not start successfully, look at the tracefile log: tail -f opt/logs/tracefile

    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: ./adminclient.sh
  4. Wait until you see the console message Console Ready. Then administer the server:
    1. When the Administrative Console opens, the Topology tree view is shown. Click on the + sign next to WebSphere Administrative Domain to expand the view.
    2. Your host name should be listed. Expand the view of that node, and you should see an entry called Default Server. Expand that and you will see the default container and servletEngine.
    3. Select Default Server. If the Current State of DefaultServer is Stopped, click the Start icon on the tool bar. After an information dialog displays, stating that the server is running, click OK. Note that the current state changes from Stopped to Running.

      Once the server starts, it is marked in the configuration database that it should be running. If it 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 Server is running. If the IBM HTTP Server is not running, start the server by entering the following in the /opt/HTTPServer/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