...
The following Database version are supported
(We use the same driver as that used by The Jira Server. Please see check these out: https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html )
Oracle: We use the same driver as that used by The Jira Server (Please see hereby: https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html )
Oracle 19c
Oracle 18c
Oracle 12c R2
PostgreSQL
PostgreSQL 11
PostgreSQL 10
PostgreSQL 9.6
2 – Database connections
The Database connections are considered as a pool or resources, which can be used for several purposes. This core functionality will be installed with every VIP.LEAN app requiring a read and /or /and write access to the databases.
Under the menu point: Manage apps > VIP.LEAN DATABASES ETL FOR REPORTING > Database Connections you can create, edit, and delete the database connections:
...
Field | Type | Description |
|---|---|---|
Database Connection Name | String | Please enter a name for your database connection. It is mandatory and should be unique. |
Driver | List | Possible values: Please select your database version. |
Connection URL | String | When you click in this field a configuration URL will be recommended. Please enter the URL without any user or password information. See attached pictures below this table. Postgres URL: Please ask your DB ETL admin for the correct URL. |
Username | String | Database user name username provided by the DB Admin. |
Password | String | Database password provided by the DB Admin. |
Max. Pool Size | Number | Number of open connections to be used by the Data Warehouse ETL for Reporting app to accelerate the DB read and write actions. When you increase this value, please make sure the required hardware resources are available. |
Please test your connection before you save the connection. In case you receive any an error message, please contact your DB admin to analyze the root cause (Network connection error, User and password are wrong, Connection URL is wrong …).
Once the connection is saved, it can be used by the app for further actions.
Please note: in In the case where you use the DB connection actively for read or write actions, any subsequent change of to the database parameters could lead to major errors. If you want to migrate your Data Warehouse ETL for Reporting App to another DB ETL connection, please create first a second DB connection and migrate the Data Warehouse ETL Rules to this connection.