Tuesday, March 25, 2014

Contract first web service integration with Apache Camel on JBoss EAP

Christian did a great job on a Blog Post and Video on Apache Camel on JBoss EAP.  The links for the blog and video are below:

Blog - http://www.christianposta.com/blog/?p=359
Video - https://vimeo.com/89750593

Service Lifecycle Management with Fuse Service Works Webinar

I will do a quick overview of Fuse Service Works and Kurt will dive deeper into Design Time Governance.  See the details of the Webinar below.

Register at https://vts.inxpo.com/scripts/Server.nxp?LASCmd=AI:4;F:QS!10100&ShowKey=18867&AffiliateData=em2inactive&elq=108fe86f87a44a85a0161adc5867d0f7&Referrer=https%3A%2F%2Fmail.corp.redhat.com%2Fzimbra%2F

You have a lot to keep track of—people, processes, and technologies—when it comes to service-oriented architecture (SOA) governance. You need the ability to manage the life cycle of services from inception through deployment through change management. Red Hat® JBoss® Fuse Service Works can help.

Design time governance
JBoss Fuse Service Works provides design time governance allowing an enterprise to manage software artifacts using workflow and human task management. It’s an SOA repository compliant with the recently published OASIS S-RAMP specification. Its ATOM-based API makes it highly suitable as a solution for software artifacts governance.
Join Kurt Stam, Red Hat senior software engineer, for his webinar covering:
  • An introduction to deign time governance.
  • A demonstration of two processes—management deployment and software project development—using JBoss Fuse Service Works design time governance.
  • The answer to some painful questions he’s experienced while working on the full life cycle of SOA services:
  • “I have all these enterprise software systems, but where the heck’s all my stuff?”
  • “Hey dude, you pushed that to production right? Right?”
  • “Who’s working on this service implementation, and who signed off on this design?”
Speaker: Kurt Stam, senior software engineer Core Developer, Red HatKurt is the project lead on the registry and repository projects. He has been working in enterprise integration for the last decade. He has designed and implemented integration solutions for high-volume distributed systems in the telecommunication, financial, and travel industries.

Friday, March 21, 2014

Client API's with A-MQ 6.1 Webinar

Please watch for the registration link for the April 23 11am EST Webinar-

Title: Getting Started with A-MQ 6.1 and Client APIs

JBoss A-MQ is a high performance, flexible, cost-effective messaging platform
that delivers information safely and reliably with a small footprint.
Multi-protocol support (JMS 1.1, TCP, SSL, STOMP, NMS) and multi-client
support (Java, C, C++) enables real-time messaging with all enterprise
assets.  Red Hat JBoss A-MQ clients can connect to a broker using a variety
of transports and APIs. The connections are highly configurable and can be
tuned for the majority of use cases.  Join us as we explore the use cases and
using different JBoss A-MQ clients including AMQP JMS, C++ and .NET as well
as the REST API.

Join Kenneth Peeples, Red Hat Technical Marketing Manager, for his webinar

-An introduction JBoss A-MQ 6.1
-An introduction to JBoss A-MQ Client APIs
-A demonstration of using the the different client APIs including the Qpid
JMS Client API

Tuesday, March 11, 2014

Fuse Service Works and SCA

Fuse Service Works contains three main components - Core ESB based on JBoss Fuse, Service Framework based on Switchyard and Governance based on Overlord.  Switchyard is a lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

Switchyard is a implementation of some of the SCA specifications.  The Switchyard Designer below shows an example of a Home Loan Application with the Services/References/Bindings.

Service Component Architecture (SCA) is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture (SOA).  SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services.  This diagram shows services and references in relation to bindings.

Open CSA oversees the work of several OASIS Technical Committees on SCA that address the following specifications:

• SCA Assembly Model
• SCA Policy Framework
• SCA Java Annotations, APIs, and Component Implementation
• SCA Client & Implementation: C++
• SCA Client & Implementation: BPEL
• SCA Client & Implementation: PHP
• SCA Client & Implementation: Spring
• SCA EJB Component Model
• SCA Bindings Specifications

SCA essentially standardizes a conceptual model for the definition, structure and implementation of service-oriented applications.   Even though the standard is defined there is no guarantee of interoperability or portability for applications across different vendors which are developed for an SCA runtime.  So there is a big advantage in having the shared conceptual model between implementations as the user's view of the application will be similar across them.  The  implementation of the specifications that Fuse Service Works v6 follows are based on the merit and relevance of the specification and the ability to deliver it in the product.   There are some parts that are useful which we have not implemented yet and others that customers may request which we can take on as feature requests.  So the product team will continue to fill out our support for SCA specs as it makes sense for the product platform.

