Overview

(1) Opens a dialogue for managing the database drivers under ./extlib. Note: Please upload JDBC drivers only as .jar files. Afterwards a restart of the Integration Server is necessary. To check whether the driver has been loaded correctly, you can search for the name of your .jar file in file./logs/wrapper.log (Windows) or ./logs/console.txt (Linux).

(2) Selection of a chargeable Business Connector (Input Agent Cron). Please contact information@lobster.de. Note: See also page Update-Center.

(3) Indicates whether it is a classic database connection (as you know it) or a Business Connector (plug symbol). You can recognise the database for Lobster_data itself by the green icon.

Creating New (Classic) Database Connection

You can create a new database connection via the plus symbol at the bottom right or via the context menu. Connections that you create here no longer have to be maintained in the configuration file ./etc/database.xml, you can work exclusively in the GUI. In addition, no restart of the Integration Server is necessary, only for newly uploaded drivers (see above).

(1) See section DatabaseService for details.

(2) Here you can select pre-configured connection templates. Note: You can obtain the latest templates via the Update-Center.

(3) If this checkbox is set, field Catalog Name can be left empty. If the checkbox is not set and the Catalog Name field is empty, the alias name is automatically entered there.

(4) Classic database connections. Replace the placeholders DB_HOST_OR_IP and DB_NAME with your specific values. If required, fill in missing fields and JDBC properties such as Catalog Name, User, Password, etc.

(5) Connectors.

Connection Test

You can carry out a connection test via the context menu of a selected connection. See also following section.

Database Access via GUI Tools

• Plugin SQL Console.

• Admin Console → SQL Monitor.

Database Access in Input Agents in Phase 1

• Basic SQL (Input Agent Cron).

• Business Connector (Input Agent Cron) (paid connectors and classes DefaultFileSQLCron, DefaultSQLCron, CrossSQLCron)

Database Access via Functions in Phase 3

• select into list(select a, dbalias b, [c,d,e,f,g,h,i,j],k,l,[m,n,o,p])

• select into map(a,b,[param &1 = c], d,e, f,g,h,i,j], delimiter k, map l,m,n,o,p)

• select into map(a,b,list name c, delimiter d, map e,f,g,h,i)

• select-statement a [[param &1 = c], d,e, f,g,h,i,j], default k,l,m,n dbAlias = b

• call db procedure a, alias b, [c,d,e,f,g,h,i,j],k,l,m,[n],o,[p]

• call db procedure a, alias b,c,d,e,f

• call db procedure a with ResultSet [[param &1 = c], d,e, f,g,h,i], [column of ResultSet j = 1], default k,l dbAlias = b

• call db procedure a with ResultSet into Map/List k [[param &1 = c], d,e, f,g,h,i], delimiter j, l, dbAlias = b

• update (sql-stmt a, alias b, list c, ignore error d)

• update-statement a, alias b [[param &1 = c],d,e,f,g,h,i,j,[k],[l],[m]]

• exists db-row(select-statement a [[param &1 = c], d,e,f,g,h,i,j,k,l])

• set-vars(select a, dbalias b, [c,d,e,f,g,h,i,j for params &1...&8][,k,l,m,n])

Relevant System Variables

• VAR_SYS_EXCEPTION_STACKTRACE

• VAR_SYS_HAS_SQL_ERROR

Database Access in Phase 4

See section Phase 4 - SQL Execution (GUI).