Home » Java » Enterprise Java » Spring Boot / Java 8 / Tomcat 8 on Openshift with DIY

About Rafal Borowiec

Rafal Borowiec
Software developer, Team Leader, Agile practitioner, occasional blogger, lecturer. Open Source enthusiast, quality oriented and open-minded.

Spring Boot / Java 8 / Tomcat 8 on Openshift with DIY

DIY cartridge is an experimental cartridge that provides a way to test unsupported languages on OpenShift. It provides a minimal, free-form scaffolding which leaves all details of the cartridge to the application developer. This blog post illustrates the use of Spring Boot / Java 8 / Tomcat 8 application with PostgreSQL service bound to it.

Creating new application

Prerequisite

Before we can start building the application, we need to have an OpenShift free account and client tools installed.

Step 1: Create DIY application

To create an application using client tools, type the following command:

rhc app create boot diy-0.1

This command creates an application boot using DIY cartridge and clones the repository to boot directory.

Step 2: Add PostgreSQL cartridge to application

The application we are creating will use PostgreSQL database, hence we need to add appropriate cartridge to the application:

rhc cartridge add postgresql-9.2 --app boot

After creating the cartridge, it is possible to check its status with the following command:

rhc cartridge status postgresql-9.2 --app boot

Step 3: Delete Template Application Source code

OpenShift creates a template project that can be freely removed:

git rm -rf .openshift README.md diy misc

Commit the changes:

git commit -am "Removed template application source code"

Step 4: Pull Source code from GitHub

git remote add upstream https://github.com/kolorobot/openshift-diy-spring-boot-sample.git
git pull -s recursive -X theirs upstream master

Step 5: Push changes

The basic template is ready to be pushed:

git push

The initial deployment (build and application startup) will take some time (up to several minutes). Subsequent deployments are a bit faster, although starting Spring Boot application may take even more than 2 minutes on small Gear:

Tomcat started on port(s): 8080/http
Started Application in 125.511 seconds

You can now browse to: http://boot-yournamespace.rhcloud.com/manage/health and you should see:

{
    "status": "UP",
    "database": "PostgreSQL",
    "hello": 1
}

You can also browser the API. To find out what options you have, navigate to the root of the application. You should see the resource root with links to available resources:

{
  "_links" : {
    "person" : {
      "href" : "http://boot-yournamespace.rhcloud.com/people{?page,size,sort}",
      "templated" : true
    }
  }
}

Navigating to http://boot-yournamespace.rhcloud.com/people should return all people from the database.

Step 6: Adding Jenkins

Using Jenkins has some advantages. One of them is that the build takes place in it’s own Gear. To build with Jenkins, OpenShift needs a server and a Jenkins client cartridge attached to the application. Creating Jenkins application:

rhc app create ci jenkins

And attaching Jenkins client to the application:

rhc cartridge add jenkins-client --app boot

You can now browse to: http://ci-.rhcloud.com and login with the credentials provided. When you make next changes and push them, the build will be triggered by Jenkins:

remote: Executing Jenkins build.
remote:
remote: You can track your build at https://ci-<namespace>.rhcloud.com/job/boot-build
remote:
remote: Waiting for build to schedule.........

And when you observe the build result, the application starts a bit faster on Jenkins.

Under the hood

Why DIY?

Spring Boot application can be deployed to Tomcat cartridge on OpenShift. But at this moment no Tomcat 8 and Java 8 support exists, therefore DIY was selected. DIY has limitations: it cannot be scaled for example. But it is perfect for trying and playing with new things.

Application structure

The application is a regular Spring Boot application, that one can bootstrapped with http://start.spring.io. Build system used is Maven, packaging type is Jar. Tomcat 8 with Java 8 used. Spring Boot uses Tomcat 7 by default, to change it the following property was added:

<properties>
    <tomcat.version>8.0.9</tomcat.version>
</properties>

The Maven was selected, since currently only Gradle 1.6 can be used on OpenShift. This is due to a bug in Gradle. Gradle 2.2 fixes this issue.

Maven settings.xml

The settings.xml file is pretty important, as it contains the location of Maven repository: ${OPENSHIFT_DATA_DIR}/m2/repository.

On OpenShift, write permissions are only in $OPENSHIFT_DATA_DIR.

Data source configuration

The application uses Spring Data REST to export repositories over REST. The required dependencies are:

  • spring-boot-starter-data-jpa – repositories configuration
  • spring-boot-starter-data-rest – exposing repositoties over REST
  • hsqldb – for embedded database support
  • postgresql – for PostgreSQL support. Since currently OpenShift uses PostgreSQL 9.2, the appropriate driver’s version is used

Common properties – application.properties

