PowerServer

Automatically Deploy C/S Apps to the Cloud

The PowerServer project type re-compiles existing client/server projects for Internet access with a cloud-native, .NET architecture. It typically requires minimal code changes and supports almost all existing PowerBuilder features.

Schedule a Demo

CAPTCHA

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

Key Benefit of PowerServer

Internet Accessible

End users can access PowerServer apps from Windows devices over the Internet. 

Host Anywhere

Host PowerServer apps with cloud providers, private data centers, or even on-premise.

Centralized Deployment

Updates are automatically pushed to users from the server without manual intervention.

No User Retraining

PowerServer apps look and work the same as before, eliminating the need for user training.

Great Scalability

Supports containerized deployment, enabling automatic scaling and cost savings compared to traditional deployments. 

Enhanced Security

All SQLs executed on the .NET server behind the firewall. Data consumption is secure via REST APIs using HTTPS and token authentication.

Low-Cost

Converts most PowerBuilder features automatically, usually reducing project migration time to just weeks.

Low-Risk

Developers continue using the PowerBuilder IDE and existing skills, virtually eliminating all project risk.

PowerServer Deployment & Architecture

Deployment Process

PowerServer streamlines the deployment of client/server applications by automating the conversion into a cloud-native architecture. The process involves the following key steps:

Step 1: Configure Project
Create a new PowerServer project from within the PowerBuilder IDE to define how the installable cloud app will be generated. This configuration is typically a one-time step per project.
Step 2: Generate Installable Cloud App
The PowerServer compiler uses the project's configuration to automatically generate the installable cloud app, which comprises of two main components:
Client App: This component on the client-side renders and executes UI elements, system objects, and PowerScript.
REST APIs: This component on the server-side executes data access logic, including DataWindows, DataStores, and embedded SQL.
Step 3: Deploy to Host
• The Client App is deployed to a web server, enabling users to install the app over the Internet.
• The REST APIs are deployed to IIS or Kestrel, executing the data access in 100% managed .NET code environment.
• You can host the application with cloud providers, private data centers, or even on-premise.

Cloud-Native Runtime Architecture

End users download the Client App over a secure HTTPS connection and run it on their Windows devices. The application performs all data operations through industry-standard REST APIs in 100% managed .NET code environment. The client app no longer establishes local database connections or executes any SQL on the client device. By separating the UI and data layers, PowerServer achieves a cloud-native architecture that enhances availability, security, and scalability. 

Get Started Today

Don't let on-premise infrastructure hold back your business. With PowerServer, you can deploy, secure, and scale your PowerBuilder applications effortlessly.

Get a Free Trial Request a consultation