Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 12.1
edited by David Holt
on 2008/09/11 19:47
Change comment: There is no comment for this version
To version 17.1
edited by David Holt
on 2007/06/20 19:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,23 +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 -{{info title="Alternate method for getting started with BugTracker"}}
6 -
7 -If you're just exploring BugTracker, you may prefer to use the method outlined on [this page|Getting Started with BugTracker Alternate method] that depends on installed Wonder frameworks instead of importing the Wonder source into your workspace.
8 -
9 -{{/info}}
10 -
11 -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.
12 -
13 -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.
14 -
15 -{{warning title="Missing Projects from the screenshots below"}}
16 -
17 -BugTracker has new dependencies on DerbyPlugin and ERChronic since these screenshots were taken. Make sure to import them into your workspace as well.
18 -
19 -{{/warning}}
20 -
21 21  [[image:Context-023.jpg]]
22 22  [[image:Context-024.jpg]]
23 23  [[image:Context-025.jpg]]
... ... @@ -24,81 +24,60 @@
24 24  
25 25  ----
26 26  
27 -2. Check out the folders into their own projects in your workspace.
11 +#Check out the folders into their own projects in your workspace.
28 28  
29 29  [[image:Context-026.jpg]]
30 30  
31 31  ----
32 32  
33 -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:
34 34  
35 35  [[image:Context-027.jpg]]
36 36  
37 37  ----
38 38  
39 -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:
40 40  
41 41  [[image:Context-028.jpg]]
42 42  
43 43  ----
44 44  
45 -5. Uncheck the item selected in the image below:
29 +#Uncheck the item selected in the image below:
46 46  
47 47  [[image:Context-029.jpg]]
48 48  
49 49  ----
50 50  
51 -{{id value="Configuration"}}{{/id}}
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]]
52 52  
53 -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"
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 +~-~--
54 54  
55 -{{info title="Update: Sept 11, 2008 How to enable properties for databases other than Derby (FrontBase,PostgreSQL)"}}
52 +Here are the settings I used for FrontBase:
56 56  
57 -* 3 Default Global database properties files are now included with BugTracker. Please see Properties.Derby,Properties.FrontBase,Properties.PostgreSQL
58 -* In the 3 launch configurations (discussed below in point 7) user.name=Derby is now set by default.
59 -* You can swap out Derby for your favourite database (i.e. user.name=FrontBase or user.name=PostgreSQL) in all 3 launch configurations if you want to use your database properties instead of the default Derby
60 -
61 -
62 -{{/info}}
63 -
64 -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]]
65 -
66 -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:
67 -
68 -ERXConfigurationManager properties moved in from Properties.ak
69 -Original Settings for Postgresql
70 -Changed to Frontbase
54 +#ERXConfigurationManager properties moved in from Properties.ak
55 +#Original Settings for Postgresql
56 +#Changed to Frontbase
71 71  dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
72 72  dbConnectUserGLOBAL=//system
73 73  dbConnectPluginGLOBAL=Frontbase
74 -dbConnectDriverGLOBAL=org.postgresql.Driver
75 -dbConnectPasswordGLOBAL =
60 +#dbConnectDriverGLOBAL=org.postgresql.Driver
61 +#dbConnectPasswordGLOBAL =
76 76  dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
77 77  er.javamail.adminEmail=foo@localhost.com//
78 78  
79 -You can see the Properties file that you are editing in the following screenshot:
80 -
81 -[[image:Context-036.jpg]]
82 -
83 -{{info title="MySQL Configuration for BugTracker"}}
84 -
85 -* Create a database named "bug" in your MySQL development database
86 -* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
87 -* Add the following properties to the Properties file in BugTracker using the user and password from the previous step
88 -
89 -dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
90 -dbConnectUserGLOBAL=user
91 -dbConnectPasswordGLOBAL=password
92 -dbConnectPluginGLOBAL=
93 -dbConnectDriverGLOBAL=
94 -dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
95 -er.javamail.adminEmail=foobar@domain.com
96 -
97 -
98 -{{/info}}
99 -
100 -----
101 -
102 102  Make sure that the build path contains the plugin for your database;
103 103  
104 104  [[image:Context-030.jpg]]
... ... @@ -105,7 +105,7 @@
105 105  
106 106  ----
107 107  
108 -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.
109 109  
110 110  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.
111 111  
... ... @@ -113,19 +113,19 @@
113 113  
114 114  ----
115 115  
116 -8. We do that by selecting Run as > Run...
79 +#We do that by selecting Run as > Run...
117 117  
118 118  [[image:Context-032.jpg]]
119 119  
120 120  ----
121 121  
122 -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.
123 123  
124 124  [[image:Context-033.jpg]]
125 125  
126 126  ----
127 127  
128 -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.
129 129  
130 130  Now select BugTracker as your launch configuration to start the application:
131 131  
... ... @@ -133,10 +133,10 @@
133 133  
134 134  ----
135 135  
136 -~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"
137 137  
138 138  [[image:Context-035.jpg]]
139 139  
140 140  ----
141 141  
142 -12. Explore
105 +#Explore!!