Eric D. Schabell: New integration scenarios highlighted in JBoss BPM Suite & JBoss FSW integration demo

Wednesday, August 20, 2014

New integration scenarios highlighted in JBoss BPM Suite & JBoss FSW integration demo

There is a new demo on the block and it is all about showing off the integration between JBoss BPM Suite and JBoss FSW.

This initial announcement provides an automated installation (repeatable) in minutes where you get JBoss BPM Suite running on an instance of JBoss EAP and a separate instance of JBoss FSW on its very own EAP instance.

There are plans to expand this demo project with various integration scenarios or use cases, but for now we start with just a single story around using JBoss FSW governance integration to manage your rules, events, data models, processes, and other BPM artifacts.

Background

This demo is brought to you in part by Kenny Peeples who is the JBoss Technology Evangelist that focuses on this product. He will be expanding this project in the coming days to include a Switchyard services application that will leverage a Fuse camel route which in turn makes a call to a process running on JBoss BPM Suite.
Governance workflow

There will be more expansion such as calling a Switchyard services application from a BPM process and much more so stay tuned.

The project can be found on github and has documentation to get you up and running in minutes.

Governance process

The S-RAMP and DTGov tooling comes with a standard process that was designed using the same BPM Suite tools you are using to create your process projects.

Email task notification
It models the process you work through when you run mvn deploy in the provided demo project, which uploads the project artifacts into the S-RAMP repository and automatically starts a process instance for the new artifact.

Installing and running

The following steps will get you up and running in a matter of minutes with this fully automated and repeatable demo:
  1. Add products to installs directory.
  2. Run 'init.sh' or 'init.bat'.
  3. Copy this code snippet into your ~/.m2/settings.xml (authorization for s-ramp repository):
    <!-- Added for BPM Suite Governance demo -->
    <servers>
      <server>
         <id>local-sramp-repo</id>
         <username>erics</username>
         <password>jbossfsw1!</password>
      </server>
    </servers>
    
Follow the instructions on the screen to start JBoss BPM Suite server and JBoss Fuse Service Works server.
   Login to http://localhost:8180/business-central  (u:erics / p:bpmsuite1!).

   Login to http://localhost:8080/s-ramp-ui         (u:erics / p:jbossfsw1!)

   As a developer you have a modified project pom.xml (found in projects/customer)
   which includes an s-ramp wagon and s-ramp repository locations for transporting any
   artifacts we build with 'mvn deploy'.

        $ mvn deploy -f projects/customer/evaluation/pom.xml

   The customer project now has been deployed in s-ramp repository where you can view
   the artifacts and see that the governance process in the s-ramp was automatically
   started. Claim the approval task in dashboard available in your browser and see the
   rewards artifact deployed in /tmp/dev copied to /tmp/qa upon approval:

        http://localhost:8080/s-ramp-ui            u:erics/p:jbossfsw1!       

   The example of promoting through dev to qa to stage to prod is an example of using
   a local filesystem for this demo.

       $ ls /tmp/dev/

         evaluation-1.0.jar

       $ ls /tmp/qa/

         evaluation-1.0.jar

Note that the setup puts JBoss FSW product on port 8080 and JBoss BPM Suite on port 8180 (offset 100).
Artifact repository

The FSW S-RAMP and DTGov installation is configured to automatically react to any deployments of the provided customer evaluation project, kicking off an instance of the process to start evaluating and approving or rejecting the artifact build for the next level of your infrastructure.

The current demo setup just uses the following file system locations to show progression but you can configure this to make use of existing continuous integration infrastructure in your own enterprise as needed.
  • /tmp/dev
  • /tmp/qa
  • /tmp/stage
  • /tmp/prod
If at each stage you approve the task waiting in the S-RAMP UI, it will copy the artifact to the new /tmp/dev folder, but after approving the waiting task you will find a new copy in /tmp/qa.
deployment stage.

This video walks you through the installation and BPM artifact governance use case in just under 10 minutes:



We hope you enjoy this new demo showcasing JBoss FSW governance integration with JBoss BPM Suite.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.