Migration Guidelines for Appeon Web (Web only)

Appeon® for PowerBuilder® 2015


DOCUMENT ID: ADC37817-01-0700-01

LAST REVISED: November 27, 2015

Copyright © 2000-2015 by Appeon Corporation. All rights reserved.

This publication pertains to Appeon software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement.

No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Appeon Corporation.

Appeon, the Appeon logo, Appeon Developer, Appeon Enterprise Manager, ARM, Appeon Server and Appeon Server Web Component are registered trademarks of Appeon Corporation.

SAP, Sybase, Adaptive Server Anywhere, SQL Anywhere, Adaptive Server Enterprise, iAnywhere, PowerBuilder, Sybase Central, and Sybase jConnect for JDBC are trademarks or registered trademarks of SAP and SAP affiliate company.

Java and JDBC are trademarks or registered trademarks of Sun Microsystems, Inc.

All other company and product names used herein may be trademarks or registered trademarks of their respective companies.

Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies.

Appeon Corporation, 1/F, Shell Industrial Building, 12 Lee Chung Street, Chai Wan District, Hong Kong.

Table of Contents

Web RAD with PowerBuilder and Appeon
Traditional approach to Web development
Advantages of Appeon for Web RAD
Leveraged functionality with server components
Appeon Web RAD methodology
Appeon-standard PowerBuilder coding
Migration Process
Installing required softwares
Understanding the general limitations of the Appeon solution
Defining migration objective
Defining migration objective for non-PFC application
Defining migration objective for PFC application
Upgrading the original application
Upgrading obsolete PBLs
Upgrading PFC applications
Preparing the target application
Special processing required for PFC applications
Processing application based on migration objectives
Pre-configuring for the Web applications
Why is pre-configuration necessary
Four pre-configuration tasks
Modifying unsupported features
How to identify unsupported features
Feature modification methods
Enhancing the application with Web or Appeon features
Trial deployments and debugging
Special deployment steps for distributed applications
Debugging deployed applications
Fine-tuning the runtime performance
Go-live deployment
Go live
Migration FAQ
How do I rapidly build a new Web application with Appeon for PowerBuilder?
Does Appeon support every PowerBuilder feature?
Do Appeon-deployed Web applications support external resources?
Why classify my application into types?
What are the different application types?
What are the recommendations for converting the different application types?
What are the basic requirements for rewriting complex applications?
When would I need to modularize my application?
What are the benefits of modularizing my application?
What are the basic principles for modularizing an application?
Can you give an example of the modularization process?
Building and Migrating Distributed Applications (EAServer Windows only)
Moving unsupported features to Appeon Server as n-Tier NVOs
Advantages of n-Tier NVO usage
Restrictions in n-Tier NVOs usage
Steps for moving unsupported features or business logic to Appeon Server
Migrating distributed applications without distributed DataWindows
Generating Stub/Skeleton in EAServer
Deploying the application
Migrating distributed applications with distributed DataWindows
Benefits in using distributed DataWindows
Workaround required if you use distributed DataWindows
Enhancing an application with Web or Appeon features
Appeon Server open interfaces
Description of the open interfaces
Applying Appeon Server open interfaces in Appeon-deployed applications
Appeon client functions
Description of Appeon client functions
Using Appeon Client functions
Loading an application in SAP Sybase Enterprise Portal
Restrictions on supporting Enterprise Portal
Tasks required to load the application in Enterprise Portal
Single sign-on
Integrating Appeon Web applications with JSP/ASP
Processing PFC Applications
Auto-Sensing Environment
Suggested Modifications to PFC
Unsupported user objects
Unsupported standard class objects
Unsupported object properties
Unsupported object functions
Unsupported object events
Unsupported system functions
Unsupported Shared variables
Unsupported Function not found
Unsupported calls
Differently behaved features
Migration Tutorial
Preparing for the tutorial
Relevant files
Loading the Tutorial PowerBuilder Application
Creating a Workspace
Loading the tutorial PBL file
Configuring ODBC data source
Running the tutorial application
Configuring Appeon Developer
Configuring basic settings
Selecting PBL file(s)
Configuring deployment settings
Selecting DB Type(s)
Declaring transaction object(s)
Analyzing Unsupported Features
Unsupported features analysis
Optimizing and full build
Deploying the Tutorial PowerBuilder Application
Running the Web Application