8.5
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
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 PlanetPress and the MySQLserver.
l MySQL's performance has been slower than SQLServer and SQLServer 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 SQLServer)
l All versions of the SQLServer are supported, including all Express versions.
l Database can be in any location, but performance will depend on the speed of the connection
between PlanetPress Production and the SQLserver.
l In the event where 2 requests are made simultaneously on the same record, SQLServer will
drop the most complex request. Resubmitting the PGCfor processing should resolve this issue.
This, however, should happen only rarely.
l When configuring the ODBCconnection, 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 PlanetPress 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 suggested 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).