|
 |
| |
| |
General Requirement |
| All PowerBuilder Client/Server applications should comply with the following guidelines before being deployed to the Web:
|
- PowerBuilder 8 or 9 compliant. All code contained in the application must be upgraded to PowerBuilder 8 or 9 syntax.
- Smaller than 100 MB. Applications larger than 100 MB should be broken down into separate modules that are smaller than 100 MB each.
- Free of "critical" unsupported features. The PowerBuilder application should not contain unsupported features that are critical in running the application in PowerBuilder. Such unsupported features are automatically ignored by Appeon on the Web, and will therefore cause the Web application to break.
- Uses a certified database. The application should only use the following DBMS: Sybase ASE, Sybase ASA, Microsoft SQL Server, Oracle, or IBM DB2. Other DBMS are not certified and could potentially be problematic.
|
| |
|
| |
In order to realize acceptable Web runtime performance, Appeon strongly recommends that your PowerBuilder client/server application comply with the following guidelines:
|
- Reduce excessive data retrieval. Reduce the size of the data sets requested, especially their size in rows but also their size in columns, makes dramatic performance improvements. Appeon suggests that you retrieve larger results sets in chunks, much like how in JSP or ASP Web applications you would click Next to view the next 50 or 100 results. Besides, reducing the number of columns requested to the precise set of columns needed can also correspondingly reduce your Web-enabled application timings.
- Thin-out "heavy" windows. Windows become "heavy" when they contain 10 or more DataWindows. The Tab control should also be avoided as it encourages a large number of DataWindows to be piled into a given Window. You can implement each Tab page as its own Window.
- Decrease "global" overhead. You can decrease the "global" overhead by reducing the number of "global" PowerBuilder features, such as global functions and variables. For example, in many situations it may be possible to replace global functions with object functions, and replace global variables with local or instance variables.
- Consolidate business logic into NVOs. The client-side processing can be thinned out quite a bit if the business logic is moved into NVOs and deployed to Appeon Server. Such partitioning of business logic is not required but it is a highly recommended practice even for traditional Client/Server development with PowerBuilder.
|
| |
|
|
| |
|
