Changes for page Getting Started with BugTracker
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
on 2007/07/17 10:04
Change comment:
There is no comment for this version
To version 17.1
edited by David Holt
on 2007/06/20 19:12
on 2007/06/20 19:12
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.d frolov1 +XWiki.dholt - Content
-
... ... @@ -1,11 +1,7 @@ 1 1 **Getting Started with BugTracker** 2 2 3 - ~1.Import the source code foldersneededforBugTrackereither[[from local Wonder sourcetree>>http://wiki.objectstyle.org/confluence/display/WONDER/Working+with+Wonder+source+in+Eclipse]] orfromWonderCVSserverasdiscussed 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,35 +12,48 @@ 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 theProperties located in the resources folder to match the requirements for your database.WonderapplicationsneedPropertiesfilestomanage their configurationcorrectly. Thereare anumberof different placesintheWonderframeworkshatapplicationpropertieswill be readfrom.In theoriginalexample,the Databaseconnection propertiesaretaken froma loggedin user's properties file,in this caseit is named "Properties.ak".I movedtherelevant lineso the ApplicationPropertiesfile that described the Global connectiondictionary for BugTrackertoaccessmy FrontBase database. Alternatively (a recommended way) you canreate 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 -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 databaseconnection 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]] ... ... @@ -65,7 +65,7 @@ 65 65 66 66 ---- 67 67 68 - 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. 69 69 70 70 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. 71 71 ... ... @@ -73,19 +73,19 @@ 73 73 74 74 ---- 75 75 76 - 8.We do that by selecting Run as > Run...79 +#We do that by selecting Run as > Run... 77 77 78 78 [[image:Context-032.jpg]] 79 79 80 80 ---- 81 81 82 - 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. 83 83 84 84 [[image:Context-033.jpg]] 85 85 86 86 ---- 87 87 88 - 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. 89 89 90 90 Now select BugTracker as your launch configuration to start the application: 91 91 ... ... @@ -93,10 +93,10 @@ 93 93 94 94 ---- 95 95 96 - ~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" 97 97 98 98 [[image:Context-035.jpg]] 99 99 100 100 ---- 101 101 102 - 12.Explore!!105 +#Explore!!