Friday, January 30, 2015

Government Certification and Accreditation Made Easy

I wanted to highlight this week the resources that will help you with Government certifications and Accreditations. There is a great resource page that highlights everything but I wanted to list the middleware specific ones below. These will help you comply with a variety of the government Requirements. You can find the government standards page here.

Common Criteria Certification (CCC):
JBoss EAP 5 is EAL4+ Certified. You can find the configuration guide here.

JBoss EAP 6.2 is being evaluated for EAL4+ Certification. You can find more about the certification process here.

There are some tools that help with compliance:
OpenSCAP is a tool for running Security Content Automation Protocol (SCAP) content. The project is the upstream for the openscap tool that ships in Red Hat Enterprise Linux.

The SCAP Workbench provides a simpler interface for creating and editing SCAP content.

The Baseline compliance content in SCAP formats is located on github  -

Communities that help:
The Red Hat-sponsored gov-sec community is a moderated mailing list for US government security professionals.

Military Open Source Working Group (Mil-OSS) is a community of open source enthusiasts in the DOD. It is not affiliated with Red Hat in any way, but many Red Hat folks are active members. If you are interested in any of the information on this page, there's a good chance you'll enjoy this group. You can find more information on the Mil-OSS website.

Monday, January 19, 2015

The Business Value of Integration Products


Companies ranging from 100s to 1000s of employees were interviewed, including global representatives of the telecommunications, IT, shipment and logistics, retail and document management industries.
Red Hat® JBoss® Fuse delivered an average 3-year ROI of 488%, in a payback time of 8.2 months, with a number of business value benefits.


  • 51.5% more applications integrated per year
  • 40.8% fewer FTEs per application integration
  • 62.8% less application downtime related to integration
  • 18.1% improved middleware integration solution performance
  • 34.2% less costly than previous middleware integration solutions
Read the entire whitepaper for the details, including the reasons these 6 customers adopted Red Hat JBoss Fuse at

Thursday, January 15, 2015

Scaling Microservices

I am working on API Guidance with Fuse and Data Virtualization and have been thinking about splitting services into manageable microservices that expose APIs by function.  I came across a site that discussed some microservice patterns:
  1. Monolithic architecture
  2. Microservices architecture
  3. API gateway
One of the articles on the Pattern site discussed the Art of Scalability that describes how to solve scalability problems.  This gives us good insight on how to split applications and services by function to achieve Scalability.  We can achieve this by building APIs with microservices within containers.

The Art of Scalability  book describes a really useful, three dimension scalability model: the scale cube.  The microservice architecture is an application of Y-axis scaling on the scale cube.   We will go through more detail of the Y-Axis but for further description of the X and Z Axis you can read more on the AKF Partner site.  

As you can see from the graphic below, the AKF Scale Cube consists of an X, Y and Z axis.  Each of the Axes addresses a different approach to scale a service.  The Y-Axis highlights splitting services by function which we can split into Microservices that expose APIs by Function or Service.

From AFK Partners splitting services article:
The Y Axis of the cube represents a split by function, service or resource. A service might represent a set of use-cases and is most often easiest to envision through thinking of it as a verb or action like “login” and a resource oriented split is easiest to envision by thinking of splits as nouns like “account information”. These splits help handle not only the split of transactions across multiple systems as did the X axis, but can also be helpful in reducing or distributing the amount of memory dedicated to any given application across several systems. A recommended approach to identify the order in which these splits should be accomplished is to determine which ones will give you the greatest “headroom” or capacity “runway” for the least amount of work. These splits often come at a higher cost to the engineering team as very often they will require that the application be split up as well. As a quick first step, a monolithic application can be placed on multiple servers and dedicate certain of those servers to specific “services” or URIs. While this approach will help spread transaction processing across multiple systems similar to our X axis implementation it may not offer the added benefit of reducing the amount of system memory required by service/pool/resource/application. Another reason to consider this type of split in very large teams is to dedicate separate engineering teams to focus on specific services or resources in order to reduce your application learning curve, increase quality, decrease time to market (smaller code bases), etc. This type of split is often referred to as “swimlaning” an application.
From scale cube article:
Unlike X-axis and Z-axis, which consist of running multiple, identical copies of the application, Y-axis axis scaling splits the application into multiple, different services. Each service is responsible for one or more closely related functions. There are a couple of different ways of decomposing the application into services. One approach is to use verb-based decomposition and define services that implement a single use case such as checkout. The other option is to decompose the application by noun and create services responsible for all operations related to a particular entity such as customer management. An application might use a combination of verb-based and noun-based decomposition.

