Changes for page Getting Started with BugTracker

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,7 +1,9 @@
1	1	**Getting Started with BugTracker**
2	2
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:
	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	+
5	5	[[image:Context-023.jpg]]
6	6	[[image:Context-024.jpg]]
7	7	[[image:Context-025.jpg]]
...	...	@@ -32,24 +32,11 @@
32	32
33	33	----
34	34
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]]
	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.
36	36
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		-~-~--
	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]]
51	51
52		-Here are the settings I used for FrontBase:
	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:
53	53
54	54	#ERXConfigurationManager properties moved in from Properties.ak
55	55	#Original Settings for Postgresql
...	...	@@ -62,6 +62,12 @@
62	62	dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
63	63	er.javamail.adminEmail=foo@localhost.com//
64	64
	54	+You can see the Properties file that you are editing in the following screenshot:
	55	+
	56	+[[image:Context-036.jpg]]
	57	+
	58	+----
	59	+
65	65	Make sure that the build path contains the plugin for your database;
66	66
67	67	[[image:Context-030.jpg]]