| Section | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
It is included in the v7.2.4+ in-house tomcat bundle. You can download the in-house software from frevvo DocuPhase Forms Software Downloads Directory. It is also available in a separate Standalone zipfile which can also be downloaded from the frevvo Software Downloads Directory.
Tickets Fixed:
- #21139 - A third party JDBC driver to connect to Active Directory as an SQL database causes validation to fail. Drivers of this type are not supported
- #21150 - Adding SQL Server JDBC driver to WAR causing issues for customers who already have the driver installed in the tomcat/lib directory
- #21156 - MS SQL JDBC driver embedded in the dbconnector causing queries to not work after upgrading to version 2.5 of the Database Connector
- #21196 - Write dbconnector logs to tomcat/logs/database-connector.YYYY-MM-dd.log instead of frevvo.log
- #21232 - jTDS driver does not work with DBConnector v2.5.0
- #21279 - Log is not generated when configuration parameters are located in database.xml
#21411 - <cache/> element in configuration.xml causing error
#21421 - Autocreate="true" does not work"
#21428 - Empty resultsets report "Document is null. Premature end of file" errors in the debug console when testing forms
...
The Database Connector is included in the v7.2.1 in-house tomcat bundle. You can download the in-house software from the frevvo DocuPhase Forms Software Downloads Directory. It is also available in a separate zipfile. Click to download the standalone zipfile from the frevvo DocuPhase Forms Software Downloads Directory..
One advantage to using version v2.5 of the Database Connector with v7.2.1 is that the configuration.xml is separated from the underlying infrastructure database and related credentials. Review the enhancements below for more reasons to upgrade.
Enhancements:
- #18166 - Batch processing of POST/Create requests. JDBC inserts are batched instead of performing individual inserts.
- Logging improvements
- KIOSK mode - when no configuration.xml is defined, the KIOSK mode pre-loads BIRT (ClassicModels) and myStore QuerySets with in-memory Derby databases. This will make it very easy to try out the DB Connector.
- #19243 - Support for JSON payload from business rules when performing POSTs and PUTs.
- #20546 - Query statements are validated when the DB Connector starts instead of when used.
- Console prints the DB Connector version and revision number.
- #18620 - Generating max-length for SQL Server NVARCHAR
- #20532 - Ability to disable QuerySets and/or Querys while developing your integration.
- #18708, #18676 - Returns blank or null in the JSON results for columns that have blank or null values..
- The database.war is executable.
- The SQL Server JDBC driver is included in the Database connector war.
- QuerySet and Query names only allow alphanumeric, dot, dash and underline characters. They must start with letters. This change makes sure that they are automatically XML and JSON friendly.
- The driver and validationQuery attributes in <resource-def> are now optional: they will be properly inferred based on the current database.
- The configuration.xml file is automatically picked up from the current directory where the DB Connector was launched or from ./config/configuration.xml. It can be manually set by using the frevvo.connectors.database.configuration property as before. This is specially useful when running the DB Connector standalone.
- #9564 - Ability to generate schemas for all queries in a queryset. This makes it possible to download a single XSD for all queries at once.
Tickets Fixed:
- #9244 - http.post() to DB connector not working from rules for URL parameters and JSON payload in POST/PUT requests.
- #9565 - A query with '<' sign in it does not work.
- #12750 - DB Connector:Support PUT/POST for European Characters.
- #13134 - Database POST fails when there is % character in one of the fields.
- #18620 - SQLSERVER : Datatype nvarchar does not generate max-length restrictions
- #18207 - Errors while inserting, updating, selecting row(s) using the DB connector are simply logged and ignored: it always returns an HTTP 200 status code.
- #19062 - MySQL column w/ timestamp datatype failing when trying to insert date/time control value.
...