OpenShift is great! Developers can quickly start development on a new project. Just log into the web console, create a new application, select a gear and start coding. When you are done implementing a feature you push to OpenShift and after a few seconds you can admire and share your work with the whole world.
But there is more to consider when working with OpenShift. What if you develop in teams? Usually applications are not directly deployed into production. How can I implement a staging process harnessing the OpenShift Infrastructure? How do I know if my changes passed an Acceptance Test or failed it? How does a test team know which features have been implemented?
The answer to these questions are usually not easy, and every company has implemented their own set of processes to address these problems. Although some Organizations have automated some of their IT Infrastructure, there are still a lot of manual processes and changes involved when it comes down to taking a particular software release from development into production. On the other hand, the business stakeholders have a high interest into a fast and efficient Release process, because every day that my feature is not in production and available to my users, is lowering my ROI. Continue reading →
The following article originally appeared here in the UK and here in Germany.
Who could have predicted the impact on mainstream businesses of data coming in via social media and mobile technology, the escalating importance of trends such as ‘big data’ or the move towards cloud computing that is now gathering momentum?
The sources of data coming into the enterprise IT infrastructure are proliferating, with new channels and touch-points constantly emerging at an unprecedented rate. Clearly, in an uncertain world, flexibility is a critical component of any business IT strategy.
With today’s customers choosing to interact through multiple channels, businesses are wasting time and budget ‘hand-carrying’ information from application to application, frequently without adding value at best and introducing human error at worst. Continue reading →
Red Hat has just released a new certification in support of its JBoss Enterprise Middleware line. Red Hat Certified JBoss Developer (RHCJD) is earned by passing a rigorous, hands-on lab exam that tests one’s ability to write, extend and modify JBoss Enterprise Edition (JEE) applications that will run on the Enterprise Application Platform.
Ever since Red Hat acquired JBoss in 2006, there has long been a certain tension between testing and certifying the “JBoss-centric” versus the “spec-level”. RHCJD is where Red Hat puts a stake in the ground and offers what we believe will become THE certification for JEE spec-level programming. There is a growing vacuum of leadership in this space and we intend to fill it. RHCJD gives us a core credential upon which we will build and extend the JBoss certification program for developers. Continue reading →
Converting a web project generated by the JBoss Developer Studio CDI Web Project wizard to a Maven project will give you the power of the Maven build system with its dependency management, build life cycles, and automated JEE packaging abilities. To covert a JBoss Developer Studio web project, follow these steps:
1. Right click on the project name in the Project Explorer tree and select Configure → Convert to Maven Project… In the wizard steps be sure to select WAR packaging.
2. Configure the Java SE 6 compiler plugin so that we can process annotations. Add this to pom.xml file: