Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 16.1
edited by Kieran Kelleher
on 2007/10/31 16:14
Change comment: Added MySQL config info and note on missing ec delegate property
To version 18.1
edited by David Holt
on 2007/06/20 19:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.dholt
Content
... ... @@ -1,11 +1,7 @@
1 1  **Getting Started with BugTracker**
2 2  
3 -~1. Import the source code folders needed for BugTracker either [[from local Wonder source tree>>http://wiki.objectstyle.org/confluence/display/WONDER/Working+with+Wonder+source+in+Eclipse]] or from Wonder CVS server as discussed below.
3 +#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:
4 4  
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.
6 -
7 -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.
8 -
9 9  [[image:Context-023.jpg]]
10 10  [[image:Context-024.jpg]]
11 11  [[image:Context-025.jpg]]
... ... @@ -12,78 +12,60 @@
12 12  
13 13  ----
14 14  
15 -2. Check out the folders into their own projects in your workspace.
11 +#Check out the folders into their own projects in your workspace.
16 16  
17 17  [[image:Context-026.jpg]]
18 18  
19 19  ----
20 20  
21 -3. Your workspace should look roughly like this once it has completed rebuilding:
17 +#Your workspace should look roughly like this once it has completed rebuilding:
22 22  
23 23  [[image:Context-027.jpg]]
24 24  
25 25  ----
26 26  
27 -4. First order of business is to find your Properties file by turning off the filter that is on by default:
23 +#First order of business is to find your Properties file by turning off the filter that is on by default:
28 28  
29 29  [[image:Context-028.jpg]]
30 30  
31 31  ----
32 32  
33 -5. Uncheck the item selected in the image below:
29 +#Uncheck the item selected in the image below:
34 34  
35 35  [[image:Context-029.jpg]]
36 36  
37 37  ----
38 38  
39 -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. Alternatively (a recommended way) you can create your own "Properties.username" file by duplicating "Properties.ak"
35 +#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>>http://webobjects.mdimension.com/wonder/api/er/extensions/ERXConfigurationManager.html]]
40 40  
41 -{{warning title="Missing Properties"}}
37 +~-~--
38 +Changing the connection dictionary
39 +To do this for Oracle you can either specify on a per model basis or on a global basis.
40 + Global:
41 + dbConnectServerGLOBAL = myDatabaseServer
42 + dbConnectUserGLOBAL = me
43 + dbConnectPasswordGLOBAL = secret
44 + dbConnectPluginGLOBAL = Oracle
45 + Per Model for say model ER:
46 + ER.DBServer = myDatabaseServer
47 + ER.DBUser = me
48 + ER.DBPassword = secret
49 + ER.DBPlugin = Oracle
50 +~-~--
42 42  
43 -The current Wonder source (Oct 31,2007) requires the addition of this property to he Properties file in BugTracker to run properly (Can someone commit this please?)
52 +Here are the settings I used for FrontBase:
44 44  
45 -er.extensions.ERXRaiseOnMissingEditingContextDelegate=false
46 -
47 -{{/warning}}
48 -
49 -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]]
50 -
51 -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:
52 -
53 -ERXConfigurationManager properties moved in from Properties.ak
54 -Original Settings for Postgresql
55 -Changed to Frontbase
54 +#ERXConfigurationManager properties moved in from Properties.ak
55 +#Original Settings for Postgresql
56 +#Changed to Frontbase
56 56  dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
57 57  dbConnectUserGLOBAL=//system
58 58  dbConnectPluginGLOBAL=Frontbase
59 -dbConnectDriverGLOBAL=org.postgresql.Driver
60 -dbConnectPasswordGLOBAL =
60 +#dbConnectDriverGLOBAL=org.postgresql.Driver
61 +#dbConnectPasswordGLOBAL =
61 61  dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
62 62  er.javamail.adminEmail=foo@localhost.com//
63 63  
64 -You can see the Properties file that you are editing in the following screenshot:
65 -
66 -[[image:Context-036.jpg]]
67 -
68 -{{info title="MySQL Configuration for BugTracker"}}
69 -
70 -* Create a database named "bug" in your MySQL development database
71 -* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
72 -* Add the following properties to the Properties file in BugTracker using the user and password from the previous step
73 -
74 -dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capializeTypenames=true
75 -dbConnectUserGLOBAL=user
76 -dbConnectPasswordGLOBAL=password
77 -dbConnectPluginGLOBAL=
78 -dbConnectDriverGLOBAL=
79 -dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
80 -er.javamail.adminEmail=foobar@domain.com
81 -
82 -
83 -{{/info}}
84 -
85 -----
86 -
87 87  Make sure that the build path contains the plugin for your database;
88 88  
89 89  [[image:Context-030.jpg]]
... ... @@ -90,7 +90,7 @@
90 90  
91 91  ----
92 92  
93 -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.
71 +#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.
94 94  
95 95  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.
96 96  
... ... @@ -98,19 +98,19 @@
98 98  
99 99  ----
100 100  
101 -8. We do that by selecting Run as > Run...
79 +#We do that by selecting Run as > Run...
102 102  
103 103  [[image:Context-032.jpg]]
104 104  
105 105  ----
106 106  
107 -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.
85 +#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.
108 108  
109 109  [[image:Context-033.jpg]]
110 110  
111 111  ----
112 112  
113 -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.
91 +#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.
114 114  
115 115  Now select BugTracker as your launch configuration to start the application:
116 116  
... ... @@ -118,10 +118,10 @@
118 118  
119 119  ----
120 120  
121 -~11. You should see a login screen. Your default administrative user is "admin" with password "admin"
99 +#You should see a login screen. Your default administrative user is "admin" with password "admin"
122 122  
123 123  [[image:Context-035.jpg]]
124 124  
125 125  ----
126 126  
127 -12. Explore
105 +#Explore!!