Appendix A. Reference
A.1. Base layers Copy linkLink copied to clipboard!
Each base layer includes core functionality for a typical server user case.
datasources-web-server
This layer includes a servlet container and the ability to configure a datasource.
The following are the JBoss EAP subsystems included by default in the datasources-web-server:
-
core-management -
datasources -
deployment-scanner -
ee -
elytron -
io -
jca -
jmx -
logging -
naming -
request-controller -
security-manager -
transactions -
undertow
The following Jakarta EE specifications are supported in this layer:
- Jakarta JSON Processing
- Jakarta JSON Binding
- Jakarta Servlet
- Jakarta Expression Language
- Jakarta Server Pages
- Jakarta Standard Tag Library
- Jakarta Concurrency
- Jakarta Annotations
- Jakarta XML Binding
- Jakarta Debugging Support for Other Languages
- Jakarta Transactions
- Jakarta Connectors
jaxrs-server
This layer enhances the datasources-web-server layer with the following JBoss EAP subsystems:
-
jaxrs -
weld -
jpa
This layer also adds an Infinispan-based second-level entity with local caching to the container.
The following Jakarta EE specifications are supported in this layer in addition to those supported in the datasources-web-server layer:
- Jakarta Contexts and Dependency Injection 2.0
- Jakarta Bean Validation 2.0
- Jakarta Interceptors 1.2
- Jakarta RESTful Web Services 2.1
- Jakarta Persistence 2.2
cloud-server
This layer enhances the jaxrs-server layer with the following JBoss EAP subsystems:
-
resource-adapters -
messaging-activemq(remote broker messaging, not embedded messaging)
This layer also adds the following observability features to the jaxrs-server layer:
- Native Health
- Native Metrics
The following Jakarta EE specification is supported in this layer in addition to those supported in the jaxrs-server layer:
- Jakarta Security 1.0
cloud-default-config
This layer provisions a server with server configuration based on standalone-ha.xml and includes the subsystem configuration messaging-activemq. On the contrary, the modcluster and core-management subsystems configuration are not included. This is configured to be used in the cloud. Additionally, all JBoss EAP server JBoss modules will be installed.
The cloud-default-config layer is defined by the eap-cloud-gallen-pack, which is only available on OpenShift Container Platform.
ee-core-profile-server
The ee-core-profile-server layer provisions a server with the Jakarta EE 10 Core Profile. The Core Profile provides a small, lightweight profile for users that provides both core JBoss EAP server functionality and Jakarta EE APIs. The ee-core-profile-server layer is best suited for smaller runtimes such as cloud-native applications and microservices.
You can also create custom layers. For more information, see Provisioning user-developed layers in JBoss EAP.
A.2. Supported Galleon layers for different deployment contexts Copy linkLink copied to clipboard!
While most Galleon layers are supported on both bare metal and OpenShift Container Platform deployments, some are specific to the deployment contexts. The following tables describe what layers are supported in deployment contexts.
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| datasources-web-server | Base | A servlet container with support for datasources. | Yes | Yes | Yes |
| jaxrs-server | Base |
An extension of the | Yes | Yes | Yes |
| cloud-server | Base |
An extension of the | Yes | Yes | Yes |
| ee-core-profile-server | Base | A Jakarta EE Core Profile server. | Yes | Yes | Yes |
| observability | Decorator | Support for MicroProfile monitoring features. | Yes | Yes | Yes |
| web-clustering | Decorator | Support for distributable web applications. Configures a non-local Infinispan-based container web cache for data session handling suitable to clustering environments. | Yes | Yes | Yes |
| ejb | Decorator | Support for Jakarta Enterprise Beans, excluding the IIOP protocol. | Yes | Yes | Yes |
| ejb-lite | Decorator | Support for Jakarta Enterprise Beans Lite. | Yes | Yes | Yes |
| ejb-local-cache | Decorator | Infinispan-based local cache for stateful session beans. | Yes | Yes | Yes |
| ejb-dist-cache | Decorator | Infinispan-based distributed cache for stateful session beans. | Yes | Yes | Yes |
| elytron-oidc-client | Decorator | Provides a native OIDC client in JBoss EAP to connect with OpenID providers. | Yes | Yes | Yes |
| embedded-activemq | Decorator |
Support for an embedded Apache Activemq Artemis Jakarta Messaging broker. Alternative to the | Yes | No | Yes |
| jdr | Decorator | Support for the JBoss Diagnostic Reporting (JDR) subsystem. | Yes | Yes | Yes |
| jpa | Decorator |
Support for JPA (using the latest JBoss EAP supported Hibernate release). Alternative: | Yes | Yes | Yes |
| jpa-distributed | Decorator | Support for JPA with a distributed second level cache. Alternative: jpa | Yes | Yes | Yes |
| jsf | Decorator | Support for Jakarta Faces. | Yes | Yes | Yes |
| remote-activemq | Decorator | Support for connections to a remote Apache Activemq Artemis Jakarta Messaging broker. Alternative: embedded-activemq | Yes | Yes | Yes |
| web-console | Decorator | Support for loading the HAL web console from the /console context on the HTTP management interface. Not required to use a HAL console obtained independently and configured to connect to the server. | Yes | Yes | Yes |
| webservices | Decorator | Support for Jakarta XML Web Services. | Yes | Yes | Yes |
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| cloud-default-config | Base | Provisions a server with server configuration based on standalone-ha.xml and includes the subsystem configuration messaging-activemq. | Not applicable | Not applicable | Yes |
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| myfaces | Decorator |
Provides | Yes | Yes | Yes |
The feature-pack only provides MyFaces-specific integration classes and not the MyFaces artifacts. You must specify the Maven artifact version for MyFaces by either using the environment variable MYFACES_VERSION or system property org.jboss.eap.jsf.myfaces.version. You can find the version for org.apache.myfaces.core:myfaces-impl, which is the groupID:artifactID for MyFaces, at Apache MyFaces Core 4.1 Impl.
During provisioning, the MyFaces artifacts will be retrieved from a Maven repository. If the MyFaces artifacts for the given version are not present in the repository, or you do not specify the version, the provisioning will fail. Also, if the MyFaces version is not Jakarta EE-compatible, provisioning will succeed, but the deployment will fail due to missing classes.
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| keycloak-saml | Decorator |
Use this layer for Source to Image (s2i) with automatic registration of the SAML client. You must use this layer along with the | No | No | Yes |
| keycloak-client-saml | Decorator |
Use this layer for web-applications on bare metal, and for Source to Image (s2i) with | Yes | Yes | No |
| keycloak-client-saml-ejb | Decorator | Use this layer for applications where you want to propagate identities to Jakarta Enterprise Beans. | Yes | Yes | No |
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| postgresql-driver | Decorator |
This installs a JBoss EAP module for the PostgreSQL driver and adds a driver resource to the | Yes | Yes | Yes |
| postgresql-datasource | Decorator |
This is built upon the | Yes | Yes | Yes |
| mssql-driver | Decorator |
This installs a JBoss EAP module for the Microsoft SQL server driver and adds a driver resource to the | Yes | Yes | Yes |
| mssql-datasource | Decorator |
This is built upon the | Yes | Yes | Yes |
| oracle-driver | Decorator |
This installs a JBoss EAP module for the Oracle database driver and adds a driver resource to the | Yes | Yes | Yes |
| oracle-datasource | Decorator |
This is built upon the | Yes | Yes | Yes |
No specific driver version is included in the feature-pack. Before you provision your server, you have to specify the driver version.
Example
POSTGRESQL_DRIVER_VERSION="42.2.19"- The driver-specific environment variables are defined within their specific driver documentation.
For more information, see the following resources:
JBoss EAP XP-specific layers
This following feature-packs and layers are only available with JBoss EAP XP.
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| microprofile-platform | Decorator | This layer includes MicroProfile capabilities:
| Yes | Yes | Yes |
| microprofile-lra-coordinator | Decorator | Provides MicroProfile Long Running Actions (LRA) capability and MicroProfile LRA coordinator. The MicroProfile LRA coordinator is responsible for starting, managing, and recovery of the LRAs. | Yes | Yes | Yes |
| microprofile-lra-participant | Decorator | Provides MicroProfile Long Running Actions (LRA) capability and the client library used in user deployments to participate in the distributed MicroProfile LRAs, and define compensation and completion callbacks. | Yes | Yes | Yes |
| microprofile-reactive-messaging-kafka | Decorator | This layer provides MicroProfile Reactive Messaging capability along with an Apache Kafka connector to integrate MicroProfile Reactive Messaging with external messaging systems. | Yes | Yes | Yes |
| microprofile-reactive-messaging-amqp | Decorator | This layer provides MicroProfile Reactive Messaging capability along with an Advanced Message Queuing Protocol (AMQP) connector to integrate MicroProfile Reactive Messaging with external messaging systems. | Yes | Yes | Yes |
| Layer | Type | Description | Bare metal | Bare metal bootable JAR | OpenShift Container Platform |
|---|---|---|---|---|---|
| cloud-default-mp-config | Base |
This layer provisions a server with standalone configuration based on the This layer is only available with JBoss EAP XP. | No | No | Yes |
A.3. JBoss EAP Maven plug-in configuration parameters Copy linkLink copied to clipboard!
You can configure the eap-maven-plugin Maven plug-in by setting the following list of configuration parameters.
| Name | Type | Description |
|---|---|---|
| bootable-jar | boolean |
Set the value to |
| bootable-jar-install-artifact-classifier | String | When <bootable-jar> is set to true, the bootable JAR artifact is attached to the project with the classifier 'bootable'. Use this parameter to configure the classifier. |
| bootable-jar-name | String |
Set the name to be used for the jar file when the |
| channels | List | A list of channel YAML file references. A channel file contains the versions of the JBoss EAP server artifacts. There are two ways to identify a channel YAML file.
|
|
| List |
A list of Galleon layers to exclude. You can use it when |
|
| List | A list of directories from which content is copied to the provisioned server. You can use either the absolute path to the directory or the relative path. The relative path must be relative to the project base directory. |
|
| List |
A list of feature-pack configurations to install, which you can combine with layers. Use the system property |
|
| String |
The file name of the application to deploy. The default value is |
|
| Map |
When provisioning the server, you can set specific Galleon options. If you are building a large number of servers in the same Maven session, you must set
|
|
| List |
A list of Galleon layers to provision. You can use it when |
|
| String |
A name of the configuration file generated from layers. The default value is |
|
| boolean |
Specifies whether to log the provisioning time at the end of the provisioning. The default value is |
|
| String | A name used for the deployment. |
|
| boolean |
Specifies whether to use offline mode when the plug-in resolves an artifact. In offline mode, the plug-in uses the local Maven repository for artifact resolution. The default value is |
|
| boolean |
If you want to delete the existing server referenced from the |
|
| List | A list of CLI scripts and commands to execute. If a script file is not absolute, it must be relative to the project base directory. Configure the CLI executions in the following way:
|
|
| String |
Path to the directory in which to provision the server. It can be an absolute path or a path relative to the |
|
| File |
The path to the |
|
| boolean |
Specifies whether to record the provisioning state in |
|
| String |
The runtime-name of the deployment. The default value is the deployment file name, such as |
|
| String |
The name of the server configuration to use during deployment. The deployment is deployed inside the configuration referenced from |
|
| boolean |
If you want the goal to be skipped, set it to |
|
| boolean |
Set the value to Note
To package a server as a hollow bootable JAR, a bootable JAR without any application, set this to
The default value is |
|
| String |
Indicates how
|
| Name | Type | Description |
|---|---|---|
| channels | List | A list of channel YAML file references. A channel file contains the versions of the JBoss EAP server artifacts. There are two ways to identify a channel YAML file.
|
|
| List |
A list of Galleon layers to exclude. You can use it when |
|
| List |
A list of feature-pack configurations to install, which you can combine with layers. Use the system property |
|
| Map |
When provisioning the server, you can set specific Galleon options. If you are building a large number of servers in the same Maven session, you must set
|
|
| List |
A list of Galleon layers to provision. You can use it when |
|
| String |
A name of the configuration file generated from layers. The default value is |
|
| boolean |
Specifies whether to log the provisioning time at the end of the provisioning. The default value is |
|
| boolean |
Specifies whether to use offline mode when the plug-in resolves an artifact. In offline mode, the plug-in uses the local Maven repository for artifact resolution. The default value is |
|
| boolean |
If you want to delete the existing server referenced from the |
|
| String |
Path to the directory in which to provision the server. It can be an absolute path or a path relative to the |
|
| File |
The path to the |
|
| boolean |
Specifies whether to record the provisioning state in |
|
| boolean |
If you want the goal to be skipped, set it to |
A.4. Bootable JAR arguments Copy linkLink copied to clipboard!
View the arguments in the following table to learn about supported arguments for use with the bootable JAR.
| Argument | Description |
|---|---|
|
| Displays the help message for the specified command and exit. |
|
| Specifies the path to a JBoss CLI script that executes when starting the bootable JAR. If the path specified is relative, the path is resolved against the working directory of the Java VM instance used to launch the bootable JAR. |
|
| Argument specific to the hollow bootable JAR. Specifies the path to the WAR, JAR, EAR file or exploded directory that contains the application you want to deploy on a server. |
|
| Print the content of the generated Galleon configuration file. |
|
|
By default, the JVM settings are used to create a TEMP directory after the bootable JAR is started. You can use the |
|
| Runs the server with a security manager installed. |
|
|
Set system property |
|
|
Set system property |
|
| Specifies system properties that are set by the server at server runtime. The bootable JAR JVM does not set these system properties. |
|
| Loads system properties from a specified URL. |
|
| Set a security property. |
|
|
Set system property |
|
| Display the application server version and exit. |