8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- Basics
- Features
- The Nature of PReS 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
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
sources. In order to create an ODBCconnection visible by PlanetPress, you will need to access the
32-bit version of the ODBCmanager, available in C:\Windows\SysWOW64\odbcad32.exe .
The following considerations should be kept in mind while working with ODBCDatabases in PlanetPress
Suite.
l All databases
l User Rights:During normal operation, Read/Write to tables should be sufficient. However, during
the initial setup, the Create/Drop tables rights is necessary.
l Minimum 100MBof database size is required as a minimum, but the space requirement depends
on the implementation. The more active documents in the database, the more space is used -
note that this progression is rather linear.
l Regular database maintenance is required, such as database compacting, is required by a
system administrator.
l It is recommended to create an ITprocess that backs up the database regularly.
l The recommended ideal setup is a dedicated SQLServer PC, accessed by PReS Workflow
through an ODBCconnection on the local network.
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.