Skip to content

Latest commit

 

History

History
39 lines (29 loc) · 1.49 KB

index.md

File metadata and controls

39 lines (29 loc) · 1.49 KB
Raw

Building an EAP server for the Cloud

In order to provision an EAP server for the Cloud, you have first to integrate the EAP Maven plugin into the pom.xml file of your project.

The "package" goal of the plugin allows you to:

  • Provision an EAP server tailored to your needs.
  • Incorporate custom content (keystores, properties files, ...).
  • Execute CLI scripts to configure the EAP server.
  • Deploy your application in the provisioned server.

The generated server is then ready to be installed inside a Docker Image to be deployed in your cluster.

Provisioning with the cloud feature-pack

The cloud feature-pack is to be provisioned along with the EAP Galleon feature-pack. This is configured in the feature-packs configuration option of the EAP Maven plugin.

For example:

<feature-packs>
  <feature-pack>
    <location>org.jboss.eap:wildfly-ee-galleon-pack</location>
  </feature-pack>
  <feature-pack>
    <location>org.jboss.eap.cloud:eap-cloud-galleon-pack</location>
  </feature-pack>
</feature-packs>

Specifics of the eap-cloud-galleon-pack

When using the cloud galleon feature-pack, the following content will get provisioned:

  • Server startup scripts.
  • Automatic adjustment of EAP Galleon layers to cope with the cloud execution environment.
  • Automatic provisioning of the health subsystem allowing for server state monitoring (Liveness and Readiness probes).
  • Automatic routing of server logs to the console