Business Making Progress

Forrester Recognizes Progress Sonic As A Leader in the ESB Market

Did you know that Progress® Sonic® was the industry's first Enterprise Service Bus (ESB)? It was, however, introduced in 2002 by Sonic Software which was an independent operating company of Progress Software Corporation.

In April independent research firm Forrester Research, Inc. named Progress Software as a leader in “The Forrester Wave™: Enterprise Service Bus, Q2 2011” report. In this detailed review of Enterprise Service Bus (ESB) providers, Progress Sonic ESB was recognized with particularly high scores for its ESB architecture, orchestration as well as change and control capabilities. The report also gave Sonic ESB high scores for product strategy and strategic alliances, while also scoring the product highly for its large customer install base.

Strategic businesses worldwide have made Sonic ESB a core component to their service-oriented architecture (SOA). A few of these companies include British Airways, Royal Dirkzwager, AutoTrader, and most recently UK-based PD Ports. Why did they choose Progress? Because Sonic ESB delivers the best overall combination of architecture, orchestration, mediation, connection as well as change and control features. It helps them achieve the business and operational responsiveness they need to be successful.

Cruise past your competition and make sure your integrated infrastructure is powered by the 1st and best ESB... Sonic ESB. If you are interested in the report, click here. It will be available FREE FROM REGISTRATION for the next five business days only. What a deal! ;-)

Feel free to also share your ESB integration and deployment experiences here.

Belgacom and the Case for Business-oriented integration in Communications Providers

It is no secret that the telecommunications industry has been exploring various ways to tackle issues such as declining ARPU (average revenue per user) and increasing customer churn over the last five years. The keys to proactively addressing these issues are agility and responsiveness. For example, responsiveness around customer service – to make customers feel they have a personalized valuable service – which reduces churn; and agility -- around launching new and compelling services rapidly – to increase ARPU.

Despite this quest for the Holy Grail, many communications providers have failed to lay sufficient foundations. While there may be some useful technologies deployed in an attempt to provide an agile and responsive integration platform – these technologies have often failed to deliver what is needed by the business. SOA is a prime case in point. While SOA technology has been successful in many ways, it has also led to a lot of disappointments. Often the business was sold on the promise that SOA would make operations more agile and responsive.  However, what resulted was technology for technologists that looked like plumbing and was daunting and too generic to the business.

Business people want solutions that can deliver visibility to problems and opportunities – such as key business events (e.g., an opportunity to sell a new service, based on context or location) or process failures (e.g. persistent dropped calls for an important customer) – so that problems can be responded to quickly and opportunities taken. The business also wants solutions that can enforce business-level policies and service-level agreements, as well as solutions that can interconnect services at a “semantic level” – not just plumb data together. In other words – the business wants to deal in business-level concepts, and be assured that the underlying complexity will be managed by the system.

Today’s announcement that Belgium operator Belgacom is transforming its business and IT integration programme (more information here) represents a huge step forward for the telecommunications industry. Belgacom is clearly focused around being more responsive to the needs of their customers in order to tackle issues such as churn through improved integration. By selecting the right business integration foundation to support their IT strategy, Belgacom has taken a critical step forward in a long-term strategy to become more operationally responsive to their customers.

Due to the nature of the economic times we live in, it is vital that the telecommunications industry as a whole ensures that they have the best possible integration technology in place. Only then will operators be able to enhance their customer experience management offerings to attract and retain their business customers, differentiate their offerings, and lower their service costs.

 

When it comes to Integration, Contracts Make all the Difference.

It may seem odd to talk about contracts and SOA in the same sentence, but without them experienced enterprise architects and integration developers understand the negative consequences that will ripple through the business.

A service-oriented architecture (SOA) requires establishing contracts between its participants. The first or most basic SOA contract provision concerns what formats and protocols are used. When two service participants, a provider and a consumer, establish a contract, it must start out with some protocol and format artifact (or transport and data-level semantic), such as an XSD and the associated WSDL describing the interface between that consumer and producer. These decisions establish the beginnings of interoperability, specifically how the first-level pin-outs get wired together.

