Chapter 3. Get Started
3.1. Using the JBoss Web Server xPaaS Image Streams and Application Templates
The Red Hat xPaaS middleware images were automatically created during the installation of OpenShift along with the other default image streams and templates.
The JBoss Web Server xPaaS application templates are distributed as two sets: one set for Tomcat 7, and another for Tomcat 8.
3.2. Using the JBoss Web Server xPaaS Image Source-to-Image (S2I) Process
To run and configure the OpenShift JBoss Web Server xPaaS images, use the OpenShift S2I process with the application template parameters and environment variables.
The S2I process for the JBoss Web Server xPaaS images works as follows:
If there is a pom.xml file in the source repository, a Maven build is triggered with the contents of
By default the
packagegoal is used with the
openshiftprofile, including the system properties for skipping tests (
-DskipTests) and enabling the Red Hat GA repository (
The results of a successful Maven build are copied to /opt/webserver/webapps. This includes all WAR files from the source repository directory specified by the
$ARTIFACT_DIRenvironment variable. The default value of
$ARTIFACT_DIRis the target directory.
- All WAR files from the deployments source repository directory are copied to /opt/webserver/webapps.
All files in the configuration source repository directory are copied to /opt/webserver/conf.Note
If you want to use custom Tomcat configuration files, the file names should be the same as for a normal Tomcat installation. For example, context.xml and server.xml.