＋设为首页 ＋添加到收藏夹
get ready for another acronym - hats (host access transformation server). lets begin with a notional conversation - an "elevator pitch" of sorts - between two it managers, jim and dennis.
jim: hey dennis, i hear that we can now create journal entries from our intranet. how is that possible? did we contract that same outfit to build us another application?
dennis: not really; were using websphere hats.
jim: never heard of it. what exactly is that?
dennis: oh, its very slick. its an extendable framework that can transform legacy application screens into web browser content - in real time. you can now click your way through journal forms in a browser instead of special-keying your way around the 3270 emulator.
over 60% of the worlds software systems are considered legacy: so-called "green-screen" applications - with line-oriented user interfaces, generally hosted on mainframe-size computers, and implemented in languages like cobol and rpg. theyre likely accessed through special terminals or terminal emulator types such as 3270, 5250, and vt.
legacy applications typically represent significant investment and tend to support critical business operations. it organizations are experiencing unprecedented budget cuts, and it would be reasonable to surmise that legacy applications wont be going away any time soon. this is much to the chagrin of many end users and business-unit managers.
while legacy applications are typically "well-oiled machines" that perform their functions efficiently and with predictable response times, their overall presentation and usability often leave a lot to be desired. a line terminal interface can be nonintuitive and difficult to navigate. furthermore, each legacy application can be limited to a narrow band of functionality - as they were often designed with functional compartmentalization in mind.
this can present a situation in which no single legacy application supports the job function of any given staff member. at best, this leaves users bouncing from one legacy application to another. in the worst case, related information is simply not accessible by the users who would benefit the most, and crude workarounds are sought.
fortunately, what most organizations actually have is a hybrid environment - one in which legacy systems coexist with a modern enterprise platform (i.e., desktops, browsers, j2ee, .net, etc.). these organizations can now be offered an opportunity to leverage their legacy systems with their investment in a 21st century enterprise by creating composite applications.
composite applications draw upon an architectural ... 下一页