JBoss EAP, step by step: understand the container, deployment, and transactions
After running a Boot API with java -jar, enterprise work introduces JBoss, EARs, MDBs, JNDI, and XML. The next question is ownership: which responsibilities belong to the application, and which belong to the container? Follow deployment and resources before memorizing configuration files.
Match the names: JBoss, WildFly, EAP
JBoss is often a historical or family shorthand, so “deploy to JBoss” is not a version specification. WildFly is the community application-server project; EAP is Red Hat’s integrated and supported enterprise product based on community work. Their release numbers are not interchangeable. Identify the product and update level before applying an example.
This course uses EAP 8.1, Jakarta EE 10, and the Java 21 migration scenario; sources were checked on October 4, 2026. Exact JDK vendor, OS, EAP update, MQ, and DB2 combinations still require vendor matrices. This is a learning series, not certification or an enterprise integration sign-off.
Six responsibilities to learn next
| Lesson | Question | Exercise output |
|---|---|---|
| 01 Modes | Which server did I connect to? | Mode and management map |
| 02 Deployment | Uploaded WAR versus usable API? | Artifact-to-URL path |
| 03 Modules | Why is a class missing despite a JAR? | Library ownership map |
| 04 Data | Does JNDI lookup prove a transaction? | Data-source and transaction boundary |
| 05 Messaging | Who owns commit and redelivery? | MQ/DB failure cases |
| 06 Evidence | What establishes migration parity? | One complete comparison case |
Keep three kinds of evidence separate
Offline exercises identify declarations in synthetic XML. Management CLI reads a specific instance’s model or runtime. Business cases observe HTTP, DB, MQ, and logs. These answer different questions: an enabled="true" declaration does not establish that a WAR is running or handling orders without duplicates.
The kit includes no EAP, MQ, DB2, or corporate credentials. Its Python tool reads selected fields, and the synthetic XML uses teaching namespaces that must not be deployed. With a training environment, collect the management evidence described in each lesson after confirming the instance and permissions.
Connecting the Spring Boot series
Controllers, services, and injection remain application concerns. EAP adds external HTTP hosting, deployment, modules, and enterprise-resource management. Keep EJB, CDI, and Spring lifecycles distinct. If the request-to-service path is still unclear, review Boot lessons 1 and 2 before deployment.
Return to Spring Boot, step by stepDownload the EAP offline kit: inventory, exercises, workbookNext: 01: Servers, modes, managementPractical lesson 07: run the migration comparison labLesson 08: build and inspect a Spring Boot WARLesson 09: Spring XML and transaction comparisonLesson 10: MDB and redelivery model