Overview
The world of enterprise manufacturing software is increasingly split: cloud-native ERP platforms like Syteline Cloud, QAD Adaptive ERP, and others promise modern APIs, real-time data, and SaaS scalability — while a huge installed base of Progress OpenEdge applications continues to run the day-to-day operations of thousands of manufacturers. The challenge isn't choosing one or the other. It's making them work together.

This session presents a complete, working integration architecture built at Wyman Gordon, a precision aerospace forging company and division of Precision Castparts Corp. The goal: allow existing OpenEdge ABL programs to retrieve live data from Syteline Cloud via Boomi web services — with no changes to the calling programs, clean error handling, and intelligent caching — all implemented as a structured shared library in standard ABL.

What You'll Learn
• How to structure an ABL shared library (.p / .i) for consuming REST web services
• Configuring HTTPS clients, SSL protocols, and cipher suites from ABL using the OpenEdge.Net.HTTP namespace
• Implementing Basic Authentication against Boomi-hosted endpoints
• Designing a temp-table caching layer to avoid redundant web service calls within a session
• Using syscode-style configuration tables to externalize endpoints, credentials, and feature flags
• Graceful degradation: falling back to local database reads when cloud services are unavailable
• Parsing JSON responses from Boomi into ABL temp-tables via READ-JSON
• Patterns for exposing the library to calling programs via persistent procedures and forward declarations

Architecture Walkthrough
The session is built around a live code walkthrough of the slibslcws library — a set of structured ABL include files and a persistent procedure that together form the integration layer. Key components covered include:
• slibslcws.p / slibslcws.i — the persistent procedure and include entry point
• slibslcwsprop.i — shared variable and temp-table definitions (ttCallLog, ttItemData, ttCustomerOrders, ttOrderShipments)
• slibslcwsfrwd.i — function forward declarations for clean scoping across include files
• slibslcwsfunc.i — function implementations: getItemData, getCustomerOrders, fnCreateCallLog, fnGetSyscodeValue, fnSetSyscodeValue
• slibslcwsproc.i — wsCallWithAuthSSL internal procedure handling the full HTTP request/response lifecycle
• slibslcwsGetVars.i / slibslcwsGetParams.i — local variable scaffolding and parameter passing includes

Who Should Attend
This session is aimed at intermediate to advanced Progress OpenEdge developers who are working with or considering integration with cloud ERP platforms, middleware layers like Boomi, or external REST APIs. Familiarity with ABL, persistent procedures, and basic HTTP concepts is helpful but not required — the architecture is explained from the ground up.

Key Takeaways
• A reusable architectural pattern for ABL-to-cloud REST integration
• Working code structure you can adapt to your own Boomi or REST endpoints
• Best practices for credential management, SSL configuration, and response caching in ABL
• A practical approach to building cloud-ready features into existing OpenEdge applications without disrupting what already works

Short abstract:

Modern manufacturing environments increasingly rely on cloud-based ERP platforms like Syteline Cloud — but many shops still have deep investments in Progress OpenEdge applications that aren't going anywhere. So how do you bridge the two?

In this session, Chris Kelleher shares a practical, real-world approach to integrating Progress OpenEdge ABL with cloud applications using Boomi as the middleware layer. Drawing on his current work at Wyman Gordon (a division of Precision Castparts Corp.) and over 30 years of OpenEdge experience, Chris walks through the design and implementation of a reusable ABL shared library that:

• Calls Boomi-hosted REST web services with HTTPS and Basic Authentication
• Manages SSL protocols and cipher configuration from ABL
• Caches web service responses in temp-tables for efficient reuse
• Falls back gracefully to local Symix/QAD database data when cloud services are unavailable
• Stores integration configuration (endpoints, credentials, feature flags) in a syscode table — no hardcoding

Whether you're maintaining a legacy OpenEdge application or building new integrations against a cloud ERP, this session will give you a concrete architectural pattern and working code you can take back to your shop.