Appeon Migration Guide

Web RAD with PowerBuilder and Appeon

Overview

Traditional approach to Web development

Advantages of Appeon for Web RAD

Appeon Web RAD methodology

Migration Process

Introduction

Installing required software

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

Production deployment

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 application?

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

Strategy

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 (Windows only)

Benefits in using distributed DataWindows

Workaround required if you use distributed DataWindows

Enhancing an application with Web or Appeon features

Appeon Server open interfaces (J2EE server only)

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

Migration Tutorial

Introduction

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