One thing to keep in mind is that the list of specifications are in very different states of maturity. At this point Assembly is the most mature.

There is not a master list of what's implemented and what's not.  If there is something specific that is needed it is best to get an idea of what they're using and we can help line that up with what we have.

SCA Assembly Model

This is where the product team invested the vast majority of our time as it represents the configuration model for the application.  The coverage is not complete, but it is substantial.  The most notable section missing right now is around packaging and deployment.  We have our own packaging model which allows for JAR/EAR/WAR deployment at the moment.  That said, there are certain elements of the SCA packaging model which are attractive to us (e.g. recursive composition) that may make it in a 6.x release of FSW.

SCA Policy Framework

This is partially supported.  SCA Assembly pulls this in and we support the transaction and security policy sections of this specification.

SCA Client & Implementation: BPEL

BPEL deployments within a Switchyard application use the standard BPEL schema from this spec. 

SCA Java Annotations, APIs, and Component Implementation
SCA EJB Component Model
SCA Bindings Specifications

We have our own implementations of these via the standard SCA extension mechanism.  If customers are really interested in the standard version of these, we can always have a look.

SCA Client & Implementation: C++
SCA Client & Implementation: PHP
SCA Client & Implementation: Spring

No plans to do anything with these at the moment.

Monday, March 10, 2014

DevNation coming up in April

I am excited to be at DevNation and Summit in San Francisco April 13-17 this year.  Alot of things are happening at both events that are co-located in San Francisco.

DevNation - http://www.devnation.org/#agenda

Summit - http://www.redhat.com/summit/agenda/

There are so many labs, presentations, panels, etc at both Conferences.  In this blog I wanted to highlight 3 sessions, two around Fuse and OpenShift and one around the Internet of Things which are at DevNation..

Sunday 4/13 1:00-1:50pm
Integration PaaS: Continuous Integration with Fabric8 and OpenShift - Rob Davies & James Strachan (Room 236)
The Platform as a Service (PaaS) space is rapidly evolving, with many categories for middleware capabilites to add functionality, from aPaaS, to bpmPaaS to iPaaS, this talk will introduce the concept of xPaaS that lays the ground work for integrating all these services. Underpinning xPaaS is fabric8, which is being used to provide both independence from the underlying IaaS and PaaS layers, and also features to enable continous deployment into production.

Monday 2:45-3:45Integrating the Internet of Things - Sameer Parulkar & Jack Britton (Room 208)The Internet has become a medium to connect people, share information, find solutions, and report problems. With the advancement and availability of smart devices, the Internet will evolve to the Internet of Things—billions of interconnected smart devices and machines measuring, collecting, analyzing, monitoring, and sharing useful information. Join this session to learn how this information can be integrated with existing enterprise systems to make smarter decisions and build smarter solutions. You’ll learn how to use the capabilities available in Red Hat JBoss A-MQ to reliably collect this smart data in real-time, and the smart data can be integrated with existing enterprise systems using Red Hat JBoss Middleware.

Wednesday 4/16 1:20 p.m.-2:20 p.m.Using Red Hat JBoss Fuse on OpenShift - Jack Britton, Kenny Peeples (Room 208)OpenShift Online automates the provisioning, management, and scaling of applications so that you can focus on development and creativity. The newly created Red Hat JBoss Fuse 6.1 cartridge allows you to use Fuse and Fuse Fabric in the OpenShift Online public cloud. JBoss Fuse provides a full-featured, easy-to-use and intuitive framework for integration with extensive connectivity options to external applications.Join us to see how to use Fuse and Fuse Fabric in OpenShift online. In this session, you’ll learn:
  • How to install the Fuse cartridge.
  • How to access and use the Fuse Management Console.
  • How to deploy and test a Fuse bundle.

OASIS Message Queuing Telemetry Transport

