How does the world deal with omnipresent legacy platforms? Means to update them include rewriting apps, re-hosting...
apps, or wrapping the system in-place with services. In fact, such legacy mid-range and mainframe host integration via XML and Web services is one of the more common, though not widely touted, examples of SOA today.
A recent move in the legacy-to-SOA modernization space sees Attachmate enhancing its Verastream Host Integrator (VHI) with added WS-I compliant Web services. As well, VHI 6.6 has added FIPS-certified Crypto libraries and Native .NET client support.
Also added is a team process modeling feature that lets multiple developers work on a single model as can be found in formal cross-group SOAs. Such modeling support proves to be useful as the needs and the size of the projects have grown.
The Verastream platform helps teams gain a handle on component complexity levels that can be hard to coax out of legacy systems, said Ron Nunan, senior product manager, Attachmate. Updates in the latest rev are designed to help people pursue a formal SOA with legacy.
Rolling through the application
"As the enterprise has come to believe in the value of a service architecture, reuse has become an attribute that drives adoption," said Nunan.
"The issue we look to resolve has to do with legacy application architecture," he said.
"Most legacy applications are monolithic in nature. They never were meant to be made in a services architecture. Data access logic, business logic, workflow and UI [logic] are intermixed."
VHI sorts through that. "We don't touch the code. We have a visual design environment that 'picks routines' by rolling through the application," said Nunan. "We call it modeling the application."
"The design environment builds services that you interact with," he said. "You have and EJB or a Web services and, when you call it, Verastream takes that and returns the results. It's fenced-in access to the application."