Jakarta EE Courses

Java Enterprise Edition (Jakarta EE or JEE) is a standard for developing large-scale Java applications with hundreds of thousands of simultaneous users. The Jakarta EE platform has Java Standard Edition (Java SE) as the underlying layer. Jakarta EE is implemented by application servers such as JBoss, WebLogic, GlassFish and Tomcat EE. SpiralTrain provides both basic classroom and advanced classroom training in Jakarta EE.

Visit our LinkedInFacebook or Instagram page for an impression of SpiralTrain. Click on the links below for more information about the courses and the schedule.

Jakarta EE Course List

Course Jakarta EE Overview
Jakarta EE Overview
Code: JEE100
First start: 25-06-2025
1 day € 749
Course Jakarta EE Web Component Development
Jakarta EE Web Development
Code: JEE200
First start: 17-06-2025
4 days € 2999
Course Jakarta EE Web Development with JSF
Jakarta EE Web Development with JSF
Code: JEE300
First start: 14-07-2025
4 days € 2999
Course Jakarta EE Web Services
Jakarta EE Web Services
Code: JEE400
First start: 24-06-2025
4 days € 2999
Jakarta EE EJB Business Components
Code: JEE500
First start: 28-07-2025
3 days € 2250
Course Jakarta EE Technologies
Jakarta EE Technologies
Code: JEE600
First start: 23-06-2025
5 days € 3299
Course Freemarker Templates
Freemarker Templates
Code: JEE210
First start: 23-06-2025
1 day € 699

Jakarta EE Platform

The Jakarta EE platform uses a multitiered distributed application model. This means application logic is divided into components according to function, and the various application components that make up a Jakarta EE application are installed on different machines depending on which tier in the multitiered Jakarta EE environment the application component belongs.

Jakarta EE Components

The Jakarta EE application parts are :

  1. Client tier components run on the client machine
  2. Web tier components run on the Jakarta EE server
  3. Business tier components run on the Jakarta EE server
  4. Enterprise information system (EIS) tier software runs on the EIS server

Jakarta EE Applicaties

Jakarta EE multitiered applications are generally considered to be three-tiered applications because they are distributed over three different locations: client machines, Jakarta EE server machine, and the database or legacy machines at the back-end. Three-tiered applications that run in this way extend the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage.

Web Components

Jakarta EE web components can be either JSP pages or servlets. Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documents that contain static content and snippets of Java programming language code to generate dynamic content. When a JSP page loads, a background servlet executes the code snippets and returns a response.

Business Components

Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans running in the business tier. An enterprise bean receives data from client programs, processes it and sends it to the enterprise information system tier for storage. An enterprise bean also retrieves data from storage, processes it, and sends it back to the client program.

Enterprise Beans

There are two kinds of enterprise beans: session beans and message-driven beans. A session bean represents a transient conversation with a client. When the client finishes executing, the session bean and its data are gone. A message-driven bean combines features of a session bean and a Java Message Service (JMS) message listener, allowing a business component to receive JMS messages asynchronously

Enterprise Information System Tier

The enterprise information system tier handles enterprise information system software, and includes enterprise infrastructure systems such as enterprise resource planning (ERP), mainframe transaction processing, database systems, and other legacy information systems. Jakarta EE application components might need access to enterprise information systems for database connectivity, for example.