I thought I would share information on a Technical Committee at OASIS that is working on a M2M/Internet of Things Protocol.  Check them out at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=mqtt
The OASIS MQTT TC is producing a standard for the Message Queuing Telemetry Transport Protocol compatible with MQTT V3.1, together with requirements for enhancements, documented usage examples, best practices, and guidance for use of MQTT topics with commonly available registry and discovery mechanisms. The standard supports bi-directional messaging to uniformly handle both signals and commands, deterministic message delivery, basic QoS levels, always/sometimes-connected scenarios, loose coupling, and scalability to support large numbers of devices. Candidates for enhancements include message priority and expiry, message payload typing, request/reply, and subscription expiry.
As an M2M/Internet of Things (IoT) connectivity protocol, MQTT is designed to support messaging transport from remote locations/devices involving small code footprints (e.g., 8-bit, 256KB ram controllers), low power, low bandwidth, high-cost connections, high latency, variable availability, and negotiated delivery guarantees. For example, MQTT is being used in sensors communicating to a broker via satellite links, SCADA, over occasional dial-up connections with healthcare providers (medical devices), and in a range of home automation and small device scenarios. MQTT is also ideal for mobile applications because of its small size, minimized data packets, and efficient distribution of information to one or many receivers (subscribers).
For more information on the MQTT TC, see the TC Charter.

Friday, March 7, 2014

Switchyard Labs for Fuse Service Works

Try the Switchyard Labs with Fuse Service Works.

These labs were originally part of a SOA training lab at Red Hat Summit 2013. The labs and guides have been updated to work with SwitchYard 1.0.0.Final. There are four labs in this training. Each lab has it's own SwitchYard project and associated lab guide. The lab guides are located in the guides/ directory.


Thursday, March 6, 2014

Provision Data Virtualization on OpenShift and Connect from Teiid Designer

Mark Drilling did an excellent article : Provision Data Virtualization on OpenShift and Connect from Teiid Designer.  The article shows to how to provision an instance of Data Virtualization 6.0 on OpenShift and connect to it from Teiid Designer / JBoss Developer Studio.


Wednesday, March 5, 2014

Making business intelligence systems more agile with data virtualization

The speed of business change continues to increase, and you need to increase your business intelligence (BI) development productivity to keep up. Data virtualization results in BI systems with simpler, and more adaptable architectures. Learn how in this webinar.

It didn’t happen overnight, but a new era for business intelligence (BI) has arrived. The technology and business requirements have changed. Gone are the days when it could take months to develop a new BI system.

Data virtualization with on-demand data integration

This webinar explains data virtualization and how its lean form of on-demand data integration results in BI systems with simpler and more agile architectures that can be adapted to new business challenges more effectively.

Red Hat® JBoss® Data Virtualization will be discussed, along with the key key concepts of data virtualization, including:
  • Logical tables
  • Importing data sources
  • Data security
  • Caching
  • Query optimization
Rick van der Lans, managing director, R20/Consulting
Rick is an independent consultant, author, and lecturer specializing in data warehousing, business intelligence, big data, data virtualization, and database technology. He has written the industry's first independent book on data virtualization titled, “Data Virtualization for Business Intelligence Systems: Revolutionizing Data Integration for Data Warehouses.” Rick has advised many large companies worldwide on defining their data warehouse, business intelligence, and SOA architectures. He is the chairman of the European Enterprise Data and BI and Conference and writes regularly for B-eye-Network.com.

Syed Rasheed, solutions marketing manager, Red Hat
Syed coordinates marketing, evangelism, and consulting activities. In addition to helping customers address integration challenges, he is responsible for working with customers, partners, and industry analysts to help Red Hat technology meet customer requirements for business process automation and integration solutions. In his 18 years in the IT industry, Syed has extensive experience in business process management systems, business  intelligence, and data management technologies. His work spans the financial services, banking, and telecommunication industries.

Join the live event:

Time zone converter
Wednesday, March 19, 2014 | 15:00 UTC | 11 a.m. (New York) / 4 p.m. (Paris) / 8:30 p.m. (Mumbai)

Tuesday, March 4, 2014

Simplified Run Time Governance and Fuse Service Works

Simplified Workshop Series
Run Time Governance
in Fuse Service Works

Welcome to the Simplified demo series. I refer to this as a workshop in a box, meaning everything is included to get you started such as the source, instructions, videos, presentations, etc. This demo will walk you through a quick demo of Run Time Governance in Fuse Service Works. It is split into 3 main sections. First is the quick demo which walks you through the quick steps to run a quick, easy demo (The What). The second section gives an overview of the technology and how the demo was created (The Why and How). The third section gives you additional collateral. So let’s get started and as they say so easy a non techie can do it...

Section 1 : Run a quick demo

Step 1: Clone the repository from https://github.com/kpeeples/simplified-rtgov

Step 2: Download Fuse Service Works from http://www.jboss.org/products/fsw.html

Step 3: Place the software in the distros folder

