All PowerBuilder Client/Server applications should comply with the following guidelines before being deployed to the Web:

• PowerBuilder 9 , 10 or 10.5 compliant. All code contained in the application must be upgraded to PowerBuilder 9, 10 or 10.5 syntax.
  
  
• 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.

• 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.

• Consolidate DB server calls. Minimize the number of calls to the server by limiting the usage of these statements:
  •  Retrieve and Update functions for DataWindow and DataStore. 
  •  Select statements
  •  Cursor statements
  •  Call for stored procedures  

• Partition business logic into server-side components. The client-side processing can be thinned out quite a bit if the business logic is moved into NVOs, EJBs or Web Service. Such partitioning of business logic is not required but it is a highly recommended practice even for traditional Client/Server development with PowerBuilder.