Beyond this basic level, IT professionals tend to think about contracts in two broad areas: the service-level agreement (SLA) and security. For IT, an SLA usually specifies scale, response time, and availability: for example, handling 10,000 requests per second with a response time of less than 500 milliseconds, and availability to four 9s, or 99.99 percent uptime. From a security standpoint, a contract covers four or five areas.

In installment #7 of the Enterprise Integration Whiteboard Series, Hub Vandervoort delves into the sixth point of mediation - Quality of Service (QoS) and Quality of Privacy/Protection. But rather than providing a comprehensive account of the idea of QoS and QoP, the video podcast and technical paper offer a high-level overview of some capabilities within Sonic ESB by itself and in association with Actional, which is largely built into the ESB infrastructure, and how those come together to create the foundation of QoS\QoP—trust and commitment —required for effective contracts.

---

Check out all of the Enterprise Integration Whiteboard Series white papers and videos here!

Are you a sitting duck or one that will respond immediately to threats?

While many organisations are being ‘cautiously optimistic’ about what the future holds, the realities of today’s tough business environment could leave them as sitting ducks, according to Rick Reidy, CEO at Progress Software. They might take consolation that they’re in the same pond, but when interest rates in Japan hit near-zero, banks continue to fail and mistakes can lead to a ‘flash crash’, the pond is not a safe place to be. Businesses may have money, but fear and uncertainty is holding back decision-making – we await further regulation and want to know the consequences of recent government changes.

 
Listening to Rick’s keynote at our UK business summit (#progresswsummit, if you want to follow on twitter), in the impressive surrounding of Chelsea Football Club’s ground, London, it seems most of the audience agrees – it’s not good enough to sit around and wait to see if growth returns, and you cannot grow simply by cutting costs. You have to take control of your own ‘growth agenda’, as Rick put it. Businesses that want to survive the next five years need better visibility, through putting processes in place that enable them to react quickly to meet customer demands, adapt to market changes and take advantage of new opportunities. As Rick has advised, businesses need to act on up to the minute information so that leaders can make decisions based on foresight, not hindsight.
 
If you’re a regular reader of this blog you’ll already know that we call this ‘operational responsiveness’: the ability to sense and respond to customer and market changes so that organisations can move quickly to meet challenges and take advantage of new opportunities. 
 
Rick has talked about what this means in the airline industry: the notion of irregular operations has become a weekly reality as companies face intense market pressure, striking staff and disruption from natural phenomenon. ‘Swivel chair’ communication between operational areas is no longer good enough. To react quickly enough, they need responsive processes in place that can help them maintain services and inform customers, almost as-it-happens. If they don’t, they will face massive fines, lost custom and damaged reputation – risks no company can afford at present.
 
We’ll be hearing more from Gordon Penfold, CTO at British Airways, about their approach to becoming operationally responsive to meet the challenges of today and tomorrow. Watch this space for my take on his talk…

 

Stamford Bridge, here we come

Tomorrow sees Progress Software taking over Stamford Bridge, home ground to the world-famous Chelsea Football Club. We’re not just there to check out the players’ dressing rooms – we are being joined by James Caan, of Dragons' Den fame, as well as the great and the good of the UK business community, to discuss how businesses can start to make decisions based on foresight, not hindsight, in their operations.

Gordon Penfold, Chief Technology Officer at British Airways, will be sharing his insight on ‘operational foresight’, revealing how the organization has set itself up to better deal with the irregular operations that have become a fact of life in the last year. And Mike Gualtieri, senior analyst at Forrester Research, will be sharing his views on where the next wave of truly responsive business management is coming from, and which trends to watch for. And Progress' own Chief Executive Officer, Rick Reidy, will be giving a keynote too.

I'll be there, speaking in one session but also blogging and tweeting from the event. So watch this space for the latest updates.

For those of you attending, I look forward to seeing you there.

www.progresssoftwaresummit.com

 

Who's Job is it (to Sequence and Process Errors) Anyway?

It is a common software and integration architectural principle that the more dependencies built into a service, the less reusable that service becomes.  So then, why do some many vendors and enterprises continually create tightly coupled services and therefore lose re-usability?

The answer likely has something to do with mediation, more specifically sequencing and error recovery mediation. Sequencing and Error Recovery mediation are the two topics covered in a new webcast and technical paper posted today on Progress.com.  Both discuss why and how you should delegate sequencing and error recovery completely away from services, how this makes services unaware of what order they’re called in and the order the processes execute in, and ultimately how this makes services maximally reusable and your business more operationally responsive. 

The paper also explains how the Sonic ESB is designed to perform sequencing and, with multiple output paths on each endpoint, enable error recovery processes that are separate from the “happy” path. Just as important, Sonic offers the unique benefit of enabling you to orchestrate services using BEPL or itineraries—whichever is optimal for your process scenario.

Be sure to watch the Sequencing and Error-Recovery webcast and download the technical brief to learn more about the Seven Points of Mediation and the importance of each in relation to supporting a truly agile and responsive business application infrastructure.

---

Check out all of the Enterprise Integration Whiteboard Series white papers and videos here!

The Seven Points of an ESB

When discussing an ESB, many people keep it simple, sticking to the generalities of SOA and sharing services to build composite business applications.  Certainly, these are incredibly important benefits of an ESB but what do these dicussions really mean at the architecture level? 

Another word for integration when it comes to ESBs is mediation.  After all, that is truly what an ESB does - mediates the differences between application components (services) that were not intended to work together.  So then, in context of mediation, how should an ESB be examined?  Here at Progress, we view there to be seven points of mediation that serve as a set of key principles that apply to any integration infrastructure. They are critical because adherence to all seven is necessary to achieve the ultimate goals of SOA: reuse and agility.

Any one point that is not mediated becomes a point of brittleness. Put another way, interoperability needs to be tested along seven key points, which, briefly, are:

7 POINTS OF MEDIATION
Transport/Protocol
Location/Destination
Semantic/Format
Sequencing
Error Recovery
Quality of Service/Quality of Protection
Interaction Model

To help examine these points in-depth Progress has created a series of technical briefs (white papers).  These papers use the 'Seven Points of Mediation' as a way of describing how an ESB is, in fact, a comprehensive infrastructure onto which services can delegate these points. The overriding idea is that if a service delegates each and every point of mediation, it becomes more reusable in more contexts. These papers explain how Sonic ESB enables a service to free itself of these considerations, ultimately, so that it can provide the agility that SOA promises.

Be sure to watch the Transport, Location, and Semantics podcast and download the technical brief to learn more about the Seven Points of Mediation and the importance of each in relation to supporting a truly agile and responsive business application infrastructure.

---

Check out all of the Enterprise Integration Whiteboard Series white papers and videos here!

Dynamic Routing Architecture - Strength Comes from the Core

This week's deep dive into the gears of Enterprise Integration take us to the Dynamic Routing Architecture or DRA.  SonicMQ's Dynamic Routing Architecture (DRA) technology allows the delivery of messages between applications regardless of the cluster that the application is connected to. In case of a connection failure, (e.g. between regional offices), DRA will route messages via alternative operational paths, and facilitate expansion without incurring significant administrative overhead. Clusters may connect to other clusters as needed, creating highly distributed deployments across loosely-coupled locations.

As mentioned in the first series brief, “Messaging Architecture,” every Sonic broker has a set of acceptors that define it’s connectivity to the rest of your messaging architecture. These can play three roles: as a client link, as an inter-broker link (in a cluster) and as a DRA link enabling two clusters to communicate across a WAN. In addition, because Sonic acceptors can handle multiple protocols, the DRA link can work over other various types of connections as well.

But, DRA goes beyond the Sonic clustering architecture. It optimizes communications in many complex, distributed topologies while providing administrative transparency, or single-entry administration. As a result, DRA enables easier scaling and greater agility in changing the IT environment to meet changing business needs and market
conditions.

Be sure to watch the DRA video podcast and download the technical brief to learn more about how DRA provides unmatched high-availability and delivers transparency and administrative efficiencies that truly ripple to both the bottom and top-line of business activity.

---

The forth brief and whiteboard video in the Enterprise Integration Whiteboard Series, Dynamic Routing Architecture,  explains how the Progress enterprise integration solutions work. This brief focuses on the Progress® Sonic® Dynamic Routing Architecture® (DRA), its purpose and capabilities over and above the Sonic clustering architecture as well as some special use cases..

Integration & Performance - It's all about the Clusters

As we continue our series on Enterprise Integration as a foundational element for Operational Responsiveness we venture into the world of Performance, Scalability and Reliability.

These characteristics are vital to distributed networks, and in large part, depend on transparency in the cluster to be fully realized. A cluster is a number of independent machines that behave as though they were one single logical entity. The rationale for clustering is that this single logical entity will easily scale and provide uniform performance: if one member fails or goes offline, messaging can continue. There are three dimensions of transparency that can be examined to determine the efficiency and effectiveness of an enterprise messaging solution in delivering this vision. These are administrative transparency, functional transparency, and high-availability and load-balancing transparency.

Check out the complete discussion on this topic by viewing the video podcast whiteboard session or downloading the transcript as a technical brief.

The second brief and whiteboard video in the Enterprise Integration Whiteboard Series, Clusters and Technologies, examines how the Progress enterprise integration solutions work. This brief focuses on administrative and functional transparency in the cluster architecture of Progress® Sonic® versus its competitors, showing why Sonic provides greater operational responsiveness at lower cost.

Integration and the Responsive Enterprise

Over the last year you’ve heard a lot about Operational Responsiveness from Progress and what it means to and for your business - the ability to:

• Respond to changing business conditions as they occur;
• Capitalize on more opportunities, to drive greater efficiencies;
• Make real-time course corrections;
• Reduce risk.

Every business and enterprise wants to be operationally responsive, but getting there is the challenge. Certainly, our recently announced Progress® Responsive Process Management (RPM) suite makes this challenge easier by enabling business users to gain visibility into critical processes, immediately respond to events, and continuously improve business performance without disrupting existing infrastructure. But what about that infrastructure? What role does that play in responsive process management and Operational Responsiveness?

We believe it plays a foundational role and that is why we’ve created a completely new set of educational and informative videos, whiteboard sessions, podcasts and technical papers that services and application platform architectures in the context of Operational Responsiveness.

Beginning with four podcasts and technical papers on messaging, the Enterprise Integration Whiteboard Series will explore services integration, data connectivity, transformation and life cycles, legacy modernization, and management as core, interdependent components of every modern enterprise application integration infrastructure. In total the series will consist of 10 topics with a new topic posted every two weeks through September 2010.

The first brief and whiteboard video, Messaging Architecture, examines the four basic components of the Progress® Sonic messaging system --brokers, acceptors, clusters, and the underlying protocols—to show how they provide not only robust integration, but business and IT benefits as well.

Read the paper and watch the video and let us know what you think by commenting to this post. Share your enterprise integration experiences.

The Industry’s 1st and Best ESB Just Got Better

On Monday we announced the release of Progress® Sonic® 8.0. Sonic 8.0 enhances existing SOA infrastructure and enterprise integration by introducing the power and flexibility of an open services and integration standards development model. It’s ideal for multi-site operations management and deployment because it is backed by the industry’s only true, 100% up-time enterprise messaging environment. Here is what current and new users can expect from Sonic 8.0:

• Open services and integration standards
• Distributed Operations Management
• Continuously Available Business Systems
• Real-time Management & Security
• Semantic Data Transformation
• Legacy and Mainframe Integration

Learn more about Sonic 8.0 >
Take Sonic 8.0 for a test drive >

SOA Upgrade to British Airways

British Airways (BA) is turning to service-oriented architecture (SOA) and Progress Software to connect over 600 different electronic systems and processes involved in getting BA passengers in the air.

BA has more than 250 key applications distributed over 300 locations around the globe, which explains why they chose Progress. From an integration perspective, Progress® Sonic ESB® excels in those scenarios that require the integration and management of hundreds or even thousands of systems. One Progress customer was able to deploy its integration backbone out to 25 locations a day (and can update them in a fraction of that time).

One can only guess how many of those 250 systems are touched when you travel BA. Everything from choosing your seat assignment to charging your credit card (once only please), to selecting a vegan meal is managed via systems. And let's hope those systems succeed in keeping track of your luggage.

The real-time data synchronization of Progress® DataXtend® Semantic Integrator (SI) allows BA to significantly improves information quality while reducing costs associated with data replication. And Progress® Actional® SOA Management provides BA with the visibility they need to make sure your reservation gets booked and you make it to your destination in a timely manner. Weather permitting, of course. ;)