Step 4: Modify the support/InstallationScript.xml file to contain the full path to the installed/fsw directory. Make sure to leave the installed/fsw directory. The script performs the automated install of Fuse Service Works. NOTE: This is installing the Switchyard, DTGov, S-RAMP and RTGov components which wouldn’t be the recommended setup as Design Time would be a separate server from the Switchyard/Run Time Server.


Step 5: Modify the post-run.sh file to have the appropriate directory for the quickstarts.

Step 6: Run the install-run.sh script to install FSW and start the server

Step 7: Open another terminal and run the post-run.sh script. This will kick off the individual examples.

A. First we deploy the application and information processor. The accepted status from the response should be true.

B. Next we will show the Synchronous Policy Enforcement to see that orders from Fred cannot be performed more the 1 request every 2 seconds.

C. Next we will show the Asynchronous Policy Enforcement to see that a customer will be suspended after 3 attempts that goes over a threshold. A make payment is done in order to continue orders.

D. Next we will show SLA Monitoring. The “Situations” active collection will report SLA violations to the end user through REST or JMX. We will use REST.

E. Next we will show SLA Reporting. We will generate a report which will return the violations that occured in year 2014.

This is a quick demo of Run Time Governance. More detail of configuration and step by step are below.

Section 2 : Technology Overview and creating the demo step by step

Technology Overview

This was compiled from http://docs.jboss.org/overlord/rtgov/quickstart/1.0.0.Final/html_single/index.html and https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6/html-single/Development_Guide_Volume_3_Governance/index.html.

In SwitchYard, the applications are exposed as shared business processes or services. In a shared environment, the most common challenges revolve around access control, access rights, security issues, and service authorizations. SwitchYard uses Run-Time Governance to facilitate complete control over the shared services by following a policy based approach. SwitchYard classifies Run-Time Governance into two aspects:
  • Policy definition and enforcement
  • Collection and exposure of run-time metrics for services and service references
The architecture is separated into four distinct areas, with components that bridge between these areas:
  • Activity Collector - this component is optional, and can be embedded within an executing environment to manage the collection of information
  • Activity Server - this component provides a store and query API for activity information. If not using the Activity Collector, then activity information can be reported directly to the server via a suitable binding (e.g. REST).
  • Event Processor Network - this component can be used to analyse the activity information. Each network can be configured with a set of event processing nodes, to filter, transform and analyse the events, to produce relevant rules.
  • Active Collection - this component is responsible for maintaining an active representation of information being collected. UI components can then access this information via REST services to present the information to users (e.g. via gadgets)

Step by Step

The step by step will be added in the next version.

Section 3 : Additional Collateral and demo structure

The root folder of the demo contains:
  • install-run.sh to install and run FSW
  • pre-run.sh to do any pre-installation setup or compiling
  • post-run.sh to do any post-install setup or compiling
  • README.MD to briefly descibe the demo
  • readme.html to meet the objectives 1) quick and easy demo 2) step by step instructions with collateral
  • reset.sh to reset the demo
The collateral folder contains:
  • Video for videos or link to video
  • Presentation for presentations or link to presentation
  • Blog for a blog document or link to blog
  • Simulation for a simulation of the demo or link to simulation
The distros folder contain the downloads for the demo
The installed folder contains subfolders for the software to be installed when the script is run
The source folder contains any source projects to be compiled and deployed
The support folder contains any supporting files/directories


Monday, March 3, 2014

Gain Actionable Insight @ Business Speed with Red Hat and Jaspersoft Webinar

Join Syed and Mike for a Red Hat and Jaspersoft Webinar!
Date: 5 March, 2014
Time: 15:00 GMT/16:00 CET
Duration: 60 Minutes
Language: English
Business intelligence (BI) teams face increasing pressure for faster time-to-value and shorter cycles to deliver decision making platforms. Hence the question in IT is shifting from how to build a data warehouse to how to speed delivery of insight and how to meet new requirements without breaking the bank. IT needs a platform that enables centralized and departmental BI/DW teams alike to respond rapidly to new requests and minimizes the temptation of business users to build their own systems outside IT. This requires more flexible platforms, tools and methods that can speed delivery and lower costs. 

We will introduce and discuss agile data integration and analytics offerings from Red Hat and Jaspersoft to enable IT to meet business demand while lowering cost.

Topics Covered:

  • Learn more about JBoss Data Virtualization for agile data integration and provisioning
  • Learn about Jaspersoft BI Platform for agile data analytics and visualization
  • See a live demo of Jaspersoft and RedHat in action
  • Summary


  • Syed Rasheed - Solution Marketing Manager (RedHat)
  • Mike Boyarski - Director of Product Marketing (Jaspersoft)