1. Migrate your PowerBuilder applications to the web
Modernize your
PowerBuilder Applications
Take your PB Apps to the next level!
Migrate your PowerBuilder applications to the web
Give your PowerBuilder applications a new look
PowerBuilder + Active Directory: Advanced user management
Make your PowerBuilder Applications Multilingual 1

2. Migrate your apps to the web
In 2010, 58% of PB Projects had either web enabled their Apps or planned to do so (1) Here is Why:
Development
Production
PowerBuilder
Applications
+ Unbeatable productivity
+ Rich User Interface
- Deployment Cost
- Limited Access (LAN users)
Web redevelopment
(Java / .Net)
- Lower productivity
- Redevelopment cost
- Delays in deployment
- Risk of failure (long projects)
+ Simplified Deployment
+ Unlimited Access (Web users)
+ Comply with corporate production standards (Java or .Net)
Optimal combination = keep PB for development and deploy as Java or .Net
Appeon for PowerBuilder
+ Unbeatable productivity
+ Rich User Interface
+ Simplified Deployment
+ Unlimited Access (Web users)
+ Comply with corporate standards (Java or .Net) 2

3. How does it work? 3

4. Appeon Partitioning Approach
Appeon Utilizes a “Balanced” Architecture
Preserve PB’s desktop UI and rich client functionality
Deploy DW, SQL, and NVOs (i.e. business logic) to the app server
Re-use database, including functions and triggers
Web App
PowerBuilder
App
Client
Presentation Tier
Replicate
HTML,XML,
JavaScript
Web browser
Export
Business Logic
Convert
Deploy
Application Server
Appeon Server
DW, NVO
Retain
Database 4 4 4

5. System Requirements PowerBuilder Web Browser Web & Application Server
Includes the latest versions: 12.0, 11.x, 10.x, 9.0.3, 8.0.4
Web Browser
Internet Explorer 8/7/6; FireFox (in progress)
Web & Application Server
Server: Microsoft IIS 7.0/6.0, Sybase EAServer 6.1/5.5, IBM WebSphere /5.1, BEA/Oracle WebLogic 10.0/9.2, JBoss 5.1
O/S: Windows 2008/2003, Red Hat Linux 5.0/4.0, IBM AIX 5.3/5.2
Database
Sybase ASA 11.0/10.0/9.0/8.0, ASE 15.0/12.5, IQ 12.7, Microsoft SQL Server 2008/2005/2000, Oracle 11g/10g/9i/8i, Informix 9/7, IBM DB2 9.5/8.2 5
2017/4/6 5

6. Major Unsupported Features
PowerScript Statements
GOTO, THROW, THROWS
DataWindow
TableBlob Control for DataWindow
System Functions
Class Definition functions, DDE Server functions, Garbage Collection functions, Help functions, Library functions, Shared Object functions, Tracing functions
System Objects
ADOResultSet, ArrayBounds, ClassDefinition, ClassDefinitionObject, ConnectionInfo, ConnectObject, ContextInformation, ContextKeyword, CORBA (all), CPlusPlus, DivideByZeroError, DWRuntimeError, EnumerationDefinition, EnumerationItemDefinition, Error, ErrorLogging, Exception, ExtObject, JaguarORB, NullObjectError, OLERuntimeError, OLEStorage, OLEStream, OLETxnObject, OMControl, OMCustomControl, OMEmbeddedControl, OMObject, OMStorage, OMStream, ORB, PBTocppObject, Pipeline, ProfileCall, ProfileClass, ProfileLine, ProfileRoutine, Profiling, RemoteObject, ResultSet, ResultSets, RuntimeError, ScriptDefinition, Service, SimpleTypeDefinition, Throwable, Trace (all), TransactionServer, Transport, TypeDefinition, VariableCardinalityDefinition, VariableDefinition
* Nearly all major unsupported features can be commonly worked around utilizing server-side PowerBuilder NVOs
** Many unsupported features can be readily worked around at the client-side without utilizing server-side PowerBuilder NVOs 6
2017/4/6 6

7. Automatic Performance Boosting
Numerous functionalities built-in to boost Web performance under real-life situations
Download manager offers Just-in-Time (JIT) or Preload options for running the Web application
10X data compression to compress DataWindow result sets
3-level DataWindow caching technology caches at the application server, Web server, and Web browser
Micro-refresh (via AJAX) eliminates all redundant generation and downloading of data, such as in commonly and frequently-used “Master-Detail”
Application server connection pooling can boost database scalability by several folds through “shared” connections 7 7

8. Why Choose Appeon? Shortest development time and lowest cost.
Migrate existing PowerBuilder applications to web in a few months or weeks
No need to retool your engineering team
No need to re-train your end-users
Least project risk.
No need to rewrite your entire code base
No need to re-architect your system,
Powerful PowerBuilder Web deployment.
Effortlessly handles the largest of applications (up to 600MB)
with the most robust PowerBuilder feature support
offers powerful desktop integration with the richest Web user interface.
Performance and scalability.
Delivers virtually the performance of client/server with the scalability of the Web 8 8

9. How to get there? 9

10. Migration Process Analyze the application with Appeon tools
Unsupported PB functionalities?
Ineffective code?
1 – Analyze the PB code
2 – Adapt the PB code
Replacement of any unsupported functionalities
Optimisation of specific components
We keep the usual tools (PB, VE, PB Delta…)
3 – Web deployment
Appeon developer generates .NET or Java code
This code is deployed on the Appeon Server
The application is accessible on the Internet immediately
4 – Future development?
The migration is done once and for all
Maintenance and future development will only use functionalities supported on the web
Any future versions will be deployable “as-is” 10 10

11. Automatically migrate to Java/.NET
Appeon Developer
Appeon provides a suite of tools to assist developers in their development/deployment
Appeon Developer
Automatically migrate to Java/.NET 11

12. Unsupported Features Analyzer
Identifies unsupported features based on keyword, providing you with location, line number, and code snippets 12
2017/4/6 12

13. Appeon Code Insight
Keep future development Web-compliant by listing only supported PowerScript at your fingertips 13
2017/4/6 13

14. Appeon (Web-to-PB) Debugger
Use Appeon Debugger to real-time debug the resulting Web application tracing back to specific line of PowerScript 14
2017/4/6 14

15. Timeframe and budget
Average budget for an application serving 200 to 400 concurrent users (i.e. simultaneously connected to the application)
Software : ~ 10 K$
Hardware : 1 Dual CPU Server
Migration : varies from a few weeks to a few months of work.
The migration can be :
Done internally: Appeon tools list all unsupported features, you replace them with PB
Outsourced: A ready-to-deploy version of your application is delivered
Examples :
Mid-sized applications : 30 to 80 MB PBL, with a few hundred Windows.
Cost of a turnkey migration : 30 to 80 K$
Timeframe : 2 to 5 months 15

16. What about your applications?
Go further:
To try Appeon by yourself : get a trial
To find out the cost of a turnkey migration : get a quote
For any questions about Appeon :
In English :
En Français :
En Español : 16

17. Give your Application a new look

18. Makeovers: Pros and Cons
Why makeover PowerBuilder Applications?
Over the years, presentation standards have evolved.
Some applications need a redesign to give their GUI a new, modern look.
But obstacles to this exist:
Reworking screens and reports consumes lots of development resources
The application code is stable we don’t want to risk adding bugs to it
In certain cases, there is no PB developer available for this
Developers are not designers. They have mastered the technique, but do not necessarily know how to create new interfaces with attractive modern looks…
Customization Studio proposes a new approach
to avoid these problems…

19. What is Customization Studio?

20. Customization Studio is:
A solution to modify screens and reports of a PB application.
Providing simple tools, designed for non-developers (users, designers...).
Making modifications on an executable copy of the application.
Development
Design or
Relooking
End-users
Source code
ExecutableCopy
New User Interface

21. Makeovers for PowerBuilder Applications
Why use Customization Studio?
No need to pull resources from the development team. Anyone can update the GUI with a new look (user, designer…)
The code of the application remains stable and unchanged. At any time, you can deactivate some or all of the changes
Customization Studio provides Style Sheets to speed up the process: Define a style once and apply it to several components

22. Timeframe and budget
Average budget for Mid-sized applications (30 to 80 MB PBL, with a few hundred windows)
Software: ~ 10 K$
Hardware: same requirements as the PB application
Makeover time: from a few weeks to a few months
As for the web migration, the makeover can be done internally or outsourced

23. What about your applications?
Go further:
To try Customization Studio for yourself : get a trial
To find out the cost of a turn-key makeover : get a quote
For any questions about Customization Studio:
In English :
En Français :
En Español :

24. PowerBuilder + Active Directory Advanced user management24

25. Reuse Windows Accounts
In the majority of companies, a user often has multiple accounts to access multiple systems and applications.
Each application often relies on its own access control solution.
As a result, each application is managed as a « Silo ».
Managing silos comes with the following shortcomings:
You have to maintain several access control systems
You manage multiple accounts per user
Fragmented policy management is too complex
No centralized View and Control of access rights
2.1 Authentication
This confirms the user’s identity: It consists of checking the identity of the user of your application. Actually, this is a two step process: First, identification, which consists of stating who you are; and then authentication, which consists of proving who you are. This is usually done via user accounts and passwords. This is the first level of security.
2.2 Authorization
Authorizations define what a user can do in an application: Basically, you define what the user is allowed to see, do and modify in the application.
You need to choose between two ways of defining authorizations:
• The most secure way is to forbid everything by default, and then grant permissions to open possibilities. This way, if you forget to define a permission, the user won’t be able to do something he should, rather than accidentally do something he shouldn’t.
• The faster way is to allow everything by default, and then you assign restrictions to forbid some actions. This way is faster because typically there are fewer restrictions than permissions.
This is the second level of security and represents the heaviest parts of RBAC design, since you need to code every permission/restriction.
2.3 Audit
Keep track of sensitive transactions in the application: You may need auditing features to comply with business rules specific to your company, with legal requirements like SOX or certification processes like ISO.
Audit should enable you to review who did What in your application, When, and Who granted which permission to Which user.

26. Reuse Windows Accounts
To eliminate these inconviences, companies use Windows accounts to manage access rights for their users.
Visual Guard automatically integrates your PB applications with Active Directory:
A Single list of users:
All user accounts are listed in the same Repository (Active Directory)
Users only need 1 account to access all applications
A Single Administration Console:
Administrators use the same tools to grant access to all systems
You can delegate limited administration rights to local administrators
Centralized view and control of:
User access rights
User operations made in all applications
Administration operations for all applications
2.1 Authentication
This confirms the user’s identity: It consists of checking the identity of the user of your application. Actually, this is a two step process: First, identification, which consists of stating who you are; and then authentication, which consists of proving who you are. This is usually done via user accounts and passwords. This is the first level of security.
2.2 Authorization
Authorizations define what a user can do in an application: Basically, you define what the user is allowed to see, do and modify in the application.
You need to choose between two ways of defining authorizations:
• The most secure way is to forbid everything by default, and then grant permissions to open possibilities. This way, if you forget to define a permission, the user won’t be able to do something he should, rather than accidentally do something he shouldn’t.
• The faster way is to allow everything by default, and then you assign restrictions to forbid some actions. This way is faster because typically there are fewer restrictions than permissions.
This is the second level of security and represents the heaviest parts of RBAC design, since you need to code every permission/restriction.
2.3 Audit
Keep track of sensitive transactions in the application: You may need auditing features to comply with business rules specific to your company, with legal requirements like SOX or certification processes like ISO.
Audit should enable you to review who did What in your application, When, and Who granted which permission to Which user.

27. Visual Guard Implementation Process:
Add the Visual Guard libraries to the Application’s PBL List
Declare and instantiate the Security manager
Connect to the Security Repository
Load the user Security profile
Secure the application objects (apply permissions)

28. Single Sign-On 28

29. Single Sign-On Why implement Single Sign-On (SSO)?
Users are automatically identified by the PB Applications with their Windows account
They log in once (Windows startup) and gain access to all applications without being prompted to log in again for each of them
Benefits include:
Reducing time spent re-entering passwords for the same identity
Reducing IT costs and Helpdesk calls about passwords

30. Timeframe and budget
Average budget for an application serving 100 to 400 users
Software: ~ 6 to 10 K$
Hardware: same requirements as the PB application
Work: a few hours for implementation. 30

31. What about your applications?
Go further:
To try Visual Guard for yourself : get a trial
To find out the cost of a turn-key integration: get a quote
For any questions about Visual Guard :
In English :
En Français :
En Español :

32. Make your applications multilingual

33. Why make your application multilingual?
Extend life-cycle of existing applications
Expand commercial markets for existing applications quickly and easily
Work in preferred language: multilingual employees, international branches, personnel visiting from abroad
Streamline maintenance (single source code) and distribution (single executable code)

34. What is Enable?
A solution for transforming PowerBuilder software into multilingual applications
Enable is a Framework-level tool: maximum control, flexible, easy to apply
Single source code, single application
PowerBuilder oriented in every aspect
Translated application does not require any royalty fees.

35. Timeframe and budget Average budget for a PowerBuilder team :
Software: ~ 10 K$
Hardware: same requirements as the PB application
Work : a few hours to a few days for the implementation. Texts extraction and translation depend on the size of the application.
The implementation can be done internally or outsourced 35

36. What about your applications?
Go further:
To try Enable for yourself : get a trial
To find out the cost of a turn-key implementation: get a quote
For any questions about Enable :
In English :
En Français :
En Español :