EuroAP is a middleware platform based on open standards. We offer two leading versions of the solution - EuroAP 6.x compliant with the Java ™ EE 6 specification and EuroAP 7.x compliant with the Java ™ EE 7 and Java ™ EE 8 specifications.
EuroAP has a modular structure, which makes it extremely flexible. The user can choose predefined sets of components (profiles) or create their own – unique, tailor-made for their applications. Below is a list of components available from EuroAP. The users do not have to be limited only to them, they can freely add their own modules.
Examples of components present in EuroAP and their application:
|It provides CLI (Command Line Interface), modular class loading and unified EuroAP management even in domain mode.
|It allows you to apply patches to the server and manage deployments and access control. It also allows you to see the health status of the server. The console works for both standalone and domain modes.
|A module implementing the Java™ Message Service 2.0 standard
|It is distinguished by excellent performance. In EuroAP, as in JBoss® EAP, it has been present from version 7 onwards.
|CDI (Context and Dependency Injection) implementing module for Java™ EE
|Provides dependency injection.
|Web server supporting Java ™ EE 7 requirements
|Supports network sockets. It has many improvements, including: NIO network container, load balancing, session management, HTTP port reduction (EuroAP 7 uses two – 9990 and 8080).
|A unified framework ensuring security
|It includes both the application server itself and the applications installed on it. Thanks to its architecture – it consists of many small components – it can be easily adapted to your needs. It allows you to replace default components with other implementations, including your own. Additionally, different components are treated as capabilities within the server, so that they can be mixed and merged together. In EuroAP present from version 7.1 onward.
|A set of components providing security in EuroAP 6x
|In version 7 it is present for the sake of compatibility.
|Load balancing module based on httpd
|In addition to the standard communication channels used to forward requests from httpd to the appropriate application server nodes, it uses an additional channel for feedback so that it can balance the load with some intelligence and respond to changes over the application lifespan. It can change its configuration dynamically.
|Alternative component for NIO
|It provides, among others an API that allows you to combine blocking and non-blocking operations, even within a single channel.
|Framework for Java™
|Used to map Java™ objects to a relational database and vice versa (ORM – Object-Relational Mapping).
|It stores data in the operating memory in the form of a key-value pair. It is most often used as a cache.
|Java™ EE Connector Architecture 1.7 implementing module
|Defines how the Enterprise Information System is to integrate with Java™ EE. In other words, how databases or messaging systems are to communicate with the application server.
|A set of tools for reliable messaging
|Allows you to manage the cluster (creating, destroying, joining and leaving clusters, detecting and reporting that a node has broken down/joined/left the cluster), and allows you to send and receive point-to-point and point-to-multi-point messages, that is, to send a message between nodes, as well as between a node and a cluster.
|Provides support for applications that use transactional protocols, such as: JTA, JTS, Web-Service Transations czy Rest Transations.
|Component supporting Enterprise Java™ Beans (EJB) 3.0
|Enterprise JavaBeans is a server-side component that encapsulates the business logic of an application. For example, in an inventory control application, EJB components can implement business logic in methods called checkInventoryLevel and orderProduct. By calling these methods, clients can access the inventory services provided by the application.
|Web services framework
|It provides all services necessary to ensure compatibility with Java™ EE 7. Components present in EuroAP right out of the box include: EuroWS API, EuroWS SPI, EuroWS Common, EuroWS Common Tools, EuroWS-CXF. The latter component provides excellent integration with Apache® CXF.
|Component responsible for the Virtual File System
|It makes each deployed application visible as a read-only hierarchical file system, regardless of whether the application is actually packed or not.
|Component that provides an API for serialization
|It includes improvements to the standard API while remaining fully compatible with java.io.
|Component responsible for handling logs in EuroAP
|It allows for advanced log management – their levels and methods of handling.
|Framework supporting developers in building web services
|It provides, among others, clear separation of the frontend part of the code, e.g. JAX-RS or JAX-WS from business logic or the ease and simplicity of creating new clients and endpoints.
EuroAP also includes many libraries directly supporting the building of Web Services.