EGL offers two other ways to create an SQL connection:
Even if you plan to use either of these functions, it is still recommended that you have a default connection in place.
You must have a database set up and running. The database must be one of the products that EGL supports. See Supported SQL database managers for more information.
In EGL, you can access the New Connection wizard from many of the places where an SQL connection is required. The workbench provides several places to find the New Connection wizard:
The information the wizard needs varies with the type of database that you use. When you choose from the Select a database manager list, the wizard fills in as many default values as it can. For the list of supported databases and the information that each requires, see Supported SQL database managers.
The Drivers dropdown list contains the names of drivers you entered through the Driver Definitions preferences page. For more information, see "Creating a driver definition" earlier in this topic.
When you have given the wizard enough information, the Test Connection button becomes available. Click this button to verify your connection information. If you get an error message, check your settings or work with your database administrator to resolve the problem.
If the test is successful, you have everything you need to use the EGL features that require a design-time connection, such as Creating a data access application or Retrieving SQL table data. You are not, however, automatically set up to have an SQL connection at run time. To specify that connection, see Using an SQL database connection at run time.
By default, the New Connection wizard will retrieve information for each schema in the database and each table in each of those schemas. Retrieving this information can take time on large databases. The EGL Data Access Application wizard requires this connection information to produce parts from the database, but the other areas of EGL design-time access functionality, such as the SQL retrieve functionality described in Retrieving SQL table data, do not require this information. For this reason, you can save time by filtering out schemas or tables that you do not want to use with the Data Access Application wizard, or by filtering out all of the schemas and tables if you do not want to use this connection with the Data Access Application wizard at all.
Schemas that you filter out of the connection will not be available if you use this connection with the Data Access Application wizard.
You can override the default values in these fields by selecting Other for your JDBC driver and specifying the appropriate JDBC driver class.