Considering Legacy Migration? We Make it Possible!

PowerBuilder to Java Client Server

Home | Legacy Conversion PowerBuilder to Java Client Server

 

PowerBuilder to Java Client Server Conversion

 

Legacy applications migration tools and methodology used for the conversions of PowerBuilder into Java Client Server

 

Pros
PowerBuilder to Java Client Server Conversion

 

Similar architecture

Exact replication

Reduced risk

Error handling & security

Similar look and feel

Testing

Some degree of automation possible

Lower degree of end user involvement

 

Cons
PowerBuilder to Java Client Server Conversion

 

Error handling & security

Testing

Client server

Not fully automated

 

Suited when

 

Web based application is not a requirement

Well documented

 

UI Controls & Data types
PowerBuilder to Java Client Server Conversion

 

PowerBuilder

boolean

boolean

date

datetime

datetime

dec

dec

long

real

 

string

 

CheckBox / DataWindow checkbox

CommandButton / DataWindow command button

DropDownListBox / DataWindow drop down or drop down listbox

Edit mask / DataWindows editmask

DataWindow Form

DataWindow Grid

ListBox

Java

boolean

char

java.util.Date

java.util.Date

java.util.Date

java.math.BigDecimal

short

int

float/double depending on precision

java.lang.String or

java.lang.StringBuffer

javax.swing.JCheckBox

 

javax.swing.Jbutton

 

 

javax.swing.JComboBox

 

 

Third party tools such as JSuite

Various swing components

javax.swing.JTable

javax.swing.JList

 

 

Issues (Design & Development)
PowerBuilder to Java Client Server Conversion

  • UI control mapping and look and feel differences
  • Converting DataWindows
  • Mapping of PB UI events to Java Swing
  • DataWindow Report
  • Client Server deployment

 

Solution (Design & Development)
PowerBuilder to Java Client Server Conversion

  • Since the Swing library is platform independent to achieve the same look and feel the Layout Manager needs to be set to Windows look and feel. There is no native Java for Edit Mask but there are third party components available.
  • There are many forms of DataWindows – drop downs, form, tabular, free form and DataStores. These are converted to Java with the use of helper classes that implement the base DataWindow functionality and child classes implement the full functionality.
  • Some UI events in PB do not have equivalent in Java Swing. Combination of events and additional coding will be needed e.g. DataWindow ItemChanged Event -> FocusListener.focusLost
  • Java is weak in reporting capabilities but commercial as well as open source tools can provide the same level of functionality as PowerBuilder. Some tools to consider are Business Objects, Cognos, and BIRT (open source).
  • Client Server deployment of Java applications is challenging because of the various JVM vendors and JDK versions. Java web start technology helps greatly in ensuring that the clients are running the correct version of the application and its pre-requisite JDK.

 

Client Server Architecture Diagram
PowerBuilder to Java Client Server Conversion

 

Java Client Server Architecture Diagram

 

 

 

back to PB to Java Client Server Conversion

 

Conversions
 

Updates

Enter your email to get notified.

send your email
Conversions