Thanks to SOA, BA is able to extend the features of its e-commerce site right through to its airports, allowing greater self-service functionality and 'plug and play' capability to over 25,000 users.

"Moving this to a highly automated environment is a challenge, but SOA quickly proved itself to be the right approach to achieving our goal of a fully agile environment."

So the next time you take your family to London (or Disney - that's my family's destination of choice at the moment), think about how many transactions went right along the way, automatically.

I love when technology makes a tangible difference. Pretty cool stuff.

CORBA is now Actional-ized!

This is really cool, and I can finally speak about it. Wow, gag orders just don't work very well for me. I mean, I can keep a secret, it's just that the really juicy ones are harder to keep than the others! And, this one's juicy. Ready...

Today we will release Orbix 6.3.4 with support for Actional.

Whoa! I bet at this point a lot of you are like SOA What? (yeah, remember that blog-ism we did here back when SOA was cool?)

Well, let me give you end-to-end visibility into the import of that sentence above.

As with all the other technologies we cover, including the recently announced SAP ABAP integration, Actional integration with Orbix gives customers:

1. End-to-end message flow visibility across an entire CORBA environment, in run-time, without any impact on performance or scalability. That same visibility extends beyond CORBA, and does so consistently to provide a unified view of message flows and business transactions in their environment.
2. The ability to centralize run-time policy creation, allow for distributed enforcement across multiple environments, and to ensure compliance with corporate and regulatory policies across the entire messaging infrastructure.
3. The same tools our current customers have that help them achieve an 80% reduction in time to resolving critical production incidents and a 20% reduction in major production incidents per year by simplifying root-cause analysis and problem resolution.

