Migrating Existing PowerBuilder
Applications |
| Step1. Analysis |
|
| Analyze the PowerBuilder application
for PowerBuilder features that cannot be converted
to the Web. Identify mission critical unsupported
features.
Our analysis report highlights PowerBuilder objects the application that are unsupported.
|
|
| Step2. Modification |
|
Rewrite unsupported PowerBuilder features that are critical to running the application in PowerBuilder. All work is done in the PowerBuilder IDE using only standard PowerBuilder skills. Test PowerBuilder application.
Your application is now ready for automatic deployment to the Web.
|
|
| Step3. Web Deployment |
|
| Deploy the PowerBuilder application to the Web at the click of a button.
The resulting standard Web application has the same user interface, logic and data as the PowerBuilder client/server application.
|
|
|
|
| Developing New Web Applications |
| Step1. Design |
|
|
Design a new Client/Server application that complies with Appeon guidelines and project requirements (i.e. functional specifications).
Application has design specifications that will serve as the blue print for coding.
|
|
| Step2. Develop |
|
|
Build quickly with PowerBuilder a new Client/Server application that complies with Appeon guidelines. Test application for software defects.
Your application is now ready for automatic deployment to the Web.
|
|
| Step3. Deploy |
|
|
Deploy the PowerBuilder application to the Web at the click of a button.
A standard Web application with the same user interface, logic and data as the entire PowerBuilder Client/Server application has been successfully deployed. |
|
|
|
