Contact Us
- Email: products@kumaran.com
- Toll Free: 1-800-kumaran
WebNabler
Kumaran Systems has developed an effective and comprehensive Legacy-to-J2EE migration practice. We have migrated a myriad of applications developed in equally myriad technologies to Java for several clients across the globe. Our Legacy-to-J2EE practice is powered by our internally developed re-engineering workbench, WebNabler. It is an effective and comprehensive workbench, which helps us automate the migration process up to 50% of the total re-engineering effort.
What We Offer
Here are some of the salient features of WebNabler:
- Workbench is a collection of tools, each focused on specific source targets of migrating to J2EE.
- Workbench-based automatic migration, as opposed to rewriting, reduces development time because it involves moving to a new system based on business logic, requirements, and functionality that is already well defined.
- Functional testing efforts are reduced to a great extent as the code is generated automatically based on the original source code.
- Automatic migration makes for a relatively low risk development project because of the reduction in time.
- Automatic migration tools accelerate the production of code, after the application has been rebuilt in Java, acceptance testing, integration, and customization are performed.
Business Benefits
Here are some of the business advantages that WebNabler offers:
- Maintenance of Software Investment - By migrating the existing application instead of rewriting it, the organization maintains its software assets and operation procedures.
- Support for Industry Standards - Moving to the latest industry standards is vital in today’s competitive markets. The converted applications are fully Web-enabled as per the prevailing industry standards.
- Efficiency and User-Friendliness - The total user interface is re-engineered to suite the target framework making the system very efficient and user friendly.
- Compliance - The migrated application code is made compliant to the application framework defined in the target.
- Cost-Effective - The cost of a migration is much less when compared to redevelopment.
Kumaran’s Legacy-to-J2EE Migration Practices
With the help of WebNabler, we at Kumaran have set our automation benchmarks at a maximum of 50%. This is because our experience shows that a higher level of automation is not feasible and trying for more brings zero value to the business. It is also not advisable, because it becomes imperative for tools to duplicate coupling logic from thick clients, and this can lead to a tight coupling of Presentation tier, Business tier, and Database/persistence tier. Changes made at any of the tier will enforce changes to be made at other tiers, thus the essence of code manageability will be lost.
Beyond the 50% automation limit, our consultants re-engineer the code and optimize it. This helps create an application exactly as per the client requirements the first time over, reducing iterative development, risk of bugs is also mitigated and the application remains light and highly portable, robust and scalable across the application servers.
Advantages of WebNabler
- Workbench-based automatic migration, as opposed to rewriting, reduces development time because it involves moving to a new system based on business logic, requirements, and functionality that is already well defined.
- Functional testing efforts are reduced to a great extent as the code is generated automatically based on the original source code.
- Automatic migration makes for a relatively low risk development project because of the reduction in time.
- Automatic migration tools accelerate the production of code, after the application has been rebuilt in Java, acceptance testing, integration, and customization are performed.
- Java migration workbench automates the process of migration in a component fashion by addressing various layers of the source application individually. In other words, singular tools help automate the migration of various code components of the source application into the target code. The migrated code is then integrated manually, tested, customized, and optimized by augmented manual services.


