* A windows Client Server, fat client or thin client application
* A web application plain old HTML
* A web 2.0 Application, script, Java, ActiveX (with embedded widgets)
* A Java applet or Java Application
* A custom application (Salesforce.com, Oracle Forms, Lotus Notes)
* Packaged Applications
You get the point. If it’s deployed live, it’s legacy.
So, for years we have wrapped green screen applications successfully to enable their business functionality to be consumed by other technologies. Heck, many of your ATM transactions are just plain wrappers on mainframe applications and screens. The good thing about this approach is - IT JUST WORKS (my new motto). So, wouldn’t it be nice if we could “wrap” any application like this, not just 80x24 screens but all the "other" stuff. Well, now we truly can. OpenSpan Studio enables virtually anything that runs on the Windows O/S to be wrapped – exposing the deep UI elements, controls and transactions (robustly and securely) to any mid-tier technology. You can even take any of those legacy applications and move them to the server room (thanks to Virtualization) and run them completely without a user ever needing to see them again! SOA enablement of legacy applications - it's here now.
This approach is crucial is 2009 for delivering quick solutions to the business. IT JUST WORKS.
So, whether the application is 5 minutes old, or 30 years old, if it has a UI, there’s a good chance it will be part someone’s SOA / API strategy in the very near future. Thanks to OpenSpan :)
Look at this quote from an Article on SOA in the SDTIMES last year if you needed any further proof.
The survey found that a majority, or 58 percent, of SOA systems contain components that are not designed to be interoperable as Web services. These include components that use non-SOAP messaging, such as IBM WebSphere MQ and Java’s Remote Method Invocation. Further, mainframe applications show up in 47 percent of SOA applications, and packaged applications accounted for 68 percent of components.