Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • <host> - the URL for the web server on which you deployed database.war.
  • <port> - port where the container is listening for http requests. This defaults to 8082 if the database connector was deployed in the  tomcat bundle or port 8081 if you are running the Database Connector in Standalone mode.
  • <queryset name> - queryset name defined in the database connector configuration file.
  • <query name> – query name  defined in the database connector configuration file.

Logfiles

  • Restart the connector.
    1. Tomcat bundle
  • The database connector writes all output to a single logfile <frevvo-home>\tomcat\logs\database-connector.YYYY-MM
      1. -
    DD.log
    Turning on DEBUG level logging
    1. Stop . You do not have to stop the Insight Server.
    2. Edit the
      1. <frevvo-home>
      \
      1. /tomcat
      \conf\frevvo-config
      1. /conf/dbconnector.properties file.
    3. Add the following line.

    Excerpt

     

    The database connector logging output is very helpful for troubleshooting database SQL issues. This example shows the log entry generated when browsing with an incorrect query name.

    Code Block
    2017-10-26 10:31:35.359 ERROR   12048 --- [http-nio-8082-exec-5] c.f.connectors.database.QueryResource    : Query BIRT/allcustomers not found
    2017-10-26 10:31:35.372  INFO   12048 --- [http-nio-8082-exec-5] org.restlet.Component (1199403432)       : 2017-10-26    10:31:35    0:0:0:0:0:0:0:1    -    0:0:0:0:0:0:0:1    8082    GET    /database/BIRT/allcustomers    -    

    The database connector logs version information for each datasource definition as it makes initial contact with your database(s).

    Code Block
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DriverName: Microsoft JDBC Driver 6.3 for SQL Server
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DriverVersion: 6.3.1.0
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DriverMajorVersion: 6
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DriverMinorVersion: 3
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DatabaseProductName: Microsoft SQL Server
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DatabaseProductVersion: 14.00.900
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DatabaseMajorVersion: 14
    2017-09-15 15:50:01.554  INFO   28614 --- [ost-startStop-1] c.f.c.d.service.ConfigurationService     : DatabaseMinorVersion: 0

    To log the actual SQL statement, arguments, number or rows returned and success status, set logging level to INFO.

    There are different logfiles for the Standalone and tomcat bundle installations.

    Standalone mode

    There are four logfiles in <db-home>\database\database-connector-2.5.x\logsThe Database Connector logfile is located in <frevvo-home>\tomcat\logs for the tomcat bundle and in <db-home>\database-connector-X.X.X\logs directory for the Standalone bundle. X.X.X is the version of the Database Connector. It is named database-connector.YYYY-MM-DD.log

    In standalone mode, you will see three additional logfiles.

    1. DbConnector.err.log - currently empty.
    2. DbConnector.out.log - logs the database connector version.
    3. DbConnector.wrapper.log - empty unless the database connector is running as a servers. Logs starts/stops date/time

      .

      database-connector.YYYY-MM-DD.log - This is the main logfile all output.

    Turning on DEBUG level logging

    1. Stop if you are using the tomcat bundle or the Standalone database connectorDatabase Connector service if you are using the Standalone bundle.
    2. Edit the:
      1. Standalone bundle - <db-home>\database-connector-DBC version number\config\dbconnector.properties file
      .

      Add the following line.

      code
     logging.level.com.frevvo.connectors.database=DEBUG
    Code Block
     logging.level.com.frevvo.connectorsconnector.database=DEBUG
  • Save the file
  • Restart
  • Generate
    1. the
    Database Connector log in JSON formatLogging output defaults to text format. To switch to JSON format, add thisproperty to the frevvo-config.properties for the frevvo-tomcat bundle or to dbconnector.properties file for the standalone bundle. Code Blockspring.profiles.include=logging-json 
    1. Standalone Database Connector service or if you are using the tomcat bundle.

    Common Problems

    Doc Post Failure

    ...