- What "RHCEAD Training" Actually Covers
- The Exam You Are Training For
- Training Paths: AD183, Self-Study and Lab Practice
- Domain-by-Domain Training Plan
- Stateless EJB Business Logic: The Skill Between the Lines
- Building a JBoss EAP 7 Lab Environment
- Sequencing Your Training Weeks
- Booking, Cost and Retake Mechanics
- After Training: Renewal and Career Context
- Frequently Asked Questions
- EX183 is a hands-on JBoss EAP 7 development exam, so training must be lab-based, not flashcard-based.
- Seven preparation domains: bean validation, JPA mapping, JPA query, messaging, JAX-RS, security and CDI.
- Stateless EJB business logic is also supported by the exam overview, so practice it alongside the seven domains.
- Configurations must persist after reboot, and only documentation shipped with JBoss EAP is available during the exam.
What "RHCEAD Training" Actually Covers
"RHCEAD" is the legacy and search label for what Red Hat now calls the Red Hat Certified Specialist in Enterprise Application Development. The credential is earned by passing exam EX183, and everything in your training should point at that one assessment. If you are still sorting out the terminology, the explainers at What Is RHCEAD? and What Does RHCEAD Stand For? cover the naming history, including why older pages still say "Developer" instead of "Specialist."
Training for this credential means building working Java EE code on JBoss Enterprise Application Platform 7 and getting fast at doing it under exam conditions. It does not mean memorizing definitions. The exam asks you to produce a configured, deployed, persistent result, so the best training mirrors that: you write entities, queries, endpoints, message consumers and security configuration, deploy them to a real EAP 7 instance, and verify they behave correctly.
The Exam You Are Training For
Understanding the format shapes how you train. EX183 is a performance-based assessment, not a multiple-choice question bank. You are given tasks, you implement them on a JBoss EAP 7 environment, and your finished configuration is evaluated. Two rules deserve special attention in your preparation:
- Persistence after reboot. Configurations must survive a restart. If you tweak something only in a running server's memory or forget to save a change to the persisted configuration, you can lose credit. Train yourself to verify by restarting the server.
- Restricted references. Internet access and candidate-supplied documentation are prohibited. Documentation shipped with JBoss EAP is supplied. That means your training should include working from the bundled docs, not from search results or bookmarked blog posts.
The current exam page does not state a duration, so confirm the timer on your booking rather than relying on a figure you heard elsewhere. Likewise, this article does not quote task counts or a pass mark, because they are not verified. For what is and is not known about scoring, see RHCEAD Passing Score, and for a realistic sense of difficulty, How Hard Is the RHCEAD Exam?
Training Paths: AD183, Self-Study and Lab Practice
There are no formal prerequisites for EX183 (details in RHCEAD Requirements). Red Hat's recommendations are practical rather than mandatory: solid Java SE knowledge, familiarity with JBoss Developer Studio on RHEL, and preparation through the related course, AD183. How you combine those depends on your background.
| Training Path | Best For | Main Strength | Main Risk |
|---|---|---|---|
| Instructor-led AD183 preparation | Developers new to JBoss EAP 7 or Java EE APIs | Structured coverage of the platform and guided labs | Passive attendance without independent repetition |
| Self-directed lab study | Java EE developers who already know the APIs | Flexible, cheap, and easy to repeat tasks until fluent | Gaps in domains you find boring or avoid |
| Hybrid (course plus independent labs) | Most candidates | Guided foundation plus the speed that only solo repetition builds | Spending too long on the course and too little on timed drills |
Whichever route you choose, treat course material as a map, not the territory. The exam rewards candidates who can do the work without a lab guide in front of them. Our broader RHCEAD study guide pairs well with this article if you want a first-attempt planning framework.
Domain-by-Domain Training Plan
Red Hat's EX183 objectives group the preparation topics into seven unweighted categories. "Unweighted" matters: there is no published percentage telling you which domain counts most, so training should leave no domain at the bottom of your priority list. For a deeper breakdown of each area, see RHCEAD Exam Domains: Complete Guide to All 7 Content Areas. Below is how to turn each into hands-on training.
Domain 1: Bean validation
Practice declaring and enforcing constraints on data objects so bad input is rejected consistently.
- Apply built-in constraint annotations to entity and DTO fields.
- Write a custom constraint annotation and its validator class.
- Trigger validation from JPA lifecycle events and from REST endpoints, then inspect the resulting violations.
- Customize violation messages and confirm they surface where you expect.
Domain 2: JPA mapping
Mapping is where Java objects meet relational tables, and mistakes here cascade into every query you write.
- Map entities with identifiers, column attributes and generation strategies.
- Model one-to-one, one-to-many, many-to-one and many-to-many relationships, including owning versus inverse sides.
- Understand fetch behavior and cascade options, and what each does to the generated SQL.
- Configure the persistence unit and datasource so deployment succeeds on EAP 7.
Domain 3: JPA query
Once entities map correctly, you must retrieve data precisely.
- Write JPQL queries with parameters, joins and ordering.
- Use named queries and the Criteria API, and know when each is the cleaner option.
- Handle result types: entities, scalar values and projections.
- Recognize and avoid common pitfalls such as lazy-loading outside a transaction.
Domain 4: Messaging
Asynchronous communication on EAP 7 combines code with server-side resource configuration.
- Create queues and topics in the server configuration and verify they persist across a restart.
- Write producers that send messages and message-driven beans that consume them.
- Understand the practical differences between point-to-point and publish-subscribe models.
- Practice injecting connection factories and destinations rather than looking them up manually.
Domain 5: REST services with JAX-RS
Expose business logic as HTTP resources.
- Define resource classes with path, method and media-type annotations.
- Bind path, query and header parameters and return meaningful status codes.
- Produce and consume JSON or XML and handle exceptions through mappers.
- Combine JAX-RS resources with validation and persistence so endpoints are genuinely end to end.
Domain 6: Security
Security tasks typically span both descriptors or annotations in code and server-side configuration.
- Protect web resources and EJB methods with role-based access.
- Configure a security domain and users and roles on the server, then confirm the settings survive a reboot.
- Test both permitted and denied access, not just the happy path.
- Know how declarative security (annotations and descriptors) differs from programmatic checks.
Domain 7: CDI
Contexts and Dependency Injection ties the rest of the application together.
- Inject beans using qualifiers to resolve ambiguity.
- Choose the right scope for a bean: request, session, application or conversation.
- Use producer methods, interceptors and events to decouple components.
- Diagnose unsatisfied and ambiguous dependency errors at deployment time.
Stateless EJB Business Logic: The Skill Between the Lines
The seven domains above are the issuer's preparation categories, but the exam overview and the credential competency list also explicitly support stateless EJB business logic. It is not presented as an eighth objective heading, yet it is the connective tissue in most realistic tasks: the REST resource calls a stateless session bean, which uses the entity manager, which is protected by role-based security and validated on input.
In training, build every mini-project around that layering. Write a stateless bean, inject a persistence context, expose it through a JAX-RS resource, validate its inputs, and secure its methods. When you practice domains in isolation, you will miss integration errors that only appear when the pieces meet, such as transaction boundaries, injection mismatches and classloading problems inside an EAR or WAR.
Building a JBoss EAP 7 Lab Environment
Because the exam runs on JBoss EAP 7, your practice environment should match it as closely as you can manage. Recommended characteristics of a good home lab:
- A genuine EAP 7 installation, not a different Java EE server. Behavior differences in configuration files and management tooling will cost you time on exam day.
- Familiarity with JBoss Developer Studio on RHEL, which Red Hat recommends, or an equivalent workflow you can reproduce quickly.
- Offline documentation habits. Practice looking things up in the documentation bundled with the product, with your browser disabled for anything else. Learn where the configuration reference and API details live.
- A restart discipline. After every configuration change, restart the server and confirm the change persisted. This one habit protects you from a common failure mode.
- A clean-slate routine. Periodically reset to a fresh workspace and rebuild a small application from nothing. Speed from a blank project is a different skill from editing something you wrote last week.
All of your practice material should be original. Write your own exercises and scenarios rather than hunting for leaked or reconstructed exam tasks. Beyond the ethical problem, they tend to be inaccurate and teach you to recognize tasks instead of solving them. If you want structured self-assessment, our practice test site offers original questions to check conceptual gaps before and between lab sessions.
Sequencing Your Training Weeks
This is the one place where a schedule is useful, and it is tied to how the domains depend on each other rather than to generic study theory. Foundations first, integration last:
JPA mapping and bean validation
- Entities, relationships and the persistence unit come first because every later domain leans on them.
- Add validation constraints early so they become habitual.
JPA query and stateless EJB logic
- Queries only make sense against working mappings.
- Wrap data access in stateless beans and test transactional behavior.
CDI and JAX-RS
- Wire beans together with injection and scopes.
- Expose the business layer as REST endpoints.
Messaging and security
- Both involve server-side configuration that must persist after reboot, so they reward careful, repeated drills.
- Secure your existing endpoints and add asynchronous processing.
Integrated builds under time pressure
- Rebuild a full multi-domain application from scratch with only bundled docs.
- Review weak spots and consult the RHCEAD cheat sheet for a final fact check.
Stretch or compress this to fit your experience. An experienced Java EE developer may need only the first and last weeks; someone newer to JPA or messaging may need to repeat the middle weeks.
Booking, Cost and Retake Mechanics
Training is easier to plan when you understand the logistics. The program-wide standard exam list price is USD 500, but the regional price shown in the booking cart controls, so treat that figure as a reference point and not a checkout quotation. A fuller discussion lives in RHCEAD Certification Cost.
- Delivery options. Remote, testing-center and classroom delivery are offered subject to availability. Remote candidates need LiveUSB, a successful compatibility test, and the required identity and hardware checks, so complete these well before exam day.
- Results. The program guide gives a results window of up to five business days. No shorter EX183-specific promise is made here.
- Retake. Eligible unsuccessful first individual attempts receive one free retake under Red Hat's training policies, subject to purchase or subscription eligibility periods and scheduling restrictions. Read the policy before relying on it.
- Scheduling. See RHCEAD Exam Dates for how to approach availability and booking windows.
Key Takeaway
Run the remote compatibility test and a full dry run of your hardware and environment days before the exam. Training time lost to a failed system check is the most avoidable setback in the whole process.
After Training: Renewal and Career Context
Certifications are current for three years. You can renew before expiry by retaking the original exam or by earning a qualifying same-level or higher-level credential under the current framework. For credentials earned before the May 11, 2026 framework change, Red Hat's FAQ indicates that updated renewal and mapping rules apply to the active transcript after you pass a new exam following that date. Be aware that Red Hat's standalone renewal page still uses older non-expiring terminology and narrower exam-only wording for specialist credentials. Rely on the current handbook, the dated framework and your active transcript rather than that legacy page alone.
On the career side, the skills you practice (JPA, JAX-RS, CDI, messaging, security, EJB) are standard enterprise Java competencies, so they are relevant wherever organizations run Java EE workloads on JBoss EAP. We deliberately avoid quoting earnings or hiring promises here, because no certification guarantees them. For evidence-based discussion, see RHCEAD Salary Guide, Is the RHCEAD Certification Worth It? and RHCEAD Jobs.
Frequently Asked Questions
No. There are no formal exam prerequisites. Red Hat recommends solid Java SE knowledge, familiarity with JBoss Developer Studio on RHEL, and AD183 preparation, but none of these are enforced at registration.
No. Internet access and candidate-supplied documentation are prohibited. Only documentation shipped with JBoss EAP is provided, so train by working from the bundled documentation.
No. EX183 is a hands-on enterprise Java development assessment on JBoss EAP 7. You implement and configure solutions, and your configurations must persist after a reboot.
Start with JPA mapping and bean validation, since later work depends on them. Move through JPA query, CDI and JAX-RS, then finish with messaging and security, where persistent server configuration matters most.
The overview articles RHCEAD Certification and What Is RHCEAD Certification? explain the credential, and the original-question practice test site helps you check your understanding between lab sessions.