Belmark

Full-Stack OpenEdge Modernization — 11.7 to 12.8

Client: Belmark Industry: Manufacturing Project Focus: Platform Upgrade, Infrastructure Automation, CI/CD, Developer Enablement, Database Optimization

Overview

Belmark's core business operations run on a Progress OpenEdge platform that supports ERP, web applications, and critical manufacturing workflows. The platform is deeply embedded in daily operations — it is not optional infrastructure.

The engagement encompassed a comprehensive upgrade from OpenEdge 11.7 to 12.8, but the scope extended well beyond the version change. We rebuilt the infrastructure automation layer, established CI/CD pipelines for OpenEdge ABL, standardized developer environments, trained the team on modern version control practices, optimized database performance, and executed production cutovers with zero downtime.

The Challenge

Belmark was running Progress OpenEdge 11.7 across development, QA, and production environments. The version was approaching end of support, and the gap between current state and target (12.8) represented a platform-level shift — not a patch — touching databases, application servers, developer tooling, CI/CD pipelines, and server infrastructure.

The risks were compounded by several factors:

No environment automation. RHEL servers were manually provisioned and configured, making environment parity unreliable and rebuilds time-consuming.
No CI/CD for ABL. OpenEdge ABL code was deployed manually with no automated build, test, or promotion process across environments.
Inconsistent developer environments. Each developer's PDSOE setup was configured independently, leading to drift, onboarding friction, and integration issues.
Limited version control practices. While Bitbucket was in place, the team lacked structured branching strategies and consistent Git workflows.
Database performance concerns. Index structures and tuning parameters had not been revisited in years and needed optimization for the new platform version.
RHEL version currency. The underlying Red Hat Enterprise Linux servers also needed upgrading to remain on supported versions.

The upgrade had to happen without disrupting production operations. Belmark could not afford extended downtime or a failed cutover — the platform runs the business.

The Solution

Infrastructure Automation with Kickstart

We designed and implemented automated provisioning of RHEL servers using Kickstart. This replaced manual server builds with a repeatable, documented process that produced consistent environments across development, QA, and production tiers.

When RHEL versions needed upgrading to remain on supported releases, the Kickstart automation made it possible to rebuild environments cleanly rather than performing risky in-place upgrades.

CI/CD Pipeline for OpenEdge ABL

We built CI/CD pipelines using Jenkins that automated the build, compilation, and deployment of OpenEdge ABL code. The pipelines pushed to multiple testing and staging slots on the RHEL servers, giving the team a structured promotion path from development through QA to production.

This removed manual deployment steps, reduced human error, and gave the team confidence that what they tested is what they shipped.

Developer Environment Standardization

We automated the setup of PDSOE (Progress Developer Studio for OpenEdge) to create consistent developer environments. The automated setup connected each developer's workspace to the correct Atlassian Bitbucket repositories, configured project settings, and eliminated the hours of manual configuration that previously accompanied each new setup or workstation rebuild.

This reduced onboarding time for new developers and eliminated a class of integration issues caused by environment drift.

Git Training and Branching Strategy

We trained Belmark's OpenEdge developers on Git fundamentals — commit discipline, merge workflows, conflict resolution, and history management. We then worked with the team to define and implement branching strategies suited to their release cadence and team structure.

This was not theoretical training. We worked alongside the team during real development cycles to reinforce practices and resolve workflow questions as they arose.

Database Performance Optimization

We reviewed and optimized OpenEdge database indexes and tuning parameters. Index structures that had accumulated over years of organic growth were analyzed against actual query patterns, and tuning parameters were adjusted for the 12.8 runtime characteristics.

The result was measurable improvement in database performance — faster queries, reduced lock contention, and more efficient resource utilization.

Zero-Downtime Production Cutovers

We assisted in production cutovers and deployments with zero downtime. The combination of automated infrastructure, tested CI/CD pipelines, and rehearsed cutover procedures meant that each deployment was controlled, reversible, and invisible to end users.

RHEL Environment Upgrades

We upgraded the Red Hat Enterprise Linux environments to newer supported versions. The Kickstart automation we established earlier in the engagement made these upgrades predictable — each environment was rebuilt to specification rather than patched in place.

Results

The upgrade delivered more than a version change. It established a modern operating foundation for Belmark's OpenEdge platform:

Platform upgraded from OpenEdge 11.7 to 12.8 across all environments
Infrastructure automation established with Kickstart for repeatable RHEL provisioning
CI/CD pipelines operational for OpenEdge ABL across testing, staging, and production
Developer onboarding reduced from hours of manual setup to automated PDSOE configuration
Zero production downtime during cutovers and deployments
Database performance improved through index optimization and tuning
Team capability elevated through Git training and structured branching strategies
RHEL environments upgraded to current supported versions

About Our Approach

This engagement reflects how we approach legacy platform modernization: stabilize first, automate delivery, and build durable capabilities the team keeps after we leave.

We did not treat the OpenEdge upgrade as an isolated version bump. We recognized that the version change was an opportunity to address the infrastructure, tooling, and process gaps that made every previous change to the platform riskier than it needed to be.

The automation, pipelines, and developer tooling we implemented are now part of Belmark's standard operating environment — not one-time project deliverables, but permanent capabilities that reduce risk and improve velocity on every subsequent initiative.