The following are recommendations for handling the different types of applications.
Type 1 applications: This type is ready to be migrated. There is no additional work to do. PowerServer reads the PowerBuilder PBLs and generates the n-Tier Web application. The Web application will have DataWindows, business logic, and UIs identical to the original PowerBuilder application.
Type 2 applications: The developer needs to remove the unsupported features and Client Server specific functions from the application that cannot be implemented on the Web to ensure that the Web deployed application functions in the same manner as the PowerBuilder application. If the application is large and complex, PowerServer suggests splitting it into smaller applications to simplify the debugging of the application. Remove as many minor and unnecessary features as possible. Simplify the code and object interdependencies to make the application more straightforward. The DataWindows and a good portion of the PowerBuilder source code can be utilized. The amount of PowerBuilder source code that can be reused depends on the actual application's complexity and the user's requirements.
Type 3 applications: These generally cannot be migrated to the Web as-is, but the DataWindows and other useful objects can be exported and used to rapidly build a more straightforward PowerBuilder application using standard PowerBuilder programming.
The ultimate aim of the guidelines is to help you modify the PowerBuilder application and make it well supported by PowerServer. The existing DataWindows may be used. Depending on the application type, modify a fraction, a part, or all of the PowerBuilder source code.
