How To Install Under Ubuntu 7.10 – Method 1

The following are steps we take in deploying the Bugs Dashboard to a test platform running Ubuntu 7.10. Under this method, we do not use the Tomcat Manager to deploy; we'll look at that in another post.

Prerequisites

  • Tomcat has been successfully installed (see Installing Tomcat 6 on Ubuntu at the How-to Geek)
  • MySQL (see the Ubuntu Guide) or PostgreSQL (see the Ubuntu Guide and supriyadisw dot net) have been successfully installed
  • Bugzilla has been successfully installed in one of the above databases and can be reached via a JDBC connection from the Tomcat server

Steps

  1. Download the latest Developer or Enterprise version of Bugs Dashboard and either a) save it to disk or b) open it with the Archive Manager and then Extract the contents. We chose to save the zip file to the desktop.
  2. If you did not use the Archive Manager in step 1, navigate to the downloaded file, right-mouse click on the file and select Extract Here.
    Extract zip screen shot
  3. Extracting the file locally will result in a new directory named "bugs".
    Bugs directory screen shot
  4. Open the bugs directory. Inside, you will find the README (read it, please!), the documentation (under the docs directory), the license, and the bugs.war file.
    Bugs directory screen shot.
  5. Right mouse cick on the bug.war file and choose Extract Here.
    Extracting the war file screen shot.
  6. This will create another 'bugs' directory and this is the directory you will deploy.
    Bugs directory screen shot.
  7. Open the bugs directory. In it are the css, images, javascript and WEB-INF directories. Much of the modification which you must do to configure the Bugs Dashboard will be done in the WEB-INF directory.
    The Bugs directory screen shot.
  8. Follow the steps at the Quick Start post or the How-to Configure pages to configure your copy of the Bugs Dashboard.
  9. When your configuration is complete, move the second bugs directory (the one we stated you would deploy above) with the WEB-INF directory in it to the Tomcat webapps directory. In our case, this was under /opt/apache-tomcat-6.0.16/webapps.
  10. In our testing, we found that it was not necessary to bounce the Tomcat server for the Bugs Dashboard to deploy. Open a browser and navigate to your local installation (this might be http://localhost or your domain name, in our case, it was http://localhost:8080/bugs/portal) and open the portal page (it will open to the first portal in the portals_en_US.properties file). If, for any reason, the page does not come right up, review the troubleshooting tips in the Quick Start guide.
  11. Should you need to change your configuration, it may be necessary to stop and restart (i.e. bounce) Tomcat. You can do this by opening a terminal window, switching to root (sudo -s) and navigating to the Tomcat bin directory. Execute the shutdown script (./shutdown.sh), make any necessary changes, and then execute the startup script (./startup.sh).


Leave a Comment

Spam Protection by WP-SpamFree