Migrating from Classic Application Server to Progress Application Server for OpenEdge

Learn how migrating to Progress’s Application Server for OpenEdge can help evolve your OpenEdge Application.

Progress first launched the Progress OpenEdge Application Server, also known as the Classic Application Server (CAS) in 1996. This initial version of the OpenEdge application server utilized a proprietary architecture. The implementation was complicated and utilized a number of external components that required adapters for WebSpeed, web services, AIA, and REST to respond to HTTP/https requests.

Introduction of the Progress Application Server for OpenEdge

As distributed applications and N-Tier architectures became more widely adopted, Progress continued introducing new enhancements and functionality to its application server in order to evolve along with the growing needs of its customers and partners. Fast forward several years, Progress introduced PAS for OpenEdge which is a platform that provided a number of improvements including:

• A scalable architecture using far less resources
• A simplified implementation that is easily upgradable from the classic app server
• Better analysis tools for monitoring and administering including industry-standard JMX (using any third-party Tomcat tool)
• Faster thru-put and performance (in some cases, exponential)

Another benefit of the PASOE Application server is that it is available as two configurations including PASOE for OpenEdge development, which is extremely flexible and configurable during the development and testing process, and deployment version, which has been hardened for security purposes as you deploy your application.

Cloud-based, Scalable and Secure

Progress Application Server for OpenEdge is a scalable and cloud-ready server that optimizes operations and reduces management costs. This modern application server unifies all of the Progress products into a single powerful industry-standard platform resulting in easier and more comprehensive management, a scalable architecture, a simplified implementation, better analysis tools, and faster thru-put and performance.

Progress Application Server for OpenEdge (PAS for OpenEdge) is based on the industry-standard Apache Tomcat webserver. This is beneficial because Apache Tomcat updates ensure compliance with industry standards, like Spring Security. Also, the server has built-in routing and adapter functionality which enables you to access your business logic on a variety of clients including ABL, browser-based clients, and mobile clients.

Migrating from PAS Classic to PAS OpenEdge

Migrating an application from the classic OpenEdge AppServer or the WebSpeed Transaction Server to the Progress Application Server for OpenEdge (PAS for OpenEdge) should involve minimal changes to ABL application code.

However, an OpenEdge application may encompass many distributed components including multiple AppServers, adapters, various types of OpenEdge and non-OpenEdge clients, NameServers, and so forth.

If your business requires assistance migrating from the Classic App server to PASOE, the experts on Progress’s Professional Services team provide PASOE migration services along with a series of on-demand webinars and training courses such as Progress Application Server for OpenEdge Administration to help ease your transition.

Contact Progress Professional Services