Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Tutorial/3.7/Minicrm/Set up SQL Service"
m (Clean up tag soup) |
(Support for other database products) |
||
Line 2: | Line 2: | ||
We want to connect to a database. In Scout terms, the client might want to fill a table with data from the database. It calls a service on the server to provide some table data. That service in turn has to get the data from somewhere. In this case, it sends a SQL statement to a yet another service, the '''SQL service'''. This service will handle connecting to the database and the rest. | We want to connect to a database. In Scout terms, the client might want to fill a table with data from the database. It calls a service on the server to provide some table data. That service in turn has to get the data from somewhere. In this case, it sends a SQL statement to a yet another service, the '''SQL service'''. This service will handle connecting to the database and the rest. | ||
+ | |||
+ | Eclipse Scout comes with support for [http://db.apache.org/derby/ Apache Derby], [http://www.postgresql.org/ PostgreSQL], and [http://www.oracle.com/de/products/database/index.html Oracle] out of the box. Switching to other solutions like [http://www.hibernate.org/ Hibernate] possible, but is beyond the scope of the tutorial. (Essentially you'll need to use Hibernate beans instead of the FormData objects Eclipse Scout provides for you to communicate between client and server.) | ||
== Create a new AbstractDerbySqlService == | == Create a new AbstractDerbySqlService == |
Revision as of 05:57, 8 October 2010
We want to connect to a database. In Scout terms, the client might want to fill a table with data from the database. It calls a service on the server to provide some table data. That service in turn has to get the data from somewhere. In this case, it sends a SQL statement to a yet another service, the SQL service. This service will handle connecting to the database and the rest.
Eclipse Scout comes with support for Apache Derby, PostgreSQL, and Oracle out of the box. Switching to other solutions like Hibernate possible, but is beyond the scope of the tutorial. (Essentially you'll need to use Hibernate beans instead of the FormData objects Eclipse Scout provides for you to communicate between client and server.)
Create a new AbstractDerbySqlService
Go to the server node and open the tree, drill down until Sql Services below Common Services and right click in order to open the wizard to create a new SQL service.
Name your new service DerbySqlService and choose AbstractDerbySqlService from the combobox Super Type then click finish.
If the Super Type AbstractDerbySqlService doesn't appear within the combobox, you need to organize your server project's plugin.xml. Go to the Java Perspective, double click on the server project, open the plugin.xml and in the box Required Plug-Ins add the plug-in org.eclipse.scout.rt.jdbc.derby. If the Super Type still does not appear, make sure that the derby.jar is in the lib folder of the Java installation. You can get this library directly from Apache Derby.
Change default configuration settings
Adjust the default settings in your DerbySqlService by editing the Jdbc Mapping Name, this should point to the folder where you unzipped the DerbyDb to. As username/password use minicrm/minicrm.