More firms using Web services to integrate legacy apps

Products from the established mainframe players “make sense if you have investments in those technologies” that you plan on keeping for the long-term, says Ron Schmeltzer, senior analyst with consultancy ZapThink LLC, in Waltham, Mass. But if you have older technology and are not looking to upgrade, it might make more sense to go with an independent software vendor for Web services help.

Read more at: TechTarget

SOA Tools and Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.

SOA Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra

SOA Tools

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best pra

Service-Oriented Integration

Connecting systems both within the enterprise and with suppliers, partners, and customers is of critical importance to today’s enterprise. However, integration remains complex, expensive, and risky. While Web Services won’t be the magic bullet that immediately solves these problems, they enable a new approach to integration. Service-Oriented Integration (SOI) leverages open standards, loose coupling, and dynamic description and discovery capabilities of Web Services to reduce the complexity, cost, and risk of integration. This report identifies the key aspects of SOI, solutions for implementing SOI, ROI metrics, and critical challenges.

ZapNote: iWay

Subscribe Today to Get Access!

Service-Oriented Integration

Connecting systems both within the enterprise and with suppliers, partners, and customers is of critical importance to today’s enterprise. However, integration remains complex, expensive, and risky. While Web Services won’t be the magic bullet that immediately solves these problems, they enable a new approach to integration. Service-Oriented Integration (SOI) leverages open standards, loose coupling, and dynamic description and discovery capabilities of Web Services to reduce the complexity, cost, and risk of integration. This report identifies the key aspects of SOI, solutions for implementing SOI, ROI metrics, and critical challenges.

SOA Tools & Best Practices

From its inception through 2002, the primary application for Web Services in the enterprise was to simplify point-to-point integration between systems, thereby reducing the cost of integration. This application of Web Services, however, only scratches the surface of the true potential of Web Services — enabling companies to build agile business processes and IT systems that can respond to change through the use of loosely coupled, standards-based Service-oriented architectures.

The business value of such architectures in terms of the business agility they provide is substantial, but as of early 2003, only a few early adopter enterprises have built such architectures, partly because few tools for building Service-oriented architectures are available on the market, and furthermore, there is little understanding of the best practices companies should follow to build such architectures. This report seeks to clarify the requirements for realizing the value of Web Services by providing a set of emerging best practices as well as an analysis of the tools that are currently available for building Service-oriented architectures.

ZapNote: SEAGULL Software

The vast majority of legacy applications are isolated from the Internet, and none of these legacy systems were designed for the Web’s user experience. As a result, a variety of technologies have been developed to extend these systems. SEAGULL’s Transidiom product provides a unique, non-invasive solution that leaves legacy applications unaltered while complimenting existing investments in EAI, middleware, and Web application platforms. The system can create a composite application, capture and publish legacy business processes as Web Services.