Now, you might think with all these great benefits, there would be a high cost. Nuh uh!!!

• No additional coding changes to get this up and running. Instrumentation of all CORBA services is automatic.
• No architecture changes, Actional won't impact scalability.
• No extra capacity required, Actional won't impact performance.
• No additional staff are required, dependencies are dynamically discovered and maintained to help keep the cost of ownership low. In fact, case studies independently verified by Forrester Research of our customers who are in production showed a rather quick payback of the investment due, in part, to the low cost of ownership.

Of course, if you follow Actional and Progress at all, awesome technology is old news. Actional has been working on non-SOA distributed applications since early in the development of our product and anytime we add a new technology, protocol, or platform, we've always added the same rich features, while maintaining the enterprise-class performance. Let me say that again, because I've accidentally brought up a very important point.

The single Actional Agent adds all of the functionality, across all of the protocols and platforms, and provides the same outstanding performance you've come to expect from us. In contrast, many other vendors can support all the platforms/protocols, and all the business-transaction-management features, and do so non-intrusively... but THEY CAN'T DO IT ALL AT THE SAME TIME!

Back on track, sorry for the diversion. I'm almost done here, I promise.

There are other equally interesting implications from this release that I'd like to share (in no particular order).

1. This helps to, in part, validate the strategy that lead us to acquire IONA in the first place. There are a lot of cross-product synergies.
2. This continues to prove the applicability of our technology far beyond the common understanding of SOA infrastructure (SOA and HTTP/JMS). We have successfully broken out of the "SOA management" niche, and are providing real value to customers across the entire breadth of business transaction management needs.
3. In this "recovering" economy, Progress can help customers gain more value from their legacy technology investments by upgrading the capabilities in mission critical platforms like Orbix/CORBA. Whether it's from the operational perspective of lowering their operating costs while providing higher-levels of service, or from the business perspective of preventing "revenue leakage", Actional solves real-world problems without impacting the architecture or requiring coding changes to existing applications.

