meta data for this page

Setup menu > Application

Databases

This settings tab lists all databases known to Vigilens.

Add a database

SQL Language used

Vigilens natively supports the SQL language for the following platforms:

  • Access
  • DB2/400 except Union
  • DB2/Windows except Union
  • MySQL
  • Oracle
  • SQL Server

Data source

Oracle

For Oracle databases, connection is made through OCI, only TNS service name has to be provided.

In some machine configurations, the OCILIB library does not initialize correctly because the Windows user environment variables do not allow to locate the oci.dll file (present in the Oracle installation directory).
NB : this is often the case for the web server due to Windows account binded to web service.

It is then possible to define this path via a registry key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\EVIDENS\Param\OracleLibPath
(HKEY_LOCAL_MACHINE\SOFTWARE\EVIDENS\Param\OracleLibPath for 32 bits machines)

ODBC

Otherwise, the connection is made through ODBC.

You must then choose (with the wizard) one of the ODBC connections defined either at the user level or at the system level. In most cases, we will use a system source.

In the case where the data source is not created in ODBC, you can access the windows ODBC setup by clicking ODBC data source setup button.

On 64-bit systems, it is advisable to use this button to access ODBC data source administration. This is because the application uses the 32-bit version of ODBC while the administration tools allow access to the 64-bit version.

In order to be able to add or modify an ODBC source from ODBC data source setup button, it may be necessary to start the AdminTool as administrator.

Connection

It is advisable to enter the login information so that the user does not have to enter it every time the data source is used.

Database type

Allows you to specify the JDE version to ensure the correct reading of the data. In the case of a JDE type source, the choice of version ensures the correct operation of the functionalities specific to JDE type data sources.

Data source name

Type here the description that will appear everywhere in Vigilens.

Advanced Setup

Global

  • Use of binary files: Allows faster and smoother display of results by limiting access to the database.
  • Allow UNION queries: This option is only visible for DB2 type databases. It allows you to allow or disallow UNION type queries depending on the ability of the ODBC driver to handle this type of SQL syntax.
Files

  • Improve extraction of file list: Allows to recover the list of tables faster in case of a JDE data source. Warning, depending on the type of database and its configuration, using this option may cause some tables to “disappear” from the list.
  • Web Security: This setting is only available for JDE data sources. It allows you to define the name of the table (JDE) used when executing queries from JDE with automatic recovery of the security associated with the logged-in user.
Attachement

This tab is only visible for JDE data sources.
It allows you to specify if the appendices are in HTML format or not.
As for the other options, these are advanced settings that should not be modified without a valid reason.

Share

Once defined, a data source must be shared in order to be used on multiple machines. An unshared data source can only be used on the machine on which it was created.

For JDE type data sources, it is mandatory to share the data source even if only one machine is used.

Help box

This tab allows you to select the elements of the application for which you want to display tooltips as well as the delay for displaying tooltips.

Global

  • Delete : Allows you to choose whether or not to display a confirmation message before deleting a group or user.
  • Excel: Allows you to redefine the settings related to the opening of Excel files for the machine on which the application is running (see Vigilens settings).

Set user

This tab allows you to change the password of the logged-in user as well as the languages associated with it:

  • Language used for the interface: Language in which the menus and screens of the applications to which the user will connect will be displayed.
  • Language used for the descriptions coming from the database: Language in which will be displayed the possible descriptions related to the data coming from the database such as, for example the name of the fields of the JDE tables, the descriptions associated to the UDC values…

Database for export

This tab works like the “Databases” tab but allows you to define the data sources that can be used by “Export to a database” type renditions.