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. Click here for more information.

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". See here for further information.

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 that has no class assigned to it, please copy the library (*.jar) to 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, you can establish access to JDBC1-similar drivers with the data source class "de.uplanet.server.poolmanager.EmulatedPooledDataSource". Please refer to your software's documentation to see if your driver fulfills these 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.

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:

• Microsoft SQL Server

  https://msdn.microsoft.com/de-de/library/ms378672(v=sql.110).aspx

• PostgreSQL

  https://jdbc.postgresql.org/documentation/

• Firebird

  https://firebirdsql.org/en/jdbc-driver/https://firebirdsql.org/file/Jaybird_2_1_JDBC_driver_manual.pdf

If, for example, special characters are not shown properly, the corresponding encoding can be provided 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 write access will cause any problems, select another result set type here.
Batch updates use	You should keep this setting ("yes") for performance reasons. Only change this setting if any problems occur while saving data sets.
ORDER BY Alias support	1) SELECT Feld1 AS FeldAlias FROM Tabelle1 TabellenAlias ORDER BY TabellenAlias.FeldAlias 2) SELECT Field1 AS FieldAlias FROM Table1 TablesAlias ORDER BY TablesAlias.Field1 SELECT Field1 AS FieldAlias FROM Table1 TablesAlias 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 and earlier use a different SQL syntax for OUTER JOIN queries than most other data bases. If a database uses the same syntax, please select "yes"
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	Formats a date object for storage in the database via SQL command (%t is the corresponding placeholder that must be present).
ISO date text nach SQL	Formats a string for storage in the database via SQL command (%t is the corresponding placeholder that must be present).
Large Objects (Clob / Blob)
Clob method for empty Clob	Please read the documentation of the corresponding 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 will reduce unnecessary load on the database. This may also be required by the license terms of the database manufacturer, who may restrict the amount of permitted simultaneous connections.

Maximum connection age 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.

Cleanup 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 on "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