How To Import Any JBoss BRMS Example Project

This tips & tricks comes to you after I have been asked the following repeatedly over the last few weeks by users of the JBoss BRMS demos:

“How can I import the projects associated with the various JBoss BRMS demo projects into my own existing installation?”

What this means is that users want to have an example project in their personal installation of the product without using the projects installation process. This is certainly possible but not totally obvious to everyone.

Below I will walk you through how the various example projects for JBoss BRMS are setup, how the actual rules projects are loaded into JBoss BRMS when you set them up and why. After this I will show you how to extract any of the available rules projects for importing in to any previously installed JBoss BRMS server.

Figure 1: In JBoss BRMS open the Administration
perspective with menu options, Authoring -> Administration.

Background on how it works

The normal installation of a JBoss BRMS demo project that I have provided uses a template. This template ensures that the process is always the same; download, unzip, add products and run the installation script. After doing this, you are done, just fire up the JBoss BRMS for the adjusted experience where you open up the Authoring perspective to a pretty process designer with the demo project displayed for you to kick off a demo run.

These projects have a demo template that provides some consistency and you can read about how it works in a previous article.  For the initial installation run of any of these demo projects, a folder is copied from support/brms-demo-niogit to the installation at the location target/jboss-eap-{version}/bin/.niogit. 

Figure 2: To import a new project, open the Clone repository
from the menu Repositories. This will allow you to bring
in any rules project to your JBoss BRMS.

This folder contains all of the project and system Git repositories that are formatted for the version of the project you have downloaded. By installing this directory or complete repository, when JBoss BRMS starts up the first time, it will pick up the state I left it in when designing the experience around you using this demo project.

Get your hands on a specific rules project

The problem I want to help you with in this article is to show you how to extract only the rules project from one of these examples and import this into your own installation of JBoss BRMS.

Figure 3: Cloning a repository is how you import an
existing project, which requires the 
information shown.

The following list is the order you do the tasks, after which I will explain each one:

  1. Download any JBoss BRMS demo project and unzip (or clone it if you like).
  2. Log in to your own JBoss BRMS and open Administration perspective via menu: Authoring -> Administration.
  3. Setup the new rules project you want to import: Repositories -> Clone repository -> fill in details including import project URL
  4. Explore the new project in the Authoring perspective: Authoring -> Project Authoring
I am going to assume you can find a JBoss BRMS demo project of your liking from the link provided in step 1 and download or clone to your local machine.

I will be using the JBoss BRMS Cool Store Demo as the example project you want to import into your current JBoss BRMS installation instead of leveraging the standalone demo project.

In your current installation where you are logged in,  open the Administration perspective as shown in figure 1 by menu options Authoring -> Administration. This allows you to start importing any existing rules project. We will be importing the Cool Store rules project by using the feature to clone existing projects found in menu options, Repositories -> Clone repository as shown in figure 2.

Figure 4: Once the project has been imported (cloned), you
will receive this message in a pop-up.
This will produce a pop-up that asks for some information about the project to be imported, which you can fill in as listed below and shown in figure 3:
  • Repository Name: retail
  • Organizational Unit: Demos    (select whatever org you want to use from your system)
  • Git URL:  file:///[path-to-project-you-downloaded]/brms-coolstore-demo/support/brms-demo-niogit/coolstore-demo.git
Figure 5: Explore your newly imported rules project in the
authoring perspective within your JBoss BRMS installation.

The most interesting bit here is the Git URL, which is normally something hosted online, but this project we want to import is positioned locally in our filesystem, so we use a file based URL to point to it. Click on Clone button to import the project and you should see a pop-up that looks like figure 4 stating that you have successfully imported your project.

Now you can explore the new imported project in your authoring perspective and proceed as you desire with this project as shown in figure 5. This will work for any project I have put together for the field that is based on the standard template I use.

I hope this tips & tricks helps you to explore and enjoy as many of the existing rules examples offered in the current collection of demo projects.

 

See more by Eric D. Schabell, contact him on Twitter for comments or visit his home site.

Upcoming: Webinar on Design Approaches for Business Automation

Justin Holmes is a business automation practice lead with Red Hat. It is essentially his job to come up with practical solutions to business problems. He is conducting a webinar next week to go over design practices to more effectively develop and deliver software products, with a heavy emphasis using business rules and process automation to make testing and deploying software more controlled and easier. This webinar will look at two historically separate development processes — engineering-driven development and business rules-driven automation — and how it is possible to develop a design model using the strengths of both.

He has more details on the Services Speaks blog.

register_now

This event is free. It will be Tuesday, July 12, at 11am Eastern time.

And the Winner Is…

