The fully automated ATPconvert™ toolset is the engine behind ADABAS conversion into the relational database technology of your choice: SQL Server, Oracle, or DB2. The ATPconvert process includes the generation of the new database definitions, population of the tables with the current ADABAS data and allows for data cleansing activities.
After Natural replatforming, the original code seamlessly processes against the new relational databases without modification using the ATP runtime. As an added bonus, modern web applications can access the relational databases directly, allowing the organization to benefit from industry-standard SQL-based reporting, query, and business intelligence tools.
ATPaccess™ enables Natural replatforming and ADBAS conversion without affecting the business user experience. The functionality remains the same, so no training is required. All screens retain the same user-created look and feel. Even the keystrokes, tabbing, and PF-keys remain unchanged. It is easy to update the default colors and backgrounds, but user interface changes are optional.
In addition, developers gain a method for communicating with users via an application portal and message board. Notices can be issued on a per entry point basis so maintenance time frames or other user messages can be customized for each application.
Numerous factors are driving companies away from legacy platforms, but change can be risky. Replatforming is a good way to move to distributed platforms, eliminate licensing charges, and retain legacy source code, allowing existing developers to continue to work with programs they are familiar with in the syntax they know. Be sure to browse the myriad of resources we have available below on Natural replatforming and ADABAS conversion with ATP.
ATP Received Microsoft's Platform Modernization
Technology Achievement Award 2012