JDBC data source - Create connection

If the "JDBC data source" entry below "Consume data" is selected in the left-hand area, a new JDBC connection can be created 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.

Please check that all requirements are met before creating the connection. You can find all the information here.

General properties

Enter the name of the connection here.

Under "Data source", the connection data can be entered directly or compiled with the help of a wizard. To do this, click on "Wizard". You can find all further information here.

JDBC driver

For access, a JDBC data source class or a JDBC driver and a class describing some database properties must be specified as the data source. Intrexx can access all data source classes entered in the Java class path. If you connect a data source for which no class is available, please copy the library (*.jar) into the installation directory "intrexx/lib". Finally, restart the portal service.

Click on "Search" to select a JDBC driver class.

Select JAR archive / directory

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

Descriptor class

Here, the underlying data source class will be entered. Normally, this class will be made available to you by JDBC2 conforming drivers. If this is not the case, access to JDBC1-type drivers can be enabled via the de.uplanet.server.poolmanager.EmulatedPooledDataSource data source class. Please refer to the documentation of the respective provider to find out whether your driver meets the requirements. The descriptors class must be entered for access to the data source and the corresponding data fields in the correct SQL syntax to be possible. This is responsible, for example, for how date formats are queried.

Time zone

The time zone of the external source can be defined here.

Enable write access

Enable write access This setting makes it possible to change the data in the external data source.

Please note that INTREXX GmbH does not provide support for data inconsistencies caused by write access to external data sources.

Click "Next".

Connection parameters

The connection parameters can be activated here. Click on the corresponding checkbox to activate/deactivate them. 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 may vary depending on the data source in use. Information can be found in the developer's documentation for the respective driver, such as these here:

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

Click "Next".

Descriptor settings

This dialog will only be displayed if no data source directly supported by Intrexx has been selected in the General information (e.g. the descriptor class "de.uplanet.jdbc.GenericDescriptor").

General

Sort

Sets the correct sorting order (for example, how data is sorted within view tables or results lists when searching).

Result set type for update

If there are problems with write access, select a different resultset type here

Batch updates use

The setting (yes) should be retained for performance reasons and should only be changed if problems occur when saving data 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 TablesAlias ORDER BY TablesAlias.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 searchable

In this database, long text fields can be searched. This setting affects the search function.

Use driver Clob/Blob objects

For most databases you can enter ""no"" here. One of the few exceptions is Oracle. For performance reasons, it can sometimes be useful to use driver objects anyway.
Data field Transformation

Boolean Literal TRUE

Possible values: TRUE / true / 1. Normally ""TRUE"" is the correct selection.
(Except: MS SQL Server, Oracle: 1)

Boolean Literal FALSE

Possible values: FALSE / false / 0. Normally ""FALSE"" is the correct selection. (Except. MS SQL Server, Oracle: 0)

Calendar for date fields

Manche Datenbanken unterstützen die Mitgabe eines Kalenderobjektes für die Abfrage von Daten und Uhrzeitfeldern nicht. This calendar object is necessary for calculation of the local time zone. Normally, ""no"" is the safest selection.

Date according to SQL

Formatting of a date object for storage in the database via SQL statement (%t is the corresponding placeholder that must be present).

ISO date text nach SQL

Formatting of a string for storage in the database via SQL statement (%t is the corresponding placeholder that must be present).
Large Objects (Clob / Blob)

Clob method for empty Clob

 Please read the documentation

for the relevant driver. Normally no entries have to be made and the fields cannot be selected.

Clob method for Writer

Blob class for driver

Blob method for empty Blob

Blob method for Output stream

The entries explained above will normally be correctly configured by the wizard. For special data sources you can enter more exact details here. In this case, read the documentation of your database system and/or database driver.

Pooling

Activate pooling

This option means that database connections requested once can be used again. This increases performance, especially for highly frequented portals. If you only rarely access the configured data source, it makes sense to deactivate pooling. This may also be required by the license terms of the database manufacturer, who may restrict the amount of permitted simultaneous connections.

Max. age of a connection ... sec.

This setting allows you to define a span of time, after which a frequently used connection must be released, as soon as it is not in use.

Release unused connections after ... sec.

Defines after how many seconds of inactivity a connection should be released.

Clean-up interval ... sec.

This setting defines after how many seconds unused objects should be released.

Limit pool size to ... connections

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

Click "OK". The connection is now created.

DBMS properties

For existing JDBC connections, the DBMS properties can be displayed via the main menu "Data source" or the corresponding context menu. The methods and the respective value for the currently selected JDBC data source are displayed in the dialog.

The value of the respective method is shown here.

More information

General information and requirements

Integrate data into applications