OpenShift Decision Service How To

This is a series of 3 videos showing the necessary steps to have a complete source-to-production BRMS and OpenShift Decision Service configuration.

These videos talk about the steps needed to push the changes made using BRMS Workbench to GitHub, the creation of the Decision Service on OpenShift, and also the configuration of the GitHub webhook in OpenShift.
With these three steps, changes made in BRMS will kick-of a new build and deploy on OpenShift with no human interaction. This demo also uses the lates 3.1.1 version of OpenShift, so you'll see new features like the build trends chart, and the ability to edit configuration in the UI.

How to create a hook from BRMS to GitHub

This first video shows you how a simple hook can be added to your BRMS .niogit repo so it can push changes to GitHub.

How to create a hook from BRMS to GitHub

The next video shows how you can create an OpenShift Decision Service.
The OpenShift Decision Service is a rules optimized service specially created to facilite making changes to your business rules without changing your application code. More details can be found here: Middleware Services for OpenShift and here: Red Hat JBoss BRMS.
This video also covers adding a Maven proxy to your build configuration. The steps used to create, configure and run a maven proxy on OpenShift were taken from the post Improving Build Time of Java Builds on OpenShift.

Adding the GitHub Webhooks and testing the full integration

The last step is the simplest one. You need only to create a webhook on GitHub with the information you can easily get from the Build Configuration option in the OpenShift UI.

The result is that you have a complete code-to-production using both BRMS and OpenShift. This allows developers to continue using the BRMS Workbench to develop the rules, taking advantage of all the BRMS features, and when it's time to execute those rules, they become an independent scalable decision service on OpenShift.
I hope you enjoy the ride!