Deploy Your PowerBuilder App to the Cloud — Without Rewriting It
PowerServer by Appeon recompiles your existing PowerBuilder application as an installable cloud app — users visit a URL, the Cloud App Launcher installs it silently on Windows, and it runs natively with automatic updates on every launch. No web browser. No mobile. No rewrite.
Why PB-to-Cloud Migration Is Non-Trivial
Even with PowerServer eliminating the need for a rewrite, real migration projects encounter challenges that require expert remediation.
A small subset of PowerBuilder features is unsupported — typically code that directly interfaces with local Windows APIs, OLE/ActiveX controls, or low-level DLL calls. These must be identified and remediated before deployment.
Applications using direct ODBC calls, stored procedure outputs, or non-standard transaction objects may require code adjustments to align with PowerServer's client-server data architecture.
Applications calling external DLLs, COM components, or third-party controls must have each dependency catalogued, tested, and either replaced or worked around within PowerServer's architecture.
Legacy PB apps often rely on Windows-native or DB-native authentication. PowerServer supports token-based authentication (OAuth, Azure AD), requiring the login flow to be updated accordingly.
When data access moves to REST API calls over a network, DataWindow-heavy apps may experience latency. Performance profiling and DataWindow query optimisation are essential before go-live.
PowerServer 2022 and 2025 require PowerBuilder 2021 (CloudPro) or newer. Applications on PB 10.x–2019 must be upgraded first. Appeon confirms that upgrades from PB 10.x or newer typically require no code changes — Optisol verifies and handles this as part of the engagement.
Structured Migration in 5 Phases
A risk-controlled approach that addresses every technical prerequisite, compatibility issue, and infrastructure requirement — before production cutover.
Audit & Readiness Assessment
Run PowerServer's unsupported feature detection across the full codebase. Catalogue DLL dependencies, OLE/ActiveX usage, transaction objects, and auth patterns. Produce a remediation priority list.
PB Upgrade & Code Remediation
Upgrade to PB 2022/2025 CloudPro if needed. Resolve unsupported features, replace incompatible DLL calls, adjust transaction objects, and configure token-based authentication.
PowerServer Setup & Infra
Install and configure PowerServer on the target environment. Provision cloud infrastructure, set up CI/CD via PBAutoBuild, and deploy the entire application as a single PowerServer project.
Testing, UAT & Performance
Test the cloud app against the original C/S app across all functional areas. Profile DataWindow performance under load and resolve any REST API latency issues before sign-off.
Cutover, Rollout & Hypercare
Users install via deployment URL — Cloud App Launcher handles silent install on Windows. Optisol monitors server logs and update propagation for 30 days before handover.
What PowerServer Delivers
A deployment and runtime framework — not a code converter. Your source stays in the PowerBuilder IDE; PowerServer handles the cloud-native architecture automatically.
Windows-Native Client Runtime
The app runs against the PowerBuilder Virtual Machine (PBVM) — same as classic client/server. Ensures near-100% feature compatibility including DataWindow features, MDI windows, and PFC.
Automatic App Distribution & Updates
Users install once via the deployment URL. The Cloud App Launcher handles download silently. On every subsequent launch, the app auto-updates — no IT distribution tools needed.
REST API Security Layer
All database operations execute via PowerServer's .NET Core Web APIs — not the client. DB credentials are never exposed to end-user machines. HTTPS with OAuth support throughout.
Flexible Hosting — Any Environment
Host on IIS (Windows), Kestrel (.NET Core, cross-OS), Docker, or Kubernetes on AWS, Azure, or GCP. No cloud-provider restrictions — host wherever your organisation's policy dictates.
CI/CD via PBAutoBuild
PBAutoBuild compiles and deploys PowerServer projects without the PB IDE running. Integrates with Jenkins and Git/SVN for fully automated build and deployment pipelines.
Broad Database Support
Supports MS SQL Server, Oracle, SAP SQL Anywhere, SAP ASE, PostgreSQL, MySQL, HANA, and SQLite — plus cloud-managed equivalents like Azure SQL and Amazon RDS.
📊 Enterprise Load Testing — Unlocked
Because PowerServer exposes all data access as standard HTTPS REST endpoints, your app becomes fully testable with Apache JMeter and LoadRunner — simulating thousands of concurrent users and benchmarking DataWindow response times. Impossible in traditional PB client/server, where data calls go directly client-to-DB via proprietary binary drivers with no HTTP layer.
⚠️ C/S limitation: ODBC/OLE DB connections bypass any HTTP layer — JMeter and LoadRunner have nothing to intercept, making load testing and SLA benchmarking practically impossible.
🚫 Citrix makes it worse: ICA/HDX wraps sessions as screen pixels, not API calls. No tool can isolate or replay individual transactions — you cannot plan for scale with data you cannot measure.
Simulate thousands of concurrent users against PowerServer REST endpoints with per-DataWindow response time reports.
✓ CompatibleRecord and replay PowerServer API interactions at scale with SLA thresholds and real-time server monitoring.
✓ CompatibleAPI response times, peak throughput, DataWindow latency under load, and slow query identification.
✓ Per-endpoint visibilityEmbed tests in PBAutoBuild pipeline to catch performance regressions automatically on every deployment.
✓ Automated testingWhere Can PowerServer Be Hosted?
PowerServer is fundamentally a .NET Core application — it can be hosted anywhere .NET runs. Optisol has deployed it across these environments.
Amazon Web Services
Host on EC2 Windows/Linux, or containerise and deploy to ECS/EKS. Database and file server components can use AWS managed services.
- EC2 (Windows or Linux with Kestrel)
- ECS / EKS for container deployments
- S3 + CloudFront for app file distribution
- RDS for managed database
- Cognito for OAuth authentication
Microsoft Azure
Ideal for organisations with existing Microsoft infrastructure — tight integration with Azure AD for authentication and Azure DevOps for CI/CD.
- Azure App Service or AKS
- Azure AD for token-based auth
- Azure Blob Storage for app files
- Azure SQL for managed database
- Azure DevOps + PBAutoBuild pipeline
On-Premise / Private Cloud
For organisations with data sovereignty requirements — PowerServer installs on any IIS or Kestrel-capable server. Note: Appeon licensing requires internet connectivity on the hosting server regardless of deployment model.
- Windows Server + IIS (most common)
- Linux server with Kestrel
- Docker / private Kubernetes cluster
- Internet connectivity required for licensing
- Compatible with private CA certificates
PowerServer vs. Other Migration Approaches
| Factor | PowerServer Migration | Full Application Rewrite | VDI / Citrix / RDS |
|---|---|---|---|
| Timeline | ✓ Weeks to a few months | ✗ 18–36+ months | ~ Fast, but no modernisation |
| Business Logic Risk | ✓ Zero — source runs as-is | ✗ Very high — rebuilt from scratch | ✓ None — unchanged |
| Runs on | ✓ Windows PC / laptop / tablet | ✓ Web or mobile (stack dependent) | ~ Windows via remote desktop |
| Web Browser Access | ✗ Not supported (PS 2022/2025) | ✓ Yes, if built as web app | ~ Via browser-based RDP only |
| Database Security | ✓ REST API layer — DB not on client | ✓ Depends on architecture | ✗ DB often directly accessible |
| Load Testing (JMeter / LoadRunner) | ✓ Fully supported via REST endpoints | ✓ Supported (web/API architecture) | ✗ Impossible — no HTTP layer |
| Automatic App Updates | ✓ Built-in on every launch | ✓ Standard web deployment | ✓ Server-side, no client update |
| PB Feature Coverage | ✓ ~100% incl. PFC, DataWindows | ✗ Must be re-implemented | ✓ 100% — no changes |
| Cost | ✓ Low — minimal code changes | ✗ Very high | ~ Ongoing VDI licence & infra cost |