Restriction: This topic applies only when the Enterprise Server feature is enabled.
A service must manage its own resources if:
- The application accesses files or databases (or both) in a transactional way, and contains transactional logic: that is, it
includes COMMITs and ROLLBACKs
- The application uses a resource manager that we do not support in the
Enterprise Server environment; see the list in
Supplementary Information.
A service in which the application accesses files in a non-transactional way, should be application managed.
A transactional application-managed service must contain all the transactional logic it needs, that is, it must complete with
all resources either committed or rolled back.
CAUTION:
The process within which an Application-managed service is executed does not terminate when that service completes. You should
consider how this might affect resource manager client disposition. For example, if the service is accessing Resource Managers
(RMs) for which there is no XAT defined there may be a need to manage the connection.