Designing for long-lived business processes
If you plan to deploy your collaboration as a long-lived
business process, keep the following in mind when designing and
building the collaboration template:
- Use global template or port variables for any data that you
want to persist through the business process.
- The references for all CwDBConnection objects are released before
a service call in a long-lived business process environment, and
all active database transactions are implicitly committed. If necessary,
design your template to re-acquire the CwDBConnection objects after
the service call has finished. In addition, reinitialize the database
transaction context after the service call if you are using explicit
database transaction bracketing.
- If the collaboration is going to be bound to an adapter, ensure
that the adapter is configured to use JMS as the transport mechanism.
Long-lived business processes cannot use an adapter with any other
type of transport.
- Long-lived business process collaborations cannot be bound to
external Access Clients.
- Within a collaboration group, collaborations that do not support
long-lived business processes cannot bind to a long-lived business
process collaboration.