In closing, I wish I could share some of the early adopter customer quotes here. I can't, but the feedback from the (former) IONA field was equally funny. The IONA field is (relatively) new to Progress and hasn't necessarily developed the instant-automatic love for each-and-every Progress product because we all share a logo color scheme. We actually had to prove ourselves to these guys and gals (a very capable team I might add). Once the engineering team was finished, they took the early software and implemented it at some rather large (and equally skeptical) customers. After running it through it's paces, people were actually smiling. When was the last time you saw beta users smiling at performance results? To quote one guy working at a large airline... "it simply worked the way it should."

Beat that!

Now That's What We Mean By Performance!

Was visiting a customer in Switzerland last week and a funny thing happened.

They presented us with where they are in their deployment... they've deployed their first "major" application early last year (Inventory Management), and this year are planning two more applications in the suite to be deployed in 2010 (E-Ticketing & Centralized Checking-in).

They're using a very old version of Actional (v6x), and I was hoping to help them understand why it was important to upgrade to the current release (v8.0). The Inventory Management application contains about 300 applications (including TIBCO BusinessWorks and Oracle/BEA WebLogic Server), and is designed for 400 million messages per month. They're currently doing about half that. (It was really cool to see the Actional console with those sorts of numbers in the dashboards!!!)

Each of the new applications will probably add a similar amount of traffic. 1.2 Billion messages per month. Surely, there's my in.

