First screen of the dialog
REFERENCE:
Database import |
The Import Database dialog enables you to specify a database and select tables whose structure you want to model in a Together project. (For more information on the feature, see User's Guide: Import/Export Operations).
|
|
|
First screen of the dialog |
In the "Server type" option choose your database server type. Only supported types are displayed.
The "JDBC driver" label is read-only, and is used only in informational purposes to let you know the driver being used.
Read-only field specifies the location and name of the target database. Values displayed depending on settings in the following fields where you must specify several parameters which are used to compose the URL and, later, to connect to the database.
A string of a form "jdbc:<subprotocol>:" where <subprotocol> is the name of the driver or the name of a database connectivity mechanism. For example, "odbc", "oracle:thin" etc.
The database identifier. This varies with the database driver used, but it generally provides a logical name that is mapped by the database administration software to a physical directory where the database tables are located. For your database identifier to have any meaning, you must register the name using your database administration software. (The process of registration varies from platform to platform.)
If you're connecting across a network, these are used to identify the remote machine (they are disabled for MS Access).
Initialized to the server's defaults. Specify appropriate values for both fields. Leave blank for MS Access databases that do not require a log-in.
When you have filled the required parameters you can press Next. Then Together will attempt to connect to the specified database.
If connect succeeds, an option "Schema" appears along with a set of tables belonging to the selected schema. (A schema is a logical set of tables. Usually, it is thought of as simply "the database", but some databases can hold more than one schema. For example, a star schema can be a set of tables where one large, central table holds all of the important information, and is linked, via foreign keys, to dimension tables which hold detail information, and can be used in a join to create detailed reports).
|
|
|
Select schemas and table(s) for import |
Note that since MS Access doesn't support schemes, the "Schema" option is not be shown for MS Access. You should select nonempty set of tables for import.
Press Next button to continue.
The last page allow you to choose a diagram structure. Select the desired diagram format using the Import to option:
|
|
If selected, relationships in the RDB are mapped to associations between supplier Bean class and client Remote interface. Identifying relationship is presented by two associations:
client Remote interface is associated by both the supplier Bean and Primary Key classes.
Similarly the associations between Beans (and, maybe, Primary Keys) and Remote interfaces transform to non-identifying (identifying, respectively) relationships.
Other types of associations between EJBs are not supported. Transformation from RDB is done only to EJB specification version 1.1 compliant Entity Beans.
If selected, the import process recreates the database's structure in terms of classes with attributes whose types are Java equivalents to the database's column types (result looks similar to an ER diagram).
If selected, import creates this high level data model that shows the major entities and relationships which support a wide business area. (See also: User's Guide: Entity Relationship diagram.)
In this choice field you can select a diagram of the appropriate type among the currently opened diagrams (for examle, if you choose the "Entity Relationship Diagram" as the "Import to" option value, the "Diagram name" field will contain only currently opened ER diagrams). The database model will be created in the selected diagram.
You can also use the New Diagram button to tell import to create a new diagram of specified type "on the fly".
Click Finish to launch Import.
See also:
