Wiki source code of Getting Started with BugTracker
Version 27.1 by David Holt on 2007/06/20 20:07
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
11.1 | 1 | **Getting Started with BugTracker** |
| 2 | |||
| |
27.1 | 3 | ~1. Import the following source code folders from CVS according to the [[tutorial>>http://wiki.objectstyle.org/confluence/display/WOL/Project+Wonder+woa+with+Linked+Source]]. 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. |
| |
11.1 | 4 | |
| |
27.1 | 5 | The next three screenshots are showing the folders that can be found on the CVS server for Wonder. I have split them up because all the folders don't fit on the screen at once! As you can see, the folders that are necessary are found in several different sub-folders. |
| |
11.1 | 6 | |
| |
25.1 | 7 | [[image:Context-023.jpg]] |
| 8 | [[image:Context-024.jpg]] | ||
| 9 | [[image:Context-025.jpg]] | ||
| 10 | |||
| |
11.1 | 11 | ---- |
| 12 | |||
| |
25.1 | 13 | 2. Check out the folders into their own projects in your workspace. |
| |
11.1 | 14 | |
| |
25.1 | 15 | [[image:Context-026.jpg]] |
| 16 | |||
| 17 | ---- | ||
| 18 | |||
| 19 | 3. Your workspace should look roughly like this once it has completed rebuilding: | ||
| 20 | |||
| |
11.1 | 21 | [[image:Context-027.jpg]] |
| 22 | |||
| 23 | ---- | ||
| 24 | |||
| |
25.1 | 25 | 4. First order of business is to find your Properties file by turning off the filter that is on by default: |
| 26 | |||
| 27 | [[image:Context-028.jpg]] | ||
| 28 | |||
| 29 | ---- | ||
| 30 | |||
| 31 | 5. Uncheck the item selected in the image below: | ||
| 32 | |||
| 33 | [[image:Context-029.jpg]] | ||
| 34 | |||
| 35 | ---- | ||
| 36 | |||
| |
27.1 | 37 | 6. Change the Properties located in the resources folder to match the requirements for your database. Wonder applications need Properties files to manage their configuration correctly. There are a number of different places in the Wonder frameworks that application properties will be read from. In the original example, the Database connection properties are taken from a logged in user's properties file, in this case it is named "Properties.ak". I moved the relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database. |
| |
11.1 | 38 | |
| |
25.1 | 39 | You can either set Global properties for your database, or you can set them for a specific model. See the Wonder docs for more information about Properties files and database configuration [[ERXConfigurationManager documentation>>http://webobjects.mdimension.com/wonder/api/er/extensions/ERXConfigurationManager.html]] |
| 40 | |||
| 41 | Here are the Global database connection settings I used for FrontBase. If you are using a different setup, you may want to ask on the mailing list for guidance: | ||
| 42 | |||
| |
27.1 | 43 | #ERXConfigurationManager properties moved in from Properties.ak |
| 44 | #Original Settings for Postgresql | ||
| 45 | #Changed to Frontbase | ||
| |
25.1 | 46 | dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug |
| 47 | dbConnectUserGLOBAL=//system | ||
| 48 | dbConnectPluginGLOBAL=Frontbase | ||
| |
27.1 | 49 | #dbConnectDriverGLOBAL=org.postgresql.Driver |
| 50 | #dbConnectPasswordGLOBAL = | ||
| |
25.1 | 51 | dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes |
| 52 | er.javamail.adminEmail=foo@localhost.com// | ||
| 53 | |||
| 54 | You can see the Properties file that you are editing in the following screenshot: | ||
| 55 | |||
| |
23.1 | 56 | [[image:Context-036.jpg]] |
| |
11.1 | 57 | |
| 58 | ---- | ||
| 59 | |||
| |
25.1 | 60 | Make sure that the build path contains the plugin for your database; |
| |
11.1 | 61 | |
| 62 | [[image:Context-030.jpg]] | ||
| 63 | |||
| 64 | ---- | ||
| 65 | |||
| |
25.1 | 66 | 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. |
| |
11.1 | 67 | |
| 68 | 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. | ||
| 69 | |||
| 70 | [[image:Context-031.jpg]] | ||
| 71 | |||
| 72 | ---- | ||
| 73 | |||
| |
25.1 | 74 | 8. We do that by selecting Run as > Run... |
| |
11.1 | 75 | |
| 76 | [[image:Context-032.jpg]] | ||
| 77 | |||
| 78 | ---- | ||
| 79 | |||
| |
25.1 | 80 | 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. |
| |
11.1 | 81 | |
| 82 | [[image:Context-033.jpg]] | ||
| 83 | |||
| 84 | ---- | ||
| 85 | |||
| |
25.1 | 86 | 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. |
| |
11.1 | 87 | |
| 88 | Now select BugTracker as your launch configuration to start the application: | ||
| 89 | |||
| 90 | [[image:Context-034.jpg]] | ||
| 91 | |||
| 92 | ---- | ||
| 93 | |||
| |
25.1 | 94 | ~11. You should see a login screen. Your default administrative user is "admin" with password "admin" |
| |
11.1 | 95 | |
| 96 | [[image:Context-035.jpg]] | ||
| 97 | |||
| 98 | ---- | ||
| 99 | |||
| |
27.1 | 100 | 12. Explore!! |