Chapter 1. Basics of server provisioning
When you do not need all the capabilities of a JBoss EAP server, you can provision a JBoss EAP server with only the required capabilities, instead of installing the complete JBoss EAP server. By provisioning a server with only the required capabilities, you reduce the memory footprint of the server and also its security exposure. You can use a provisioned server both on bare metal and OpenShift Container Platform.
1.1. Composition of a provisioned server Copy linkLink copied to clipboard!
Server provisioning makes use of Galleon tooling and provisions a server based on three main elements:
- Galleon layer
- A Galleon layer provides a set of subsystems and Jakarta EE technologies. A provisioned server is composed of one or more Galleon layers.
- Galleon feature-pack
- A Galleon feature-pack contains a set of Galleon layers. You can choose which Galleon layer you want to include and exclude when provisioning a server.
- Channel
- A channel contains all the Maven coordinates of the server artifacts and Galleon feature-packs.
1.2. Ways of provisioning a JBoss EAP server Copy linkLink copied to clipboard!
You can provision a JBoss EAP server in the following ways:
- By using the
jboss-eap-installation-manager Use the
jboss-eap-installation-managerto install a server with only the required components.For more information, see Installing JBoss EAP using the jboss-eap-installation-manager.
- By using the JBoss EAP Maven plug-in
Use the JBoss EAP Maven plug-in,
eap-maven-plugin, when you want to use Maven tooling to provision a server. Typically, you would use the Maven plug-in when you want to package an application in a provisioned server. However, you can provision a server without packaging an application as well. Also, you can package the provisioned server as a bootable JAR. You can use the JBoss EAP Maven plug-in for both bare metal and OpenShift Container Platform source-to-image (S2I) use.For more information, see Provisioning a server by using the JBoss EAP Maven plug-in.