Documents » bpel evolveware.
Abstract: To date, the best option for discovering and extracting information from software applications has primarily been manual, with automation tools serving in support. These initiatives are tedious, long-term, and high-risk. Companies try to lower monetary cost by outsourcing such projects. However, the time to completion and risks remain unchanged at best. The solution? Automated documentation and transformation of software applications.
PubDate: 12/14/2006 4:43:00 PM
Abstract: In the larger schema of things, SOA would espouse general, more abstract concepts of software reusability and encapsulation within certain boundaries (as to then provide access to that software via defined interfaces), Web services would then make these SOA concepts vendor-independent due to their use of generally accepted standards, while BPM and BPEL would be some of the engines making the whole system work.
Abstract: It’s estimated that almost one trillion lines of legacy code are in active use around the world today. If this code is going to be migrated, it’s vital that a methodology be put in place for substantial automation; otherwise the highly tedious process will serve as a major impediment to this important initiative. So what are your options today?
Abstract: Time will tell whether Oracle's vocal endorsement of open technologies such as J2EE and BPEL will allow customers to readily adopt solutions that fit their needs and that quickly integrate with their existing infrastructure.
Abstract: With the acquisition of Collaxa, Oracle has quickly plugged a hole in its SOA/BPM message by providing new workflow capabilities and monitoring tools to report on the progress of business processes, and by providing runtime support for BPEL.
Abstract: In a somewhat simplified language, while Web services allow applications to easily exchange and reuse information, it is only when they are orchestrated (coordinated) into long-running business flows or processes that enterprises can realize their true value.