Wednesday, January 14, 2015

Red Hat Summit and DevNation Submissions

Today is the last day for Red Hat Summit Submissions.  DevNation submissions are accepted until 1/28/2015.  I have a couple of talks with demos that have been submitted for Red Hat Summit which are listed below.  I am still working on my DevNation submissions.  You can submit your Summit and DevNation talks here.

Keep these dates in mind:

November 19, 2014 - Call for proposals opens
January 7, 2015 - Call for proposals closes
January 14, 2015 - Call for proposals extended deadline—Red Hat Summit
January 21, 2015 - Call for proposals extended deadline—DevNation
March 2015 - Speaker notifications sent
May 27, 2015 - Signed release forms and presentation slides due
May 27 – June 12, 2015 - Presentation rehearsals due
June 21-25, 2015  - DevNation
June 23-26  - Red Hat Summit

If you have any questions email [email protected] or [email protected].

Summit Talk/Demo 1:  Leveraging API Management to achieve success in the Digital Economy with Fuse, OpenShift and 3Scale

An API -- Application Programming Interface -- at its most basic level allows your product or service to interact with other products or services using standard based technologies. APIs enable access to an organization's assets -- data or services -- in a simple and quick way. Just as today every business has a website to expose data or services for humans, soon every business will have APIs to expose such assets in a machine-processable way. Gartner predicts that by 2016 75% of the Fortune 1000 will offer public Web APIs and 50% of B2B collaboration will take place through Web APIs.

As an organization you want to have full control and visibility about your API. This is where API Management comes into play to fully leverage the power of exposing assets via APIs. During this session we will cover five specific use cases about how APIs can accelerate your business in the Digital Economy, we will introduce how you can use Fuse, OpenShift and 3Scale to manage and control APIs and we will conclude with a practical demo.

In detail, we will showcase how to:
-Build and deploy your API
-Secure your API via access control
-Control your API via usage policies
-Operate your API via monitoring, analytics, reporting and billing
-Engage with developers via developer portals and interactive API documentation

Summit Talk/Demo 2:  Build your next enterprise application in 60 minutes with JBoss Middleware

Business demands for new applications are increasing as businesses seek new ways to engage with their customers. As a result IT is at the center of a sea change in application development as new approaches like DevOps emphasize rapid delivery of features and greater participation by end users and “citizen developers”.

Middleware technologies such as integration, business rules, BPM , mobile application platforms and Platform-as-a-Service (PaaS) are emerging as important tools for DevOps teams, greatly reducing the traditional coding requirements for new business applications. With appropriate use of middleware, DevOps teams can collaboratively and rapidly develop and manage applications that engage customers and connect to back end services and legacy systems.

Join us for this session where we will show how three middleware technologies – integration, business process management and mobile – can be brought together in the cloud to support development of context-aware, process enabled, connected enterprise mobile apps. We’ll show you how to delight your employees and customers with modern solutions that deliver results quickly and yet integrate seamlessly into existing infrastructure. 

Through a real-word use-case we will demonstrate:
-Development and deployment of an enterprise mobile app using FeedHenry’s Mobile Application Platform
-Inclusion of captured mobile information into business processes with JBoss BPM Suite
-Integration of automated processes with legacy applications and systems of record with JBoss integration solutions
-Automation of business decisions guided by business rules
-Attendees will gain an appreciation for the ease with which middleware-enabled applications can support ever-changing business needs, and an understanding of the benefits of Red Hat JBoss Middleware products.

Friday, January 9, 2015

JBoss Data Virtualization 6.1 Beta Available

JDV 6.1 beta is available for download from
- at
- Customer Portal at

JDV 6.1 beta Documentation is available at

For JDV 6.1, we focused on three major areas:

    •    Big Data
    •    Cloud
    •    Development and Deployment Improvements

with the following new features and enhancements


 - Cloudera Impala
In addition to the Apache Hive support released in JDV 6.0, JDV 6.1 will also offer support for Cloudera Impala for fast SQL query access to data stored in Hadoop.  Support of Impala is aligned with our growing partnership with Cloudera that was announced in October.

