There is the distinction of core software and optional extensions to the core functionality.
The core critical functionality that always runs in any PDP-D container is maintained in those projects named with the “policy-” prefix. These are:
- policy-utils (utilities)
- policy-core (drools libraries interfaces)
- policy-endpoints (networking)
- policy-management. (management of the platform)
This is the minimum set of services that any PDP-D application provides to their executing drools-applications.
The intent is that this functionality is kept stable, fast, and minimal. As new development is added, the intent is that this functionality is resilient to breakage as side effects to new development.
Extensions are optional modules that are commonly known as features that extends the PDP-D core functionality with new enhancements.
Features can be enabled or disabled. When a feature is disabled, it is a hard disable with no side effects on the core functionality, meaning no additional libraries, configuration, etc. that may have side effects on the core functionality described above.
The current extensions supported are:
- Feature Test Transaction (disabled by default)
- Feature State Management (disabled by default)
- Feature EELF (disabled by default)
- Feature Healthcheck (enabled by default)
- Feature Session Persistence (disabled by default)
- Feature Active/Standby Management (disabled by default)
- Feature Distributed Locking (enabled in OOM installation by default)
- Feature Pooling (enabled in OOM installation by default)
- Feature Controller Logging (disabled by default)
- Feature MDC Filters (disabled by default)
Click on the individual feature links for more information
End of Document