The Pentaho Metadata Editor (and the Pentaho metadata architecture) supports a vast and rich set of data sources. Before you begin defining your business model, you must first describe the database or data source that you would like to model. You do this by defining one or more connections in the editor.
While the current implementation of metadata supports multiple connections and multiple business models in the same domain, each business model can use physical objects (columns and tables) from only a single connection. We hope to expand this functionality so one model can use two or more connections' tables and columns, but for now, it's important to understand this limitation.
To create a new connection:
This dialog deserves a bit of explanation before we continue.
First, note the Connection Type list on the General tab of the dialog. This is the list of database connections that the Pentaho Metadata Editor and metadata models can support. The list is quite extensive. If you do not see your database in the Connection Type list, you may be able to add it. To add a new database type, you will have to copy the JDBC driver archive for your database into the [studio:PME install directory]/libext/JDBC directory. Restart the Pentaho Metadata Editor, and you will see your database in the Connection Type list.
Under Connection Type, you will see the Method of Access list. Defining a JDBC or OBDC connection typically requires all of the remaining fields on the general tab have the correct information. But if you are into abstracting those details from your metadata domain, then using the JNDI method of access is for you. The JNDI access method keeps your server implementation cleaner as well; once you publish your domain to the server, as long as you have defined the JNDI connections with the same names, you still have a nice implementation where your database information is only described to the JNDI layer.
To take advantage of the JNDI method of access in the Pentaho Metadata Editor, you will need to define your database connection information in a properties file for the editor. We walk through a JNDI connection studio:later in this page.
This example uses the Steels Wheels sample data provided with the Pentaho Open BI Suite (aka the "pre-configured installation" or "PCI"), available from our downloads site.
To connect to a MySQL database using JDBC:
Our second example starts out much like the first, but requires a few different steps.
This name is actually the JNDI name that you will specify to map to the JNDI connection properties. In order for the Pentaho Metadata Editor to know what this name really means, you need to set up a simple JNDI properties file.
See the studio:Database Connection Guide for more information about this dialog.