Section |
---|
Column |
---|
| frevvoOnce you have started the Database Connector up and running and configured with your database, access the connector by typing the status URL below directly in your browser to quickly verify proper installation. Tomcat Bundle: http://localhost:8082/database/status - Change localhost and port 8082 to the <server> and <port> for your tomcat frevvo tomcat installation where you are deploying the connector. Standalone: http://localhost:8081/database/status - the default port for Standalone mode is 8081. Change localhost and port 8081 to the <server> and <port> where you installed the Standalone connector.
The configuration model shows two additional properties: lastModified and digest. These properties are set when the configuration.xml is read and will change when modifications are made to the configuration.xml file.
- SHA-1 digest of of all the file content is generated
- Date/time of the last modification to configuration.xml.
|
|
...
- <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 frevvo 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.
...
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 |
The 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. - DbConnector.err.log - currently empty.
- DbConnector.out.log - logs the database connector version.
DbConnector.wrapper.log - empty unless the database connector is running as a servers. Logs starts/stops date/time.
Turning on DEBUG level logging- Stop if frevvo if you are using the tomcat bundle or the Database Connector service if you are using the Standalone bundle.
- Edit the:
- Standalone bundle - <db-home>\database-connector-DBC version number\config\dbconnector.properties file
- Tomcat bundle - <frevvo-home>/tomcat/conf/dbconnector.properties file.
Add the following line. Code Block |
---|
logging.level.com.frevvo.connectors.database=DEBUG |
- Save the file
- Restart the Standalone Database Connector service or if frevvo if you are using the tomcat bundle.
|
...
If a submission doesn't reach the Database Connector or when certain database operations fail, willfrevvo will
- Flag the submission with an error in the Submissions Table
- Send Doc Post Failure notification email(s) reporting information about the error to all tenant administrators or workflow admins (if configured)
...
All DBC SQL operations are performed within a database transaction. When the following SQL errors occur, flags frevvo flags the submission with an error and generates Doc Action Failure emails to the tenant/workflow admin(s) :
...