The comparison between the bag of cash representing a MINI Cooper S and Red Hat JBoss Enterprise Application Platform 7 is kind of fun. JBoss EAP 7 — like a MINI Cooper S — is small, agile, fast, and fits easily in appropriately-sized containers.

car

As part of this year’s Red Hat Summit — and to celebrate the release of JBOss EAP 7 — the Red Hat Middleware group held a drawing for a (metaphorical) bagful of cash equal to the value of a 2016 MINI Cooper S ($24,950 as of June 1, 2016). Anyone at Summit (who is not a Red Hat employee or relative) could enter the drawing.

And the drawing was last night! The winner is … drumroll ….

RYAN THAMES.

IMG_2015

Congratulations, Ryan!

Thank you to everyone who participated and who has visited the booth so far during Summit. It has been quite a ride this week.

WP_20160630_09_09_04_Pro

Left to right, Craig Muzilla, senior vice president of Application Platforms Business; Ryan Thames (winner); and Mark Little, CTO of JBoss middleware.

For reference….

The terms and conditions for this contest are available at https://www.redhat.com/files/resources/car-giveaway-contest-terms-conditions.pdf.

Mike Piech and Rich Sharples on Facebook LIVE from Red Hat Summit

Rich Sharples, senior director of product management, and Mike Piech, vice president of marketing, got together for a half hour at the end of the Summit day today to discuss some of the major issues that have come out related to middleware this week. There have been some major announcements: the new microprofile project, the release of Red Hat JBoss EAP 7, the growth of microservices, and the recent acquisition of 3scale and what that means for API management in Red Hat Middleware.

As a quick summary, two of the major themes underscoring a lot of the announcements around JBoss, middleware, and Java this week relate to things that are micro: microservices and microprofile.

Microservices has been a subtext in many of the JBoss EAP 7 sessions and in the OpenShift sessions because this containerized, immutable, consistent environment is what makes microservices possible.Containers fundamentally enable microservices. You have an underlying runtime that is commensurate with the idea of “micro.” You can scale elastically, add instances to scale up and down. The opportunity to change things as an application travels from the desktop to the data center is much less. These are communicating systems, and that’s what container orchestration is. It coordinates these complex webs. we’re The application is the only thing that matters. Operations is there to support the application. I hit a build button and it goes through my CI/CD system, and it’s the same configuration in the environment.

However, like any application or project architecture, it’s more than “JBoss + OpenShift  = awesome microservices.” There has to be consideration and weight given to the application and the underlying technology to find a structure that fits. Microservices architecture isn’t about taking everything you’ve got and decomposing it into atomic services. It’s about having a range of sizes and services, depending on what you need. It is important to be conscious of the trade-offs that come from the increased complexity of the system. It really depends on the organization and the technology platforms they have what architecture is appropriate.

That need to understand and define the underlying framework to do microservices effectively is the theme of the second topic: the microprofile. There are defined specifications for different Java platforms (Standard and Enterprise) but both have the assumption of large-scale, full server architectures. New wave development, though, is increasingly small, with small services in those larger complex systems. What Java EE introduced to development was consistency and dependability. As we move into a new containerized world, we must do it responsibly, preserving the consistency and stability of previous environments. The microprofile project was created because a lot of vendors – Red Hat, IBM. Tomitribe, Payara – were just on a Slack chat, discussing what they needed to do for microservices and ways they could implement it. And then there was a lightbulb: maybe there’s something here. This is a chance to bring the whole Java community around a new architecture, with the strengths and discipline they’ve already developed.

Watch the whole video. For microprofile, you can join the Google group or check out the microprofile site for more information and emerging discussions.

Red Hat Summit: Tuesday Recap

redhat-sign

Tuesday was the first official day of Red Hat Summit. (DevNation started on Monday.) There is a lot going on in middleware, down a lot of different tracks — application development, business automation, integration. Tuesday had an overall focus on containers; for middleware, that means that most of the sessions related to Red Hat Enterprise Application Platform 7 and how it works in cloud and container environments.

Don’t forget to check the Middelware Guide to Loving Summit for session highlights for each day and for social media channels to watch for live tweeting and general commentary.

Continue reading “Red Hat Summit: Tuesday Recap”

JBoss EAP 7 Fast and Sporty: The Cash / Car Giveaway

Red Hat JBoss Enterprise Application Platform 7 is small, agile, fast, and fits easily in appropriately-sized containers. There are a number of ways we’re showing our pride for the JBoss EAP 7 launch here at Summit, but one of the coolest is the cash / car giveaway, with a Mini Cooper S convertible, tucked inside a custom container.

WP_20160627_15_44_09_Pro

