HIGHLIGHTS Logimethods’ automated ESB migration approach:
- Cuts time to migrate
- Results in up to 50% cost reductions
- Eliminates the risk of human error
- Preserves 100% of the business logic implemented in the legacy ESB
- The technology is proven and 100% reliable for mission-critical systems
- References from major organizations: error-free code, on-time delivery and successful go-live
KEY DRIVERS FOR ESB MIGRATIONS
Some of the choices and decisions made by ESB/SOA technology customers over the years have led them to a dead-end, as their current Enterprise Integration infrastructure doesn’t provide a suitable foundation on which to build for the future. There are many reasons for companies to want to reconsider how integration capabilities are delivered, including:
- Mergers & acquisition driving a new integration strategy
- Vendor consolidation
- Enterprise-wide integration initiatives
- Technology initiatives requiring new capabilities (e.g., IoT, Analytics, Cloud)
- Vendors introducing next-generation ESB versions lacking full backward compatibility
- Concerns or risks with the incumbent supplier and its commercial and licensing practices
- New pricing models providing a better TCO
COMMONLY USED STRATEGIES
IT Executives have few options to choose from when faced with the ESB migration problem:
A new platform for future projects – Adopt a new platform on which future solutions will be built. The existing integration portfolio is treated as legacy. Projects to slowly migrate existing integrations to the new platform can take years to complete.
Rip and Replace – Adopt a new ESB platform and launch a full-scale migration project in order to decommission the legacy ESB.
Status Quo – Accept the solution roadmap and timelines proposed by the incumbent vendor. For time-sensitive needs, the customer must supplement the vendor’s stack with commercial add-ons, custom developments, or both.
A NEW APPROACH TO ESB MIGRATION – TECHNICAL BREAKTHROUGH
Logimethods’ unique technology and delivery approach provide companies with a compelling alternative for migrating to a new ESB platform. Logimethods’ ESB migration tool makes the migration predictable, cost-effective and ensures a complete (100%) refactoring of all functionality imbedded in the legacy ESB code. The tool doesn’t rely on documentation that is often incomplete, inaccurate or simply missing. Rather, it extracts all functional requirements from the legacy ESB meta-data and source code and creates a functionally equivalent solution that runs natively on the target ESB platform. In many cases, the resulting solution will be better documented and easier to maintain than the source solution.
In addition, a Logimethods migration services advisor will guide the client through the migration process, as follows:
Solution Assessment – A Logimethods expert reviews the overall architecture of the existing solution and inspects a sample of the legacy interfaces in order to confirm the technical feasibility of the automated migration and to measure the degree of automation that can be achieved. Most projects can be accomplished at a level of 90% or higher.
Project Planning – Logimethods works with the client to identify interfaces that can be grouped into individual phases. Interfaces with commonalities such as SAP interfaces or B2B transactions can be grouped into individual phases. Business priorities and technical dependencies are also factors to consider when defining the make-up and timing of the various phases
Solution Delivery – Working in a factory-like manner, Logimethods migration team receives the source code and delivers the new code according to a pre-approved schedule. The phased delivery approach provides additional assurance to our clients early on that the technology works and that the code produced fully meets their needs. By doing extensive testing using client-supplied test data, Logimethods will ensure that the new code is 100% functionally equivalent to the old code.
A functionally equivalent solution is generated to run on the target ESB. The rigorous testing process ensures a 100% match between the old and the new. The generated ESB code runs natively on the target platform and can be maintained and subsequently modified as any other manually-developed ESB code. There is no dependency on the migration tool once the code has been generated.