Getting Started with BugTracker

Version 20.1 by David Holt on 2007/06/20 19:17

Getting Started with BugTracker

1. Import the following source code folders from CVS according to the tutorial. You may need to adjust the exact folders you import depending on the database you plan to use. In this case, I have added the FrontBase plugin as well as all the other frameworks that BugTracker expects to find in its build path:

Context-023.jpg
Context-024.jpg
Context-025.jpg


2. Check out the folders into their own projects in your workspace.

Context-026.jpg


3. Your workspace should look roughly like this once it has completed rebuilding:

Context-027.jpg


4. First order of business is to find your Properties file by turning off the filter that is on by default:

Context-028.jpg


5. Uncheck the item selected in the image below:

Context-029.jpg


6. Change the properties located in the resources folder to match the requirements for your database. I use Frontbase. You can either set Global properties for your database, or by model as per the instructions in ERXConfigurationManager documentation

---
Changing the connection dictionary
To do this for Oracle you can either specify on a per model basis or on a global basis.
 Global:
      dbConnectServerGLOBAL = myDatabaseServer
      dbConnectUserGLOBAL = me
      dbConnectPasswordGLOBAL = secret
      dbConnectPluginGLOBAL = Oracle
 Per Model for say model ER:
      ER.DBServer = myDatabaseServer
      ER.DBUser = me
      ER.DBPassword = secret
      ER.DBPlugin = Oracle
---

Here are the settings I used for FrontBase:

#ERXConfigurationManager properties moved in from Properties.ak
#Original Settings for Postgresql
#Changed to Frontbase
dbConnectURLGLOBAL=jdbc:frontbase://localhost/bug
dbConnectUserGLOBAL=system
dbConnectPluginGLOBAL=Frontbase
#dbConnectDriverGLOBAL=org.postgresql.Driver
#dbConnectPasswordGLOBAL =
dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
er.javamail.adminEmail=foo@localhost.com

Make sure that the build path contains the plugin for your database;

Context-030.jpg


7. Now we want to run the app. The Wonder team has set it up so that you can generate all necessary tables and populate them when you launch the BugTracker application for the first time using a special launch configuration.

You'll see BugTracker launch configurations for creating, creating without dropping, and normal launching. We need to select the BugTracker (create without drop) launch configuration for the initial setup.

Context-031.jpg


8. We do that by selecting Run as > Run...

Context-032.jpg


9. In the resulting dialog box, select BugTracker (create without drop). If you try to use (create) you'll get a bunch of errors complaining about lack of tables in the database.

Context-033.jpg


10. You'll see a long list of things being done in your console window that takes several minutes. When you get the final Done message, your database is set up and ready to go. You can log into your database to confirm that the tables have been magically created and populated.

Now select BugTracker as your launch configuration to start the application:

Context-034.jpg


11. You should see a login screen. Your default administrative user is "admin" with password "admin"

Context-035.jpg


12. Explore!!