The following is for experienced web masters familiar with deploying war files under a Servlet container. You will also find these in the README for version 3.0 and later.
QUICK START
If you have experience with Tomcat (or an equivalent Servlet container), then you can follow these steps to quickly install and setup Bugs Dashboard. The relevant pages from the Installation Guide are noted at each step should you need additional information.
2. [page 2.3] Open /bugs/WEB-INF/classes. If you are outside the United States, copy all files that are “_en_US” and change the copies to your language and country. You will edit your files, not the _en_US files in the following steps.
3. [page 2.3] From the classes directory, edit db_en_US.properties and change the following properties (a property is a name followed by an equal sign, e.g. name=; you will change what is on the RIGHT side of the equal sign). All property files are heavily commented so read them if you have a question about a property.
b. set the username and password properties (Oracle testing only)
c. uncomment the url which corresponds to the database in (a) and change everything in brackets to match your database.
d. save and close
4. [page 2.7] From the classes directory, edit dashboard_en_US.properties and change the following:
b. defaultAssignee (optional)
c. default priorities (i.e. P1 – P5)
d. uncomment the appropriate bugURL and set it to your system
e. save and close
5. [page 2.10] From the classes directory, edit sql_queries_en_US.properties and change the following:
b. loginName
c. save and close
6. [page 2.13] From the classes directory, edit strings_en_US.properties and set the title to your organization then save it.
7. [page 2.17] From the classes directory, edit portals_en_US.properties and change the following:
b. portal0.restrictTo
c. If you are setting up an Enterprise edition, change the following:
ii. portal1.restrictTo
d. save and close
8. [page 2.24] If you are setting up an Enterprise edition, from the classes directory, edit the projectA_portlets_en_US.properties through projectF_portlets_en_US.properties files validating the names and restrictTo values in each.
For example, in projectD_portlets_en_US.properties, you will want to change the following for both portlet groups:
b. restrictTo
c. save and close
You will then want to open the projectF_portlets_en_US.properties file and change the following:
b. restrictTo for every portlet (use global replace)
9. If you plan on using the SVNLog portlet to query your Subversion repository, from the classes directory, edit svnLog_en_US.properties and change the following:
b. all paths
c. save and close
10. If you plan on using the Links portlet, from the classes directory, edit the links_en_US.properties and change the following:
b. change all urls
c. save and close
11. [page 2.30] Move the bugs directory you created in step 1 to the /webapps directory and restart Tomcat (or the application via Tomcat Manager).
TROUBLESHOOTING
1) The View Priorities page is blank
2) Only one or two portlets show values on a page
3) All pages, including the About page, are blank.
4) If all else fails, stop Tomcat and edit the log4j.properties file in the /bugs/WEB-INF directory.
b) Change the path on line 6 to an existing directory. For example, our Ubuntu installation of Tomcat was under /opt/apache-tomcat-6.0.16. Thus, our path to the logs file is /opt/apache-tomcat-6.0.16/logs/bugs.log.
c) save and close the file
d) restart Tomcat
e) try any page
f) open the bugs.log in the logs directory and scroll to the bottom. Read back up the file until you see an error reported. If it’s something simple like “Can’t find resouce for bundle” followed by “key bugURL” then you must edit that property (i.e. it wasn’t uncommented).
g) if you are unable to determine the error or how to fix it, contact us immediately at support@bugsdashboard.com
