Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 13.1
edited by Denis Frolov
on 2007/07/17 10:04
Change comment: There is no comment for this version
To version 20.1
edited by David Holt
on 2007/06/20 19:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfrolov
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 +~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:
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]]
... ... @@ -36,11 +36,24 @@
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 +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>>http://webobjects.mdimension.com/wonder/api/er/extensions/ERXConfigurationManager.html]]
40 40  
41 -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]]
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 -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 +Here are the settings I used for FrontBase:
44 44  
45 45  #ERXConfigurationManager properties moved in from Properties.ak
46 46  #Original Settings for Postgresql
... ... @@ -53,12 +53,6 @@
53 53  dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
54 54  er.javamail.adminEmail=foo@localhost.com//
55 55  
56 -You can see the Properties file that you are editing in the following screenshot:
57 -
58 -[[image:Context-036.jpg]]
59 -
60 -----
61 -
62 62  Make sure that the build path contains the plugin for your database;
63 63  
64 64  [[image:Context-030.jpg]]