Starting today, Red Hat Summit attendees can enter a drawing to win an amount of cash equivalent to the price of the Mini Cooper S convertible ($24,950 as of June 1, 2016). Tablets to sign up are located at various JBoss booths in the Partner Pavilion of Moscone West. The drawing will be held Wednesday evening, so don’t delay.

WP_20160627_13_39_14_Pro (1)

 

There are the normal restrictions: no Red Hat employees or friends and relatives of employees, and you do have to be a Red Hat Summit attendee to be eligible. The full contest terms and conditions are on the Red Hat website: 

https://www.redhat.com/files/resources/car-giveaway-contest-terms-conditions.pdf.

Good luck.

Red Hat Summit: Monday Recap

Yesterday was an incredibly exciting day at the DevNation general session. Two major things occurred (out of half a dozen things) related to middleware at Red Hat:

I summarized those two announcements with some thoughts on how they show the evolution and resilience of Java on LinkedIn. Read the whole thing, as they say.

Other highlights from Monday’s DevNation:

There’s a new photo album on the Middleware Facebook page, too, capturing a lot of moments from this week.

A Middleware Guide to Loving Red Hat Summit

Red Hat Summit and DevNation are this week in San Francisco. There will be over 200 sessions and labs, along with exhibits and demos in the pavilion, partner presentations, coding events, and (of course) contests and swag.

Take a tour of the red carpet.

WP_20160627_11_52_42_Pro

It can be hard to keep track of everything, so this is something of a cheatsheet to sessions and social media sites that have a running commentary on what’s what.

Session Lists and Recommendations

Social Media Sites to Follow

Continue reading “A Middleware Guide to Loving Red Hat Summit”

MicroProfile – Collaborating to bring Microservices to Enterprise Java

This post was originally published at Red Hat Developers.

MicroProfile-Black

Today at the DevNation conference in San Francisco, Red Hat’s Mark Little was joined on-stage by Alasdair Nottingham from IBM, Theresa Nguyen from Tomitribe, Mike Croft from Payara and Martijn Verburg from the London Java Community to announce a new community collaboration – MicroProfile – whose goal is to make it easier for developers to use familiar Java EE technologies and APIs for building microservice applications.

Mark talked about some of the reasons Java EE has established itself as the dominant standard for companies building business-critical multi-tier enterprise applications, including :

  • An open standard platform that enables vendors to compete on implementation, price, or business model
  • A collaborative standard and process that is driven by many vendors and individual developers rather than a single vendor
  • Consistent and holistic vision for all architectural tiers of the application
  • A strong focus on adherence to the standard and compatibility between vendor implementations and versions of the specifications

As organizations start to think about the next generation of those business-critical applications, many of them are likely thinking about cloud-native, Linux containers and microservices, and how they evolve by using the technologies and skills they already have.

Red Hat, IBM, Payara, Tomitribe and the London Java Community believe that Enterprise Java is a solid foundation on which to build the next generation of applications and the MicroProfile (which may ultimately become a submission for a standard specification) can make it easier and provide portability between vendor’s implementations. The first release of the MicroProfile is expected to be available in September, with Red Hat’s implementation to be based on WildFly Swarm.

Red Hat continues to support those in the Enterprise Java community that are working hard to move Enterprise Java forward by pushing ahead on the evolution of Java EE. To emphasize this point, Red Hat has underlined its support for Java EE 8 and is committed to finishing the JSRs it leads, like CDI 2.0, and any necessary enhancements to Bean Validation while it also invests in the MicroProfile. We see synergy between the current Enterprise Java community efforts and the newly announced MicroProfile, which is born out of the same Enterprise Java community. To us it’s clear that the Enterprise Java community is forging ahead.

Red Hat understands that Enterprise Java has been successful for almost two decades thanks to the community collaboration that drove its evolution. Please join and participate in the MicroProfile effort and let’s all take the next step forward by cooperatively innovating to bring the microservice architecture to Enterprise Java.

Continuous Delivery to JBoss EAP and OpenShift with the CloudBees Jenkins Platform

If you are using JBoss Enterprise Application Platform (EAP) for J2EE development, the CloudBees Jenkins Platform provides an enterprise-class toolchain for an automated CI/CD from development to production.

The CloudBees Jenkins Platform now supports integrations with both Red Hat JBoss Enterprise Application Platform (EAP) and Red Hat OpenShift across the software delivery pipeline. This enables developers to build, test and deploy applications, with Jenkins-based continuous delivery pipelines in JBoss via JBoss EAP 7 or JBoss EAP 7 on OpenShift.  

Continue reading “Continuous Delivery to JBoss EAP and OpenShift with the CloudBees Jenkins Platform”