by Brad Davis (Red Hat)
With the release of Red Hat JBoss Enterprise Application Platform 6, Red Hat successfully delivered a full JEE 6-compliant container that is both lightweight and enterprise ready. As a result, many IT leaders are actively looking to shift their application workloads away from proprietary technologies like Websphere and Weblogic to JBoss EAP.
But questions about cost, risk and starting point often stand in the way.
In response, Red Hat Consulting has developed a proven methodology, identifying four key pillars to a successful migration. Leveraging Planning, Participation, Communication, and Follow through, more and more customers are easily migrating from legacy platforms to JBoss EAP.
The Planning pillar analyzes an organization’s proprietary applications and processes. This stage elicits an understanding of the application environment, as Red Hat’s JBoss Windup tooling quickly scans applications to find and estimate migration effort for each application. Data from the Windup report allows us to group applications together and to plan for optimized parallel or repeatable migrations where appropriate. Those critical to the migration’s success from a business, development and operational standpoint are also consulted to best understand the skill sets, procedures, and timelines needed to support development, architecture, deployment, maintenance and monitoring tasks.
Continue reading “Java enterprise application migration: The four pillars of success”
We’ve somehow already reached the halfway point of the calendar year. Since Halloween decorations will be out before you know it, we thought it would be a good idea to look back at our most popular posts from the first six months of the year, just in case you missed something. Have something in mind you want to read about during the second half of the year? Want to contribute? Please let us know.
Continue reading “The best of 2013, so far”
by Satish Irrinki (Red Hat)
Increasingly in today’s world, data centers are moving towards software-defined computing, networking, and storage. IT infrastructure that supports the application and data workloads is moving from bare metal servers to cloud. While the most obvious justification for this shift can be summarized as increased efficiency, capacity utilization, and flexibility (to scale up or down), there are less obvious fundamental economic and financial principles in play that contribute to overall business stability of the organizations and lines of business (LOB).
Cloud computing has changed the cost structure of IT infrastructure. Historically, IT infrastructure was considered a capital expenditure (CapEx) that requires large upfront investments leading to higher fixed costs for the business. With the advent of cloud computing, primarily because of its pay-for-use billing model, IT expenditure shifted from fixed operating cost structure to variable operating cost (OpEx) model.
This shift not only decreases the need for larger cash flow requirements or, in lieu, higher liabilities on balance sheet (akin to capitalization of lease expenses) for the CapEx, it also reduces the volatility in the operating income for the business.
Continue reading “Cloud Adoption for Enhanced Business Stability”
by Thomas Crowe (Red Hat)
A key component to a successful migration is a “migration mission statement.” The migration mission statement’s purpose is to summarize the key parts of a migration into a succinct, simply-communicated format that results in a clearly defined migration goal that is easily measurable for success. A sample migration mission statement could be:
Migrate the Acme Order Processing java application from the current proprietary IBM hardware running AIX and WebSphere into a cloud infrastructure running Red Hat Enterprise Linux and JBoss Application Server; in order to provide better TCO and ROI, as well as provide increased scalability and reliability. The migration should be performed during non-peak hours, have minimal downtime requirements, and provide for rollback if necessary.
Generally speaking, there are several factors that go into planning and executing a successful migration project. But by answering the following questions, a significant amount of the information necessary for a successful migration can be gathered.
The most basic question to initially ask is simply, “What is being migrated?” This simple question sets the stage for gathering the additional information that is required. Is the migration moving all services from one server to another? Maybe it is migrating an application from one application server to another, or migrating storage from one array to another. Each of these scenarios are going to have unique data-gathering requirements that need to be understood in order to successfully plan and ultimately execute a successful migration.
Continue reading “Determining your ‘migration mission statement’…and why it’s important”
by Alan Hale (Red Hat)
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 “Building the intelligent enterprise: easy and inexpensive?”
by Kenny Peeples (Red Hat)
The following article describes how to enforce authentication with SAML and authorization with XACML on a JAX-WS Web Service on JBoss Enterprise Application Platform with Picketlink. I combined several articles listed in the References section to make this one demonstration. The source code is on github.
JBoss Enterprise Application Platform 5.2.0
JBoss Developer Studio 6
Note: Future updates will the latest versions of EAP/Picketlink/Fuse and moving the projects to maven.
Contains the Web Service to take the assertion out of the wsse, validate it, verify authorization and process the request. The files contained in the project are the SAML2ServerHandler.java, WSTest.java, WSTestBean.java, jboss.xml, jbossxacml-config.xml,standard-jaxws-endpoint-config.xml,xacml-policy.xml,sts-config.properties,sts-roles.properties,sts-security-domain-jboss-beans.xml,sts-users.properties. All the XML is displayed to the console.
Continue reading “Enforcing Authentication and Authorization on a JAX-WS web service using Picketlink”
by Kenny Peeples (Red Hat)
The post below originally appeared here on March 14, 2013.
On March 12, 2013, Red Hat announced the addition of Red Hat Fuse and JBoss A-MQ to its enterprise middleware portfolio, which are based on Apache Camel and Active MQ. The announcement is here.
Additional information including software downloads are located at http://www.jboss.org/jbossfuse and http://www.jboss.org/jbossamq
I am updating the videos for better sound and content but here is the first preview of the Fuse WebSocket HTML 5 demo.
The videos will help you build your first application in Fuse.
Video Part 1: Part 1 Getting Started
Video Part 2: Part 2 Getting Started
Video Part 3: Part 3 Getting Started
Source Code located on github at: https://github.com/kpeeples/jboss-fuse-websockets-demo-1.git
by Justin Hayes (Red Hat)
Like many organizations, Red Hat Consulting constantly seeks ways to eliminate organizational inefficiencies in our business operations. These inefficiencies typically deal with how our consultants are trained on cutting edge technologies, how our sales force demonstrates product capabilities to our customers and prospects, and how our technical groups request operational environments (virtual machines, platforms, etc.)
To attack this problem, a team of architects and consultants set out to design, implement, and operationalize a system that will reduce these inefficiencies. This system is called the Red Hat Innovation Center (RHIC). Its vision is twofold:
1. To demonstrate Red Hat products’ features and capabilities through a solutions-oriented approach based on real world use cases.
2. To enable our consultants to quickly and efficiently learn our technologies by lowering the barriers to entry to internal training.
Continue reading “Introducing the Red Hat Innovation Center”