7.3

Table Of Contents
Database Considerations (ODBC)
On 64-bit operating systems, the ODBCData Sources created by the Data Source (ODBC)icon in the Administrative
Tools will not appear here, as PlanetPress Suite is 32-bit and cannot access the 64-bit data sources. In order to create
an ODBCconnection visible by PlanetPress, you will need to access the 32-bit version of the ODBCmanager, avail-
able in C:\Windows\SysWOW64\odbcad32.exe .
The following considerations should be kept in mind while working with ODBCDatabases in PlanetPress Suite.
l Microsoft Access
l Database file (mdb)must be local to the PlanetPress Workflow computer. It cannot be located on a network
drive or another server.
l Total database size is limited to 4GBof data.
l Total size of a single table is 2GB.
l May be unstable in large implementations.
l MySQL
l Database can be in any location, but performance will depend on the speed of the connection between Plan-
etPress and the MySQLserver.
l MySQL's performance has been slower than SQLServer and SQLServer Express during our tests.
l By default, MySQLis configured not to allow any SQLrequest larger than 16 megs.
l In the event where 2 requests are made simultaneously on the same record, MySQLwill queue one of the
requests and execute it once the first one is done. In extremely rare cases this may cause a timeout on very
large requests.
l MSSQL(Microsoft SQLServer)
l Database can be in any location, but performance will depend on the speed of the connection between Plan-
etPress Production and the SQLserver.
l In the event where 2 requests are made simultaneously on the same record, SQLServer will drop the most com-
plex request. Resubmitting the PGCfor processing should resolve this issue. This, however, should happen only
rarely.
l When configuring the ODBCconnection, your must use the Microsoft version of the driver, and not the Native
SQLversion of the driver. This is due to a technical limitation of the native driver that interferes with the Plan-
etPress Suite database requests.
Specifically for PlanetPress Capture, these considerations mean the following:
l In Microsoft Access, the total size of stored document cannot be larger than 2GB and this database will be very
unstable in implementation with more than a few thousand pattern sequences being used simultaneously. It is only sug-
gested for small implementation with less than 10 pens, or for demos.
l In MySQL, the 16 megs packet size limit can be an issue if the PDFs created by Capture are larger than this size; An
error saying "MySQLServer has gone away" would appear in this case. This can be fixed by configuring the max_
allowed_packet setting in the MySQLConfiguration(Reference).
l Also in MySQL, if a timeout occurs on simultaneous record access, resubmitting the PGCfor processing should resolve
the issue.
l In SQLServer, if one of your requests is dropped because of simultaneous accesses, resubmitting the PGCshould
resolve the issue.
Security Considerations
PlanetPress Capture introduces new and efficient methods for digitally capturing the contents of ink layed out on physical
paper. However, because of its nature, some end users may voice concerns about security and privacy. Are signatures
secure? Could their transmission be intercepted? How can the contents of the Anoto digital pen be protected from malicious
users?
©2010 Objectif Lune Inc - 186 -