REST API client (PB → external)
PowerBuilder making outbound REST calls with proper auth (Basic, Bearer, OAuth2 client-credentials), retry semantics, timeout handling and structured error logging.
C · Connect
Enterprise Integrations for PowerBuilder Applications
REST, SAP, reporting and document pipelines that connect PowerBuilder cleanly into the modern enterprise stack — and keep working after the next PowerBuilder upgrade.
- REST · OAuth2
- SAP RFC / BAPI
- PDF · reporting
- Webhooks
What's included
Concrete deliverables in an Integrations engagement
Integrations are easy to make work once. The harder problem is making them survive the next upgrade, network change or partner contract revision. Each deliverable below addresses both.
REST API server (external → PB)
Lightweight gateway in front of PowerBuilder business logic, exposing modern endpoints with versioning, auth and a documented contract — without rewriting the application.
SAP RFC and BAPI integration
Direct SAP integration via standard connectors, with the boring-but-vital details handled: connection pooling, BAPI commit/rollback, character-set mapping, error-class translation.
Reporting and PDF pipeline
Modern report generation that scales beyond what DataWindow PDF can do: server-side rendering, templating, batching, e-mail and store-to-fileshare flows.
ODBC / JDBC adapter normalization
Cleaning up the integration layer between PowerBuilder and external databases, normalizing driver versions, fixing character-set drift, eliminating brittle dynamic SQL.
Webhook receiver
PowerBuilder application receiving webhooks from modern SaaS (Stripe, HubSpot, Slack, internal microservices) — with signature verification, idempotency and retry semantics.
File / FTP → API replacement
Replacing legacy file-based exchange (overnight FTP, CSV drops, SMB shares) with proper APIs while keeping a file-mode fallback during the transition.
Integration test harness
Automated tests that run before each deploy and catch broken integrations early. Critical for systems where integration failure is silent and expensive.
When this engagement fits
Typical situations behind an Integrations call
Integration work usually starts because someone external changes a contract — SAP version, partner API, file format, security policy. The application has to keep talking.
SAP migration changes the contract
Your SAP team is moving to S/4HANA, cleaning up custom transactions, or replacing RFCs with OData. The PowerBuilder side has to keep working through it.
We have to integrate with a modern SaaS
Sales / finance / HR rolled out a new SaaS platform. It has a REST API. PowerBuilder is meant to send and receive — and IT doesn't want a hand-coded one-off.
Legacy file exchange must become an API
Auditors, partners or compliance pushed back on overnight FTP / CSV drops. The exchange needs to move to authenticated APIs, but the business logic still lives in PB.
Reports are slow and the PDF looks dated
Reporting volume grew, runtime hammers the OLTP database, the DataWindow-rendered PDF looks like 2008. Time to lift the reporting workload off and modernize the output.
How we work
From contract to running integration
Integrations fail less from technical problems than from unclear contracts. We spend more time at the start nailing the shape, and less time later debugging mysteries.
01
Map
Current data flows, contracts with each party, error paths, retry behaviour, who fixes what when something breaks. Often the first time it's written down.
1–2 weeks02
Design
Integration shape: protocol, auth, retry, idempotency, observability. Reviewed with you and (if relevant) with the partner system's team before any code.
1 week03
Build
Implementation in PowerBuilder + supporting service if needed. Test harness alongside the code. Monitoring hooks. Documented run book.
scoped · weeks04
Handover
Run book + change log + on-call instructions for your team. Optional follow-up retainer to handle the next contract change in 6–12 months.
ongoing optionalFrequently asked
Answers to common questions about Enterprise Integrations for PowerBuilder
Can PowerBuilder really make modern REST calls?
Yes — even PB 9 can. The HTTPClient and RestClient APIs were added in PB 11 / Appeon era and improved in every release since. For older PowerBuilder, we use a thin native wrapper that survives upgrades. The pattern is well-established; the work is in handling auth, retries and errors cleanly, not in the HTTP call itself.
We're stuck on SOAP and the partner moved to REST. Can you bridge?
Yes — common scenario. Either by upgrading PowerBuilder's HTTP layer, or by placing a small adapter service between PB and the partner. Both work; the right choice depends on how many integration points you have and what your IT environment allows.
How do you handle OAuth2 / mTLS / SAML?
OAuth2 client-credentials and authorization-code flows are standard in our engagements. mTLS is supported via Windows certificate store on the PowerBuilder side. SAML usually lives in front of your application (SSO), not in PowerBuilder itself — we wire it via the gateway.
Can the integration survive a PowerBuilder upgrade?
Yes — that's a design goal, not a coincidence. We isolate the integration code in dedicated PBL files with stable interfaces and avoid coupling to anything PB-version-specific. When the upgrade happens, the integration layer needs at most a recompile, not a rewrite.
We need webhooks coming into PowerBuilder. How does that work?
PowerBuilder applications are typically thick clients with no server endpoint — so an HTTP-receiving service sits in front, validates and persists the incoming event, and the PB application picks it up (DB row, message queue, file). The pattern is well-understood and we ship it routinely.
Contact
Need to integrate PowerBuilder with the enterprise stack?
Send a short description of the integration: which systems, what protocol, what's forcing the change. We'll reply within one business day with a practical next step.
What we need first: PB version, the systems on both sides of the integration, current protocol, target protocol, deadline (if there is one).
NDA-friendly · MSA-ready · GDPR · References on request · Hourly or fixed-fee
Other services
Adjacent engagements
Integration work often surfaces parallel needs — modernizing the runtime around it, or shoring up the database underneath. We sequence them so the integration ships first.
A · Support
PowerBuilder Legacy Support
Production support, troubleshooting, small fixes, stabilization and continuity for systems that are running but no longer easy to maintain in-house.
SLA · incident · monthly
B · EvolvePowerBuilder Modernization
Upgrade planning, PowerBuilder 2022 / 2025 readiness, UI improvements, deployment modernization, PowerServer / PowerClient strategy.
scoped · phased · safe
D · DataDatabase & Performance
Oracle PL/SQL, SQL Server T-SQL, stored procedures, packages, triggers, views and performance tuning of data-heavy enterprise applications.
Oracle · SQL Server · PG
E · LeadTechnical Leadership
Architecture review, code review, mentoring, project coordination and rescue consulting — senior eyes on the difficult decisions that protect the system.
review · mentor · rescue
F · RetainContinuity Retainer
Reliable monthly access to rare PowerBuilder expertise without hiring a full-time developer. Reserved capacity, predictable response time.
monthly · on demand