I started talking about how we've made major improvements to auditing performance, user-interface usability in large scale environments, and CPU and memory utilization, along with general performance improvements you'd expect in two years of development. I was sure this was a certain driver for them to upgrade to a recent version, when the lead architect from Progress leaned over, and whispered in my ear...

The current architecture's not even breathing hard. Even with that traffic growth, we'd probably only be at 30-40% of design capacity.

What can I say? We have a really fantastic engineering team.

And, I'll have to work with the customer on building a business case for upgrading using a different angle.

Five Dirty Little Secrets of Highly Available Integration Infrastructure

Even some of the world’s largest, most demanding companies suffer from a hardware, software, or network failure. Learn more about how a continuous availability solution will protect you from lost transactions, and guarantees in-order delivery without the cost and management complexity of the 3rd party hardware or software add-ons.

Register to download our new white paper, Five Dirty Little Secrets of Highly Available Integration Infrastructure. Topics presented in the white paper include:

• Recovery Time
• Data Corruption
• Hidden Cost and Complexity

... and those are just three secrets. Download the paper >

Meaningful Measurements

At our annual sales kickoff in Miami last week, I heard a story about one of the Regional Sales Managers that put a smile on my face, and it made me like Progress a little more. When asked by the CFO how he did last year, the regional sales manager responded "six cents".

Six cents. Huh?

Well, apparently there is a culture here at Progress that you look at regional profitability, and then each sales manager knows how their deals affect the company's bottom line. Being a numbers geek, and one who likes to measure things properly, I think it's cool.

SOA What? Well, I also heard a story about a new Actional customer who had over 98% up-time for their IT systems last year - a number they were proud to report. (Realizing, of course, that each industry has its own benchmark for up-time.)

They were proud to report it but it was meaningless to do so...

Why? Because as it turned out, while they had this brilliant up-time of their underlying infrastructure, something was preventing their largest customer from receiving any information for over three weeks. Do the math, 52 weeks in a year - down for 3, that's almost 6% downtime.

Where was the discrepancy?

