JDBC Data Source - Create Connection

If the "JDBC Data Source" entry is selected in the left pane under "Consume Data," you can create a new JDBC connection via the main menu "Data Source / New Data Source" or the corresponding context menu. A wizard will then open automatically to help you with the configuration.

Before establishing the connection, please verify that all requirements have been met. You can find all the information here.

General Information

Enter the name of the connection here.

Under "Data Source," you can enter the connection details directly or set them up with the help of a wizard. To do this, click "Wizard." You can find all additional information here.

JDBC Driver Class

To access the database, you must specify a JDBC data source class or a JDBC driver as the data source, along with a class that describes certain database properties. Intrexx can access all data source classes stored in the Java classpath. If you connect a data source for which no class exists, please copy the library (*.jar) to the "intrexx/lib" installation directory. Next, restart the portal service.

Click "Search" to select a JDBC driver class.

JAR Archive / Select Directory

Select the data source class here and click "OK."

Descriptor Class

Enter the underlying data source class here. This class is typically provided by JDBC2-compliant drivers. If this is not the case, access to JDBC1-style drivers can be enabled using the `de.uplanet.server.poolmanager.EmulatedPooledDataSource` data source class. Please refer to the documentation provided by the respective vendor to determine whether your driver meets the requirements. The descriptor class must be specified using the correct SQL syntax to access the data source and the corresponding data fields. For example, it is responsible for determining how date formats can be queried.

Time Zone

This is where you set the time zone for the external data source.

Allow write access

This setting allows changes to be made to the data in the data source.

Please note that INTREXX GmbH does not provide support for data inconsistencies resulting from write access to third-party data sources.

Click "Next."

Connection Parameters

Connection parameters can be enabled here. To do this, click the corresponding checkbox. If a checkbox is not selected, the corresponding parameter has no effect.

In the second column, you can see the current value of a parameter. The connection parameters vary depending on the data source used. You can find information in the manufacturer's documentation for the respective drivers, such as here:

If, for example, special characters are not displayed correctly, the appropriate encoding can be specified in the URL.

Click "Next."

Descriptor Settings

This dialog box appears only if no data source directly supported by Intrexx was selected in the General Settings (e.g., the descriptor class "de.uplanet.jdbc.GenericDescriptor").

General

Sorting

Ensuring the correct sort order (e.g., in view tables or in the result sets of records during a search)

Result Set Type for Update

If you encounter problems with write access, select a different result set type here

Use Batch Updates

The setting (Yes) should be kept as is for performance reasons and should only be changed if problems occur when saving records.

ORDER BY Alias Support

1) SELECT Field1 AS FieldAlias FROM Table1 TableAlias ORDER BY TableAlias.FieldAlias
2) SELECT Field1 AS FieldAlias FROM Table1 TableAlias ORDER BY TableAlias.Field1 SELECT Field1 AS FieldAlias FROM Table1 TableAlias ORDER BY FieldAlias
3) SELECT Field1 AS FieldAlias FROM Table1 TableAlias ORDER BY TableAlias.Field1

Examples:

Type 1) SQL Server
Type 2) HSQL, SAP DB, Oracle
Type 3) Access

Oracle 8 Syntax for Outer Joins

Oracle versions <= 8 use a different SQL syntax for OUTER JOIN queries than most other databases. If a database uses the same syntax, select "Yes" here

Clobs are searchable

You can search long text fields in this database. This setting is relevant to the search.

Using the Driver's Clob/Blob Objects

For most databases, you can select "No" here. One of the few exceptions is Oracle, for example. For performance reasons, it may still make sense to use the driver's objects in some cases.

Data Field Conversion

Boolean Literal TRUE

Possible values: TRUE / true / 1. As a rule, TRUE is the right choice.
(Exception: MS SQL Server, Oracle: 1)

Boolean Literal FALSE

Possible values: FALSE / false / 0. As a rule, FALSE is the right choice. (Exception: MS SQL Server, Oracle: 0)

Calendars for Date Fields

Some databases do not support the inclusion of a calendar object when querying date and time fields. This calendar object is required for calculations in the respective time zone. As a general rule, "NO" is the safe choice.

Date According to SQL

Formatting a date object for storage in the database using an SQL statement (%t is the corresponding placeholder that must be included).

ISO Date Text to SQL

Formatting a string for storage in the database using an SQL statement (%t is the corresponding placeholder that must be included).

Large Objects (CLOB / BLOB)

CLOB method for an empty CLOB

Please read the documentation at

for the corresponding driver. Generally, no information is required here; the fields are not selectable.

Clob Method for Writer

Driver's Blob Class

Blob Method for an Empty Blob

Blob Method for OutputStream

The entries described above are usually configured correctly by the wizard. For specific data sources, more detailed information can be entered here. Please refer to the documentation for your database system or database driver.

Pooling

Enable Pooling

With this setting, database connections that have already been established can be reused. This improves performance, especially on high-traffic websites. If you rarely access the configured data source, it makes sense to disable pooling. This also applies to the database vendor's license terms that limit the number of concurrent connections allowed.

Max. connection age ... sec.

Specifies the time period after which even a frequently used connection will be released at the latest once it is no longer in use.

Release unused connections after ... seconds.

Specifies the number of seconds after which a connection is released if it is not in use.

Cleanup interval ... sec.

Specifies the time period after which unused objects are released.

Limit pool size to ... connections

Enter the number of connections to which the pool size should be limited.

Click "OK." The connection has now been established.

DBMS Characteristics

For existing JDBC connections, the DBMS properties can be viewed via the "Data Source" main menu or the corresponding context menu. The dialog box displays the methods and their respective values for the currently selected JDBC data source.

The value of the respective method is displayed here.

More Information

General Information and Requirements

Integrating Data into Applications