Convert PowerBuilder to Java

Delivering you an intelligent and high quality result in due time!

With 25+ years of experience in software modernization, Ispirer is well qualified to perform comprehensive application migrations between diverse programming languages and platforms. Apart from the extensive expertise, we rely on our proprietary Ispirer Toolkit to streamline and speed up PowerBuilder to Java conversion.

Migrate PowerBuilder to Java

Bulb

Turnkey migration service for
PowerBuilder to Java

Turnkey PowerBuilder to Java migration service by Ispirer professionals includes:

  • Migration of the entire application, including project files, business logic, GUI and database API
  • Team of experts skilled in PowerBuilder and Java
  • Tailored migration roadmap from assessment through migration and testing to cutover
  • Smart automation with Ispirer Toolkit
  • Assistance in deployment and integration, performance optimization, new feature development

Contact us and we’ll discuss and estimate your PowerBuilder to Java project


Request a quote

Save expense

Ispirer Toolkit customization service

The service is aimed at customizing Ispirer Toolkit and providing you with optimal solution for automated application conversion. The service includes:

  • In-depth analysis of your application
  • Adding new conversion rules to Ispirer Toolkit (customization)
  • Assistance in Ispirer Toolkit configuration
  • Automated conversion of the codebase, including business logic, GUI, database API, etc using Ispirer Toolkit by your team
  • Timely technical support

Drop us a line and we’ll show you how a tailored version of Ispirer Toolkit can help you modernize your PowerBuilder application


Live demo

Why choose conversion over developing a new app?

Seasoned Team

Same functionality, new application

Migration does not require labor-intensive development of new functionality from scratch. Your application will be converted to a new technology while maintaining the original functionality

Enhanced efficiency

Architecture preserved or modified

By default, automated conversion implies preserving the initial architecture which is easier to maintain. It is also possible to transform the app architecture, for example, from desktop to the web and thus improve accessibility and scalability

Integrate

Legacy System Transformation

Migrating legacy systems to modern architectures or platforms can future-proof your application, making it easier to maintain, update, and extend in the long term

Advanced security

The speed of conversion

Migrating an application is much faster than creating a new one from scratch. Automated migration with Ispirer Toolkit minimizes manual effort and may speed up the delivery by 2-3 times

Growth

Performance and Scalability

Through conversion, you can optimize the application's architecture and infrastructure, improving scalability and performance without the need to rebuild everything

Advanced security

No need for documentation

To perform the conversion, we go by your source code. There is no need to have detailed documentation in place to start the conversion as is the case with development

PowerBuilder to Java Conversion Demo

Check out how Ispirer Toolkit automatically converts PowerBuilder application.


Drop us a line, if you have any business inquiries or questions regarding your PowerBuilder conversion project. Ispirer experts will demonstrate our solutions and answer any questions you may have!

Contact us


Turnkey Migration Service

The entire conversion process can be divided into several stages:

  • Preparation. During the preparation stage, the focus lies on planning and preparing applications and infrastructure for migration to a new environment or platform. This involves assessing their current state to gauge compatibility with the target environment and defining the migration strategy, timeline, and required resources. Additionally, identifying potential risks and challenges associated with the migration process and devising mitigation strategies are integral parts of this stage.
  • Assessment. During the assessment phase, the team conducts a thorough analysis of the source code to accurately estimate the migration timeframe and cost. As a first step, we apply Metrics - a set of Ispirer’s proprietary assessment tools tailored to different programming languages. These metrics automatically analyze the source application, gathering essential information and generating a comprehensive report. This report combined with the insights gathered during the expert review of the source code serves as the basis for estimating the delivery time and cost of the migration project.

APP Services general

  • Automated conversion with Ispirer Toolkit. Considering the inherent characteristics of the original technology, Ispirer Toolkit can provide varying default levels of automated code conversion. Importantly, Ispirer experts can iteratively customize the tools to meet the specific properties and patterns of the source code and thus increase the level of automated conversion.
  • Post-conversion refinement. Often an application may contain code segments that are impossible or ineffective to migrate automatically. In such a case, our team of Ispirer experts leverages their extensive knowledge and expertise to meticulously execute the manual migration of the remaining code. Moreover, this stage involves fine-tuning the application to improve its performance in the new environment. This may include optimizing resource allocation, tuning database configurations, and addressing any performance bottlenecks.
  • Functional testing. Functional testing ensures that the migrated application behaves as expected and meets the functional requirements in the new environment. The Ispirer experts run hundreds of tests to ensure that the converted application is reliable and meets user requirements, business objectives, and industry standards.

Looking for PowerBuilder to Java Conversion Services?

Drop us a line and we’ll estimate your project for free!

Request a quote


Ispirer Toolkit Customization Services