- Apache Solr
New in JDV 6.1 is support for Apache Solr as a data source.  With Apache Solr, JDV customers will be able to take advantage of enterprise search capabilities for organized retrieval of structured and unstructured data.

- MongoDB
Support for MongoDV as a NoSQL data source was released in Technical Preview in JDV 6.0 and will be fully supported in JDV 6.1. Support of MongoDB brings support for a document-oriented NoSQL database to JDV customers.

- JDG 6.3
Support for JDG as a data source was new in JDV 6.0.  We expand on this support in JDV 6.1, with the ability to perform writes in addition to reads.  JDV 6.1 users can also take advantage of JDG Library mode as an embedded cache in addition to the support as a remote cache that was previously available.

- Apache Cassandra (Tech Preview)
Apache Cassandra will be released as a Technical Preview in JDV 6.1.  Support of Apache Cassandra brings support for the popular columnar NoSQL database to JDV customers.


- OpenShift Online with new WebUI
We introduced JDV in OpenShift Online as Developer Preview with the JDV 6.0 release and will update our Developer Preview cartridge for JDV 6.1. With JDV 6.1, we are adding a WebUI that focuses on ease of use for web and mobile developers.  This lightweight user interface allows users to quickly access a library of existing data services, or create one of their own in a top-down manner.  Getting Started instructions can be found here:

With JDV 6.1 we improve support for the Bulk API with a more RESTful interface and better resource handling.  The SFDC Bulk API is optimized for loading very large sets of data.

- Cloud Enablement
With JDV 6.1 we will have full support of JBoss Data Virtualization on Amazon EC2 and Google Compute Engine.


-Security audit log dashboard
Consistent centralized security capabilities across multiple heterogeneous data sources is a key value proposition for JDV.  In JDV we add a security audit log dashboard that can be viewed in the dashboard builder which is included with JDV.   The security audit log works with JDV’s RBAC feature and displays who has been accessing what data and when.

- Custom Translator improvements
JDV offers a large number of supported data sources out of box and also provides the capability for users to build their own custom translators. In JDV 6.1 we are providing features to improve usability including archetype templates that can be used to generate a starting maven project for custom development.  When the project is created, it will contain the essential classes and resources to begin adding custom logic.

- Azul Zing JVM
JDV 6.1 will provide support for Azul Zing JVM.  Azul Zing is optimized for Linux server deployments and designed for enterprise applications and workloads that require any combination of large memory, high transaction rates, low latency, consistent response times or high sustained throughput.

- MariaDB
JDV 6.1 will support MariaDB as a data source.  MariaDB is the default implementation of MySQL in Red Hat Enterprise Linux 7. MariaDB is a community-developed fork of the MySQL database project, and provides a replacement for MySQL. MariaDB preserves API and ABI compatibility with MySQL and adds several new features.

- Apache POI Connector for Excel
JDV has long supported Microsoft Excel as a data source.  In JDV 6.1, we add support for the Apache POI connector that allows reading of Microsoft Excel documents on all platforms.

- Performance Improvements
We continue to invest in improved performance with every release of JDV.  In JDV 6.1, we focused particularly on improving performance with dependent joins including greater control over full dependent join pushdown to the datasource(s).

- EAP 6.3
JDV 6.1 will be based on EAP 6.3 and take advantage of the new patching capabilities provided by EAP.

Tuesday, January 6, 2015

Getting Started Quickly with JBoss Fuse

Build your first Fuse application
Follow the below series to build your first application. You will build some simple examples as well as build a Home Loan Application using JBoss Fuse to integrate different enterprise systems. The Home Loan Application accepts a loan request from the customer and provides a loan decision including a home mortgage rate. The series walks you through each step of the application development lifecycle, from start to finish.
Demonstration DescriptionMaterial
What is JBoss Fuse?
What is Apache Camel? What are Enterprise Integration Patterns (EIP)?
Build the Home loan application using EIP’s
Business requirements change. Extend the home loan application. New SaaS applications? No problem..
Business expanding. Extend the home loan application to partners, suppliers.
Innovate further. Try, experiment, test, deploy.
For more information:

Follow Christina Lin and Kenneth Peeples for more integration demos: