Progress Sonic ESB Configuration and Management Guide

Considerations with Dehydrated Processes
Considerations with Dehydrated Processes
With dehydration, Sonic BPEL Server stores the process and its state in the database while
waiting for a response, thus freeing up server resources. Hydration occurs when the
engine receives the response and restores the process and its state from the database and
continues executing the process.
Process instances cannot be dehydrated unless the following conditions are met:
● You are not in development mode (TEST_CONTAINER_MODE is not set, or set to FALSE).
(See “Setting Test Mode for ESB Containers Used in Development” on page 68.)
● You are using a Persistent store (that is, not In Memory). (See “Setting Persistence
Options” on page 239.)
● All activities must be in a waiting state (that is, no alerts are set).
● There are no synchronous inbound connections.
Progress Sonic ESB Configuration and Management Guide 8.5 246