Long-lived processes store process data in the LiveCycle database. The growth of the LiveCycle database can be minimized using a few easy process design and product configuration strategies.
Use short-lived processes. Short-lived processes don’t store process data in the database. The downside is that you can’t use Adobe Administration Console to track process status and state. Also, you won’t have a history of the process or any BAM reports.
Some service operations, such as the Assign Task operation (User service), require that they are used in long-lived processes. In this case, you can segment the process into several subprocesses and make them short-lived when possible. If you use this strategy, short-lived subprocesses should handle large data items, such as document values.
Use variables sparingly. When using long-lived processes, for every process instance, space is allocated on the database for each variable in the process. Strategic use of variables can save a considerable amount of space:
Use the fewest number of variables that is possible. For example, you can overwrite variable values when old values are no longer needed in the process. And delete any variables that you’ve created and are not using. (Tip for LiveCycle ES Update 1 users: Validate the process to find unused variables.)
Use simple variable types (such as string, int, etc) and avoid using complex variable types when possible. Database space is allocated for variables even when they don’t contain a value. Complex variables typically require more space than simple ones.
Use Global Document Storage (GDS) effectively. The global document storage directory on the LiveCycle ES server is used to store, among other things, files that are passed to LiveCycle ES services in processes. To improve performance, smaller documents are instead stored in-memory and persisted in the database.
Adobe Administration Console exposes the Default Document Max Inline Size property for configuring the maximum size of documents that are stored in-memory and persisted in the database. If you set this property to a low value, most documents are persisted in the GDS directory instead of in the database. The advantage is that you can more easily delete the files when they are no longer needed when they are stored in the GDS directory.
Some background references:
- Short-lived processes and long-lived processes
- “Global document storage directory” in Administering LiveCycle ES
- Configuring the core system settings