Chapter 3. Deploying an application to the server

Procedure

1. Move the application to your local Git repository, if it already is not in it.

   $ mv -r helloworld/ <your_git_repo>

2. Define the following property in the pom.xml configuration file:

   <properties>
       ...
       <version.plugin.eap>1.0.0.Final-redhat-00013</version.plugin.eap> 

   1

   
   </properties>

   1

   <version.plugin.eap> defines the version for JBoss EAP Maven plug-in.

3. Add the JBoss EAP maven plugin to <pluginManagement>, in <build> section inside the <project> section.

   <project>
       ...
       <build>
           <pluginManagement>
               <plugins>
                   ...
                   <plugin>
                       <groupId>org.jboss.eap.plugins</groupId>
                       <artifactId>eap-maven-plugin</artifactId>
                       <version>${version.plugin.eap}</version>
                   </plugin>
               </plugins>
           </pluginManagement>
       </build>
   </project>

4. Create a profile "openshift" in the pom.xml configuration file.

   This profile defines the plug-ins, feature packs, and layers required for deployment on OpenShift Container Platform.

   <profiles>
       <profile>
           <id>openshift</id>
           <build>
               <plugins>
                   <plugin>
                        <groupId>org.jboss.eap.plugins</groupId>
                        <artifactId>eap-maven-plugin</artifactId>     

   1

   
                        <configuration>
                            <channels>
                                <channel>
                                    <manifest>
                                        <groupId>org.jboss.eap.channels</groupId>
                                        <artifactId>eap-8.0</artifactId>
                                    </manifest>
                                </channel>
                            </channels>
                            <feature-packs>
                                <feature-pack>                            

   2

   
                                    <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>
                            <layers>                                      

   3

   
                                <layer>cloud-server</layer>
                            </layers>
                            <name>ROOT.war</name>                         

   4

   
                        </configuration>
                        <executions>
                            <execution>
                                <goals>
                                    <goal>package</goal>
                                </goals>
                            </execution>
                        </executions>
                   </plugin>
               </plugins>
           </build>
       </profile>
   </profiles>

   1

   wildfly-maven-plugin is a JBoss EAP plug-in for provisioning a JBoss EAP instance, with the application deployed, on OpenShift Container Platform.

   2

   feature-packs defines the feature-packs (zipped files that contains features to dynamically provision a server). In this case we need the feature-packs org.wildfly:wildfly-galleon-pack and org.wildfly.cloud:wildfly-cloud-galleon-pack.

   3

   layers defines the layers (from the configured feature-packs) to include in the provisioned server. Each layer identifies one or more server capabilities that can be installed on its own, or in combination with other layers. In our case we opt for the cloud-server layer, which provisions just the basic features of JBoss EAP, well suited for a cloud server.

   4

   <name>ROOT.war</name>: Defines the resulting name of the application’s web archive (WAR). If ROOT.war is specified then the application is deployed at the root path of the server, otherwise it is deployed at <name/> relative path.

5. Verify that the applications compiles.

   $ mvn package -Popenshift

6. Push the changes to your repository.

Procedure

1. Create a directory called charts in the application root directoy and navigate to it. Application root directory is the one that contains pom.xml configuration file.

   $ mkdir charts; cd charts

2. Create a file helm.yaml with the following content:

   build:
     uri: https://github.com/<user>/<repository>.git     

   1

   
     ref: <branch_name>                                  

   2

   
     contextDir: helloworld                              

   3

   
   deploy:
     replicas: 1                                         

   4

   1

   Specify the URL for your Git repository that contains the application to deploy on OpenShift Container Platform.

   2

   Specify the Git branch that contains your application.

   3

   Specify the directory containing the application.

   4

   Specify the number of pods to create.

3. Configure the JBoss EAP repository in Helm.

   • If you haven’t added the JBoss EAP repository to Helm before, add it.

     $ helm repo add jboss-eap https://jbossas.github.io/eap-charts/

   • If you already have added the JBoss EAP repository to Helm, update it.

     $ helm repo update jboss-eap

4. Deploy the application using helm.

   $ helm install helloworld -f helm.yaml jboss-eap/eap8

   The deployment can take a few minutes to complete.

Verification

1. Get the URL of the route to the deployment.

   $ APPLICATION_URL=https://$(oc get route helloworld --template='{{ .spec.host }}') &&
   echo "" &&
   echo "Application URL: $APPLICATION_URL"

2. Navigate to the "Application URL" in a browser.

   You are redirected to the servlet at path "/HelloWorld" and you get the following message:

   Hello World!