By default (default profile, src/main/resources/application.properties), the application will use embedded HSQLDB and populate it with the src/main/resources/data.sql. The data file will work on both HSQLDB and PostrgeSQL, so we don’t need to provide platform specific files (which is possible with Spring Boot).

  • spring.datasource.initialize = true must be used, so Spring Boot picks up the data file and loads it to the database.
  • spring.jpa.generate-ddl = true makes sure that the schema will be exported.

OpenShift properties – application-openshift.properties

OpenShift specific configuration (src/main/resources/application-openshift.properties) allows the use of PostgreSQL service. The configuration uses OpenShift env variables to setup the connection properties:

  • $OPENSHIFT_POSTGRESQL_DB_HOST – for the database host
  • $OPENSHIFT_POSTGRESQL_DB_PORT – for the database port
  • $OPENSHIFT_APP_NAME – for the database name
  • $OPENSHIFT_POSTGRESQL_DB_USERNAME – for the database username
  • $OPENSHIFT_POSTGRESQL_DB_PASSWORD – for the database password

Spring allows to use env variables directly in properties with ${} syntax, e.g.:

spring.datasource.username = ${OPENSHIFT_POSTGRESQL_DB_USERNAME}

To let Spring Boot activate OpenShift profile, the spring.profiles.active property is passed to the application at startup: java -jar <name>.jar --spring.profiles.active=openshift.

Logging on OpenShift

The logging file will be stored in $OPENSHIFT_DATA_DIR:

logging.file=${OPENSHIFT_DATA_DIR}/logs/app.log

Actuator

Actuator default management context path is /. This is changed to /manage, because OpenShift exposes /health endpoint itself that covers Actuator’s /health endpoint .

management.context-path=/manage

OpenShift action_hooks

OpenShift executes action hooks script files at specific points during the deployment process. All hooks are placed in the .openshift/action_hooks directory in the application repository. Files must have be executable. In Windows, in Git Bash, the following command can be used:

git update-index --chmod=+x .openshift/action_hooks/*

Deploying the application

The deploy script downloads Java and Maven, creates some directories and exports couple of environment variables required to properly run Java 8 / Maven build.

The final command of the deployment is to run Maven goals:

mvn -s settings.xml clean install

Starting the application

When deploy script finishes successfully, the target directory will contain a single jar with the Spring Boot application assembled. The application is started and bound to the server address and port provided by OpenShift. In addition, the profile name is provided, so a valid data source will be created. The final command that runs the application:

nohup java -Xms384m -Xmx412m -jar target/*.jar --server.port=${OPENSHIFT_DIY_PORT} --server.address=${OPENSHIFT_DIY_IP} --spring.profiles.active=openshift &

Stopping the application

The stop script is looking for a Java process and when it finds it… you know what happens.

Summary

I am pretty happy with the evaluation of OpenShift with Do It Yourself cartridge. Not everything went smooth as I expected, mostly due to memory limitations on small Gear. I spent some time to figure it out and have proper configuration. But still, OpenShift with DIY is worth trying and playing with for a short while. Especially, that to get started is completely for free.

References

Reference: Spring Boot / Java 8 / Tomcat 8 on Openshift with DIY from our JCG partner Rafal Borowiec at the Codeleak.pl blog.
(0 rating, 0 votes)
You need to be a registered member to rate this.
3 Comments Views Tweet it!
Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
6. Spring Interview Questions
7. Android UI Design
and many more ....
I agree to the Terms and Privacy Policy

3
Leave a Reply

avatar
3 Comment threads
0 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
3 Comment authors
Sathish Kumarandkopei Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
newest oldest most voted
Notify of
kopei
Guest
kopei

I have followed the steps pretty good except changing postgreaql with mysql, and tried to deploy the application both local and on openshift, both times I had problems regarding logger. Below is the exception I get:

at org.springframework.boot.SpringApplication.run(SpringApplication.java:941)
remote: at demo.Application.main(Application.java:14)
remote: … 6 more
remote: Caused by: java.lang.ExceptionInInitializerError
remote: at org.apache.log4j.Logger.getLogger(Logger.java:40)
remote: at org.jboss.logging.Log4jLogger.(Log4jLogger.java:35)
remote: at org.jboss.logging.Log4jLoggerProvider.getLogger(Log4jLoggerProvider.java:33)
remote: at org.jb

and
Guest
and

I noticed that the “deploy” file points to a maven 3.2.3 binary, however this release has been removed from the mirror. you have to change it to 3.2.5:

http://mirror.cc.columbia.edu/pub/software/apache/maven/maven-3/3.2.5/binaries/apache-maven-3.2.5-bin.tar.gz

Sathish Kumar
Guest
Sathish Kumar

Thanks a lot !! very useful article