Ispirer customization service allows you to get a personal version of the Ispirer Toolkit specifically for your application. With our proprietary tools tailored to your project requirements, you will be able to automate the conversion of your PowerBuilder code to Java with maximum efficiency. A service like this will allow you to ensure a seamless app modernization and reduce manual adjustments to the bare minimum. The engagement model will be as follows:

Related Services

  • Live demo. Our migration experts will demonstrate an example of automated app modernization using Ispirer Toolkit.
  • Proof-of-Concept. A representative scope of PowerBuilder code is migrated using Ispirer Toolkit. You will have an opportunity to evaluate the results of future PowerBuilder to Java modernization after Ispirer Toolkit customization.
  • Ispirer Toolkit customization service. This stage includes adding new conversion rules for PowerBuilder to Java direction to ensure the smooth translation process and high quality result of automated conversion.
  • Conversion with Ispirer Toolkit. Once the tool is customized, you take the matter in your hands and convert a PowerBuilder application using Ispirer Toolkit quickly and efficiently.

High quality

High quality SQL code conversion

Expert system with 20.000+ conversion rules and 100.000+ automation tests.

Flexibility

Flexible modernization

Nimble configuration with 300+ options for effective application conversion.

Free smart assessment

Free smart assessment

Free Assessment Metrics for migration scope and complexity evaluation.

Intuitive and instructive reports

Comprehensive migration analysis

Intuitive and instructive reports for cost-effective post-migration polishing.

Would you like to organize a live demo with the Ispirer team?

Our migration experts will demonstrate an example of automated database migration using Ispirer Toolkit. You will have an opportunity to evaluate the benefits of automated PowerBuilder to Java migration after Ispirer Toolkit customization.

Live demo

Conversion Samples of PowerBuilder to React and Java

PowerBuilder programs consist of Workspaces (starting from PB 8.0 and higher, these are .pbw files). Conceptually, they are similar to Solution. These are text files consisting of paths to the Target files (.pbt files) that correspond to the concept of Project. The Target files are in text format, and each contains paths to the PowerBuilder libraries (.pbl files that store source code files in binary format). Typically a library with the same name as the Target file has a .sra entry point file.

To convert a PowerBuilder application, you need to extract all source files from the appropriate Workspace libraries (or Target, if PB version is less than 8). You can download Ispirer PowerBuilder Metrics to get a statistical report on PB sources, as well as extract source files from PowerBuilder libraries using Workspace, or a set of Target files, or a set of particular PB libraries (.pbl files) that need to be converted.

Once the source code is extracted, for each PowerBuilder library file, a corresponding folder named library will be created with all the source code extracted. The folders will contain source files with the following file extensions:

  • .SRD - DataWindow source files
  • .SRW - Window source files
  • .SRM - Menu source files
  • .SRU - Custom user object source files
  • .SRS - Structure source files
  • .SRP - Data pipeline source files
  • .SRF - Function source files
  • .SRQ - Query source files
  • .SRA - Application source files

Now you can use Ispirer nGLFly Wizard to convert it to your chosen target technology.
Basic source type conversion by extension:

  • .SRD - converted to 2 files. One file is named DatawindowObjectName.ts (located on the client) - the UI and code for the DataWindow object. The other file is called DatawindowObjectController.java (located on the server) that contains the sql query.
  • .SRW - converted to 2 or 3 files. The files are named WindowObjectNamePage.tsx and store.ts (located on the client) - the UI and code of the Window object. If the source file contains sql queries, the WindowObjectNameController.java file is converted to the server with sql queries.
  • .SRM - converted to 1 file named Menu ObjectName.tsx. – the UI and menu object code.
  • .SRU - converted to 1 file named store.ts for the non-visual object and 2 files named store.ts and UserObjectName.tsx - the UI and code of the User object.
  • .SRS - converted to 1 file named StructureObjectName.ts. The file contains a class with variable declarations from the PowerBuilder structure.
  • .SRP - not used for conversion.
  • .SRF - converted to 1 file named functionObjectName.ts. The file has a public function.
  • .SRQ - not used for conversion.
  • .SRA - converted to 1 file named applicationObjectName.ts. The contents of this file are used to copy into the project's entry point file in the same way as in the conversion sample.

After the conversion, you need to create a WPF application desktop project in Visual Studio and add the converted files from the results folder to it. There is the Ispirer framework for converting PowerBuilder to React and Java (IspirerFramework) in the results folder.
Note: this is a special framework provided by Ispirer. It extends the target technology to enable specific source code features.

Variables declarations conversion:

PowerBuilderReact + Java
  1.  
  2. long var1
  3. long var2[]
  4. string var3
  5. datetime var4
  6. boolean var5
  7. decimal var6
  8. integer var7
  9. any var8
  10.  
  1.  
  2. let var1: number = 0;
  3. let var2: Array<number> = [];
  4. let var3: string = '';
  5. let var4: Date;
  6. let var5: boolean = false;
  7. let var6: number = 0;
  8. let var7: number = 0;
  9. let var8: any = null;
  10.  

