In this BOF session, we’ll go through the steps to connect hardware sensors to your Red Hat JBoss Middleware stack. We’ll do so via ARM processors using IoT protocols like CoAP (Constrained Application Protocol) and DTLS (Datagram Transport Layer Security)/UDP via REST interfaces over HTTP for lookup and eventing services.
The Red Hat JBoss Middleware layer transforms the events and states received from the IoT layer using business logic EE7 components and business rules to integrate the sensor layer with enterprise logic.
The hardware sensors that will be available include:
- 128×32 Graphics LCD
- 5 way joystick
- 2 x Potentiometers
- 3.5mm Audio jack (Analog Out)
- Speaker, PWM Conencted
- 3 Axis +/1 1.5g Accelerometer
- 3.5mm Audio jack (Analog In)
- 2 x Servo motor headers
- RGB LED, PWM connected
- Temperature sensor
- Socket for for Xbee (Zigbee) or RN-XV (Wifi)
Google App Engine (GAE) is a popular PaaS offering. While its scalable and reliable environment is hidden behind custom API, this makes GAE apps hard to port over to other non-GAE environments.
What if one could implement such similar environment? And you could simply move your GAE application’s .war file to this new environment and it would just work?
But the question we need to ask ourselves first, how do we know that such alternative environment works in the first place?
Java EE has had its Technology Compatibility Kit (TCK) from day one. This time we’ll introduce you to GAE TCK and show you how to run it against an alternative JBoss CapeDwarf GAE API implementation.
The GAE TCK is built completely on open source software, and it is a collaboration between Red Hat and Google on making the GAE API and its implementations better.
The goal is not just to run the tests, but also engage users and developers with a bunch of exciting extensions that range from cool html reporting to bytecode manipulation of external tests.
If you care about GAE, testing, Arquillian, ShrinkWrap, this is the session not to miss!
Monitoring and measuring various aspects of system performance required to provide baselines for expected performance and to identify when performances issues are occurring. In this BoF session, we’ll discuss available monitoring tools and their applications to provide insight in system performance.
Red Hat Software Collections is the new way Red Hat is making the latest stable versions available for Red Hat Enterprise Linux. It includes a host of new components:
- Python 2.7 and 3.3
- Ruby 1.9.3
- PHP 5.4
- Perl 5.16
- MySQL 5.5
- PostgrSQL 9.2
- Node.js 0.10 (tech preview)
Come to this BoF session and let’s talk use cases, discuss the problems you’re trying to solve, and answer any other questions you want to bring. This will be a great opportunity to ask follow-up questions from previous session on Red Hat Software Collections.
In this BoF session, we’ll discuss what the next steps are for Java EE and whether it’s still relevant for application developers.
This session will present new features in WildFly 8 around 2 themes :
- Java EE 7 : WebSocket / JSON / REST / Servlet NIO / Batch / JMS
- Cloud : OpenShift and AppEngine with CapeDwarf
Red Hat JBoss Operations Network helps you monitor and manage application server installations like Red Hat JBoss Enterprise Application Platform, Red Hat JBoss Web Server, and Red Hat Fuse Service Works.
Red Hat JBoss Operations Network follows a hub and spoke architecture with a central server and agents on machines with resources to manage them. Customers can interact with the system using a comprehensive user interface on the server or a command-line interface and a REST API.
In this session, you’ll have the opportunity to discuss your use cases, set ups, and needs. Come prepared to discuss your success stories and challenges and to help us shape the future direction of Red Hat JBoss Operations Network.