JBoss Enterprise Application Platform expansion pack (JBoss EAP XP or EAP XP)
Life Cycle and Support Policies
The JBoss Enterprise Application Platform expansion pack (JBoss EAP XP or EAP XP ) is an implementation of the Eclipse MicroProfile specification for application workloads. The EAP XP is not a runtime by itself, it needs to be setup to run on a JBoss EAP version and it has its own versioned releases. For example, EAP XP 1.0.0 runs on JBoss EAP 7.3 Update 1.
JBoss EAP versions certify EAP XP versions. JBoss EAP Supported Configurations page lists EAP XP versions that are certified.
The JBoss EAP XP implements the MicroProfile specification which is typically released at a faster cadence than JBoss EAP. As a result, the EAP XP has a different support life cycle and cadence (typically much faster) than that of JBoss EAP. It should be noted that when JBoss EAP XP is setup on a JBoss EAP server installation, the JBoss EAP XP Support Life Cycle becomes effective and the Red Hat JBoss Middleware Product Update and Support Policy terms and dates no longer apply.
Every major version of a JBoss EAP XP product is maintained and supported independently during its life cycle. For each major version of a product, patch updates, if and when available, will be issued serially and will be applicable incrementally to previously released patches and updates. Future major releases will aggregate the contents of prior patches and updates and may add additional new functionality. Before applying JBoss EAP XP patches, users need to ensure that the underlying JBoss EAP has the latest patches applied.
Every major version of JBoss EAP XP products endeavor to maintain backward-compatibility with previous versions to aid with the migration of applications from one major release to another. However, the implemented Eclipse MicroProfile version releases may break backward compatibility. Because the new JBoss EAP XP is dependent on Eclipse MicroProfile, backward compatibility is therefore not guaranteed.
The life cycle for a major release of JBoss EAP XP product is divided into two primary phases: the Full Support Phase, the Maintenance Phase.
JBoss EAP XP adopts a life cycle to accommodate rapidly changing Eclipse MicroProfile technology.
Phase 1: Full Support
Full support is provided according to the published Scope of Coverage and Service Level Agreement. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement. All available and qualified patches will be applied via periodic product updates and patches, or as required for qualified security patches.
Full Support starts with a new EAP XP major release and ends when a new EAP XP major version is released. When a new major version of EAP XP arrives users are strongly encouraged to upgrade to the new major version of the EAP XP that implements a more recent version of Eclipse MicroProfile.
Phase 2: Maintenance Support
Production support is provided according to the published Scope of Coverage and Service Level Agreement. Likewise, Development Support is provided according to the published Scope of Coverage and Service Level Agreement. During the maintenance phase, qualified security patches of Critical or Important impact, as well as select mission-critical bug-fix patches, will be released.
When a new EAP XP major version is released, Maintenance Support for the prior existing major version begins. It usually lasts for 12 weeks.
The following table details each type of software maintenance performed during a typical life cycle:
|Description||Full Support||Maintenance Support|
|Unlimited-incident technical support1||Yes||Yes|
|Access to Product Knowledgebase||Yes||Yes|
|Access to Product Downloads||Yes||Yes|
|Access to Product Discussions||Yes||Yes|
|Access to Support, Configuration and Troubleshooting Tools||Yes||Yes|
|Asynchronous Security Patches4||Yes||Yes|
|Asynchronous Bug-Fix Patches2||Yes||Yes|
|New Certifications (JVMs, DBs, etc.)||Yes||Yes|
- Full details of support services are provided as part of the Subscription Agreement.
- Red Hat can choose to address catastrophic issues with significant business impact for the customer through a hotfix, as a temporary measure while the bug-fix patch is being created. Subsequent asynchronous bug-fix patches will be based on and require the installation of updates that precede them.
- Major releases are the primary source for software enhancements. Rollups, updates, and patches are specifically reserved for bug fixes.
- Latest security update information available at: access.redhat.com/site/security/updates/.
Listed below are the life cycle dates for the currently supported Red Hat JBoss EAP XP Product Releases. Life cycle dates for EAP XP releases that have reached their end of support life can be found on the Archived JBoss Product Life Cycle Information page.