The IT team was not tied into the business and was assuring system up time but NOT assuring their business transactions. So now, in order to gain credibility with the business and to make more insightful technology decisions in support of the business, the team chose Progress Actional as the management solution for their SOA and distributed applications (links to good article on what this is about by Anne Thomas Manes). Hopefully, they'll do better next year.

Have you ever had a situation, even in your personal life, dealing with a company's technology where they say all the systems are up but still, it's not working? Create a comment here and share your stories...

"But, what do you DO?"

My grandfather's curiosity makes him seem younger than his 90 years. After the war, he, an immigrant in NY, became, among other things, a tailor. For the past 10 years or so, each time I've visited, at some point the conversation would turn to my job, and he would pointedly ask, "But, what do you DO?" I didn't quite understand his emphasis on "do." So, I'd respond that I travel, talk to people, listen a lot, and ultimately advise customers and our field on ways to move opportunities forward. I'd give examples. In return, I would get a confused look and a repeat of the question, "but what do you DO?"

Finally, one day in exasperation he says, "When I went to work, I made clothes. When you go to work, what do you DO?" Now, that was awkward... you see, I don't really DO anything. I'm an enabler. I'm more like a carrier of a disease than a tailor. I travel around picking up experiences in one place and leaving them in another.

I know... fascinating. But, SOA What?

Well, we just had our annual sales meeting here at Progress. And, coming off a great year, we Actional people were pretty popular. I was delivering the Actional message to a group of new employees - which I consider the 2nd most fun thing I get to do all year - and they kept asking, "what's the business benefit of Actional?"

What's the business benefit of Actional?

I'm not going to answer that here. Suffice it to say that my answers left the people in the room last Sunday somewhat unsatisfied. They wanted something tangible to take to their prospects--something that would quickly and dramatically get their attention and priority. I gave them talking points that they could use to start conversations, but nothing that would turn people's heads. The whole thing got me thinking...

Can an enabling technology have a direct business benefit?

Notice the word direct. I think an enabling technology enables business benefits. But, it requires some deeper understanding of the business situation, and then the application of technology expertise to that situation in order to achieve some tangible benefit.

An example will help. Actional has a large number of travel and hospitality customers. We help them optimize their delivery of product across various channels. Using Actional, these companies are able to differentiate service levels by customer, channel, and dynamically based upon, among other things, immediate local market conditions. In one case, a company has saved millions of dollars on hardware investment by better utilizing their shared infrastructure. They optimize their SOA infrastructure based upon "business level SLA," rather than blindly adding capacity. In short, they more closely coupled their "business" with their "infrastructure." These benefits apply equally well to any services business, and in my opinion will be a critical differentiator in the coming years.

If you look at the benefits I just described, you might think we compete with a highly customized point-of-sale system, or some reservation system, and probably a bunch of other things, however, as much as people want the "soundbyte", it's simply not the case. We don't really do anything tangible for these companies, though we are a key part of their enterprise infrastructure for delivering a highly differentiating service. I think there was a Dupont commercial that summed it up quite well... "we don't make your business systems, we make your business systems better."

Once my grandfather realized I didn't actually "DO" anything, he was able to start to understand what I accomplished. Perhaps we need to look at enabling software the same way?

Buying and Driving your SOA

When I get around to buying a new car, I know what is important to me. Being 6 feet 4 inches tall the first criteria is whether or not I can sit comfortably and see myself driving many miles, and then small things become important, like whether I can see the lights at an intersection. The comfort criteria is independent of the car and must be applied to all cars that I try, although I do like the image of relatively fast cars. When you look at what I drive, it might surprise you, I have a Ford Focus SVT which is good for 140 mph and 0-60 in about 6-7 seconds I am told. Many people have asked why I do not drive a SUV or similar and the reason in many cases for me is that they typically have less room for a driver of my proportions than my Focus.

When I bought my car, there was a lot I already knew. Having driven many cars, I knew where the steering wheel, radio, rearview mirror, etc. were and I knew that I could drive the car without a specific driving course, although to push the limit and understand how it would go 140 mph on a sweeping right hander would probably require a day at some race track. My wife on the other hand has to transport kids to the school and to soccer practice so her vehicle of choice is a minivan.

Now that I have shared with you some of the reasons how my family chooses cars, you may be wondering how this relates to SOA. Well, last week in a meeting with customers and prospects alike, I was getting questioned on selection criteria for ESBs and SOA infrastructure technologies.  And in nearly every conversation, the same criteria was clear - how many messages per second, how much memory, etc. etc., and only a few really came up with a statement such as "We are facing challenge X and would like to solve it?" This is the most important question because just like my car challenge of "sitting comfortably for long periods of time" outweighs the need to do 140 mph (which I have yet to do), if I bought a car that does over 150mph, it would probably be gone by now as it might not meet my primary needs. And lets face it, how fast do any of us really need to drive? Even the cheapest car on the market will do 80mph all day.

Using standards such as Web-Services, JMS, etc. also means that developers can apply the same disciplines to one technology as another - in much the same way that most drivers can switch cars. If it did not, Hertz and other companies would not be in business. Which brings me to the second theme of questions and comments I was getting, "What do my developers have to learn to be successful?" They have to learn to transition from one environment to another but still be able to apply the same core software engineering practices. For instance, you would not write all your business logic in one Java class so don't do the same in one ESB process. In CORBA you would not make every object accessible, so why do you try to make every Java object a web-service?

SOA What? Buy the technology that makes sense for you and your business, e.g. if you are a distributed manufacturing organization build/buy a SOA that can be deployed and managed in a distributed manner.  If you are dealing in high volume transactions or events, you will, like a racing driver, need to look into performance. Once you have chosen your SOA technology, remember to still stop at red lights, and not to redline the engine at every gearshift. The speed limits may have increased, and you can break them later, but they still exist. And just like I would get special tuition to drive safely at 140 mph, remember to call on the experts of your SOA to drive at the limits.

9-Reasons to Use Sonic for Your Next IBM Websphere MQ Project

You have to simply stand back and admire a crisp and clear expression of a product's differentiators in a complex and competitive market. Working with some of our recently-delighted customers, erstwhile subscribers to IBM blah-blah-blah, our Sonic team developed this crisp expression of Sonic's advantages over IBM -- and where in an IBM Websphere MQ deployment you are likely to find them. Hat's off to the Sonic team!

Nine Reasons to Consider SonicMQ for Your Next Websphere MQ Project

• Because… when a broker fails, SonicMQ provides a hot mirrored backup broker so that:

  1) No messages are trapped in the failed broker.
  2) There is no need for specialized disk devices or expensive hardware.
  3) There is less error handling code needed in your applications.

• Because… when a network connection fails, SonicMQ provides automatic reconnection to the hot mirrored backup broker so that:

  4) There is no loss in state associated with the message exchange.
  5) There are no lost messages between your application and the broker.
  6) There are no duplicate messages or out-of-order conditions as a result of restarting the application.

• Because… when anything changes in your broker or client deployment, SonicMQ provides distributed configuration management so that:

  7) You don’t have to spend time assessing the impact to your topology
  8) You don’t have to find and update dozens or even hundreds of configuration files across multiple possibly remotely located machines.
  9) You don’t waste time debugging all those manual configuration changes or rolling back your changes.

If these nine reasons aren’t enough to convince you that your next WebSphere MQ application isn’t better served by SonicMQ, then we’ll have to give you the names of our capital markets clients, airport operations clients, medical device clients, ERP vendor clients, and the guys who run the large hadron collider in Cern, Switzerland. Maybe they can convince you.

Progress SonicMQ—when you and your application can’t tolerate non-sense anymore.

SOA What? Best-in-Class independent vendors have to sharpen their knives as the saskwatch-footprinted stack vendors begin to tread on their space.  Only by finding crisp and specific, and deadly, points of vulnerability can the smaller upstart continue to thwart the giants.