Function conversion:

PowerBuilderReact + Java
  1.  
  2. public function string sample_function();
  3. return "end"
  4. //do logic
  5. end function
  6.  
  1.  
  2. function sampleFunction(): string {
  3. return 'end';
  4. //do logic
  5. }
  6.  

Subroutine conversion:

PowerBuilderReact + Java
  1.  
  2. protected subroutine sample_sub (string v_app);
  3. v_app = ""
  4. //do logic
  5. end subroutine
  6.  
  1.  
  2. function sampleSub(vApp: string) {
  3. vApp = '';
  4. //do logic
  5. }
  6.  

If statement conversion:

PowerBuilderReact + Java
  1.  
  2. integer i
  3.  
  4. if true then i = 1 else i = 2
  5.  
  6. if true then
  7. i = 3
  8. end if
  9.  
  1.  
  2. let i: number = 0;
  3.  
  4. if (true) {
  5. i = 1;
  6. } else {
  7. i = 2;
  8. }
  9.  
  10. if (true) {
  11. i = 3;
  12. }
  13.  

For statement conversion:

PowerBuilderReact + Java
  1.  
  2. For lv_count = 1 to 10
  3. lb_units[lv_count].Visible = TRUE
  4. Next
  5.  
  1.  
  2. for (lvCount = 1; lvCount < 10; lvCount++) {
  3. lvCount[lvCount].visible = true;
  4. }
  5.  

While statement conversion:

PowerBuilderReact + Java
  1.  
  2. IDX = 0
  3. do while true
  4. if IDX = 10 then exit
  5. IDX = IDX + 1
  6. loop
  7.  
  1.  
  2. idx = 0;
  3. while (true) {
  4. if (idx === 10) {
  5. break;
  6. }
  7. idx = idx + 1;
  8. }
  9.  

Try catch statement conversion:

PowerBuilderReact + Java
  1.  
  2. try
  3. IDX = 1 / 0
  4. catch (Exception ex )
  5. IDX = 100
  6. FINALLY
  7. IDX = IDX * 2
  8. end try
  9.  
  1.  
  2. try {
  3. idx = 1 / 0;
  4. } catch (ex) {
  5. idx = 100;
  6. } finally {
  7. idx = idx * 2;
  8. }
  9.  

Try choose statement conversion:

PowerBuilderReact + Java
  1.  
  2. integer some_id
  3. boolean cond
  4.  
  5. CHOOSE CASE some_id
  6. Case IS < 0
  7. cond = False
  8. CASE 0 TO 2
  9. cond = True
  10. some_id = 200
  11. Case IS > 0
  12. cond = True
  13. CASE ELSE
  14. cond = False
  15. some_id = 0
  16. END CHOOSE
  17.  
  1.  
  2. let someId: number = 0;
  3. let cond: boolean = false;
  4.  
  5. switch (true) {
  6. case someId < 0:
  7. cond = false;
  8. break;
  9. case someId >= 0 && someId <= 2:
  10. cond = true;
  11. someId = 200;
  12. break;
  13. case someId > 0:
  14. cond = true;
  15. break;
  16. default:
  17. cond = false;
  18. someId = 0;
  19. break;
  20. }
  21.  

Inline query conversion:

PowerBuilderReact + Java
  1.  
  2. global type s_2 from structure
  3. long field_1
  4. end type
  5. s_2 param1[]
  6.  
  7. INSERT INTO TAB1
  8. (
  9. COL1 , COL2
  10. )
  11. VALUES
  12. (
  13. :param1[1].field_1,
  14. :param1[2].field_1
  15. );
  16.  
  1.  
  2. Client (typescript):
  3. export type s2 = {
  4. field1: number;
  5. };
  6.  
  7. export class S2 {
  8. static create(): s2 {
  9. return {
  10. field1: 0,
  11. };
  12. }
  13. }
  14.  
  15. let param1: Array<s2> = [];
  16.  
  17. await request({
  18. path: 'fileName/query1',
  19. body: {
  20. params: [param1[0].field1, param1[1].field1],
  21. },
  22. method: 'POST',
  23. });
  24.  
  25. server (Java):
  26. private String QUERY1 = "INSERT INTO TAB1 "+
  27. "( "+
  28. "COL1 , COL2 "+
  29. ") "+
  30. "VALUES "+
  31. "( ?, ?) ";
  32.  
  33. @PostMapping(value = "/query1")
  34. public @ResponseBody
  35. int query1(@RequestBody Map<String, Object> body) throws Exception {
  36.  
  37. return sqlService. jdbcUpdate (QUERY1, (List<Object>)body.get("params"));
  38. }
  39.  

CURSOR conversion:

PowerBuilderReact + Java
  1.  
  2. String v_uname[]
  3. Long v_unum[]
  4. Int v_count = 1
  5.  
  6. DECLARE c_unit CURSOR FOR
  7. SELECT U_NAME, U_NUM
  8. FROM UNT
  9. WHERE A_NUM = 10;
  10.  
  11. OPEN c_unit;
  12. FETCH c_unit INTO :v_uname[v_count],:v_unum[v_count];
  13. v_count ++
  14. Do While SQLCA.SQLCode = 0
  15. FETCH c_unit INTO :v_uname[v_count],:v_unum[v_count];
  16. v_count ++
  17. Loop
  18. CLOSE c_unit;
  19.  
  1.  
  2. Client(typescript) :
  3. let vUname: Array<string> = [];
  4. let vUnum: Array<number> = [];
  5. let vCount: number = 1;
  6.  
  7. let rows = await request({
  8. path: 'fileName/query1',
  9. body: {
  10. params: [],
  11. },
  12. method: 'POST',
  13. });
  14.  
  15. for (let i = 0; i < rows.length; i++) {
  16. vUname[v_count] = rows[i].U_NAME;
  17. vUnum[v_count] = rows[i].U_NUM;
  18. vCount++;
  19. }
  20.  
  21. server(Java):
  22. private String QUERY1 = "SELECT U_NAME, U_NUM FROM UNT WHERE A_NUM = 10 ";
  23.  
  24. @PostMapping(value = "/query1")
  25. public @ResponseBody
  26. Object query1(@RequestBody Map<String, Object> body) throws Exception {
  27.  
  28. Object values = sqlService.jdbcSelect(QUERY1, (List<Object>)body.get("params"));
  29. return ResponseEntity.ok(values);
  30. }
  31.  

How to start the client:

1) Install nodejs;
2) Open the ReactClientName folder in vs code;
3) Open terminal (Ctrl +`);
4) Run the command: npm i;
5) Run the command: npm run start;
6) Open the URL in your browser: http://localhost:3000/.

How to start the server:

1) Open the JavaServerName folder in vs code;
2) Switch to the Run and Debug tab (Ctrl + Shift + D);
3) Click the Server Application button.

Download Sample Code

You have just examined only a piece of the PowerBuilder to Java conversion sample. You can download the entire application migration sample for free by filling out the form. Once you get the code sample, you will be able to:

  • Explore how well Ispirer Toolkit migrates the source code to the target technology without downloading it.
  • Analyze and compare the source sample with your code to understand which components of your application can be automatically converted using Ispirer Toolkit.
  • Run, play with and test an application containing nearly 2,500 lines of code.

See for yourself that Ispirer Toolkit can automatically convert not only a single piece of code, but an entire application. Most likely, complex code will require customization of the toolkit, but our experts can add new conversion rules within 3-5 business days. As a result, using Ispirer Toolkit you will get readable and maintainable code of manual conversion quality in the shortest time possible.

Snatch a totally free opportunity to see the high efficiency of Ispirer Toolkit!

Get your sample code
Enter your name.

Enter a valid e-mail address.

Select your country.

Invalid input.

Accelerating our customers’ application modernization journey

The customer received a modernized application in C#, which is a feature-for-feature equivalent to the original Delphi application. Thus getting the ability to easily maintain and enhance the newly migrated code.

December 04, 2018

The company develops state-of-the-art automation systems for operation, disposition, monitoring and control for all industries. The customer needed to reanimate their software by moving from Delphi to C#.

Our customer ia a healthcare organization dedicated to improve funding and clinical performance of hospitals and healthcare systems. The company's requirement was to get the application on the new C# .NET platform.

previous arrow
next arrow
Slider

Why Migrate with Ispirer

With a proven track record validated by both time and satisfied clients, Ispirer software and services stand as the pinnacle choice for database migration and application modernization. Leveraging years of experience and client feedback, Ispirer guarantees smooth transitions and optimized operational efficiency for businesses of all scales.

  • Seasoned team. Ensuring high security and performance standards is what we do best, thanks to our impressive experience in building reliable and scalable solutions.
  • Technology expertise. Having 20+ years of experience our team has gained a wide pool of expertise in various programming languages from the rarest to the most popular ones.
  • Top-notch data security. We comply with ISO 27001 security management requirements with comprehensive policies and processes, advanced security technology, and skilled professionals.
  • Proprietary tools. In migration projects we employ Ispirer proprietary tools which underscores our dedication to delivering solutions of utmost reliability and performance. Compiled on a daily basis, this toolkit continually integrates dozens of new conversion rules, thereby consistently enhancing the automation capabilities. Find out more about our solution in the infographic:
Infographics showing how automatic application conversion brings benefits

What Our Customers Say

Get in touch with us!

Have questions about migration from PowerBuilder to Java?

Contact us