What is PAS for OpenEdge 3.0?

PAS for OpenEdge 3.0 is a version of the Progress Application Server for OpenEdge that is delivered and installed separately from OpenEdge itself. Unlike the previous generation PAS for OpenEdge that ships inside every OpenEdge installation, PAS for OpenEdge 3.0 decouples application server and its third-party dependencies (Tomcat, Spring Framework, Spring Security) from the OpenEdge release cycle. The multi-session (MS) agent and licensing continue to reside with your OpenEdge installation.

For more information, see PAS for OpenEdge 3.0.

Why is PAS for OpenEdge 3.0 introduced?

The previous generation PAS for OpenEdge is tightly coupled to OpenEdge release cycles, which means security fixes and framework upgrades for third-party libraries such as Tomcat and Spring can only be delivered as part of a full OpenEdge release. As OpenEdge long-term support (LTS) releases age, third-party vendors frequently end support for older versions, leaving the product exposed to security risks. PAS for OpenEdge 3.0 breaks this dependency so that Progress can deliver security fixes, framework upgrades, and stability improvements rapidly without waiting for an OpenEdge release.

For more information, see PAS for OpenEdge 3.0.

What are the key benefits of switching to PAS for OpenEdge 3.0?

The key benefits are:
  • Faster security and framework updates
  • Reduced environment complexity
  • Lower long-term maintenance effort
  • Minimal disruption during updates

For more information, see PAS for OpenEdge 3.0.

Does PAS for OpenEdge 3.0 change how the MS Agent or licensing works?

No. The MS Agent and licensing remain with your OpenEdge installation. Only application server and its third-party dependencies are decoupled. Each PAS for OpenEdge instance is still tied to one OpenEdge installation for licensing and compatibility.

For more information, see PAS for OpenEdge 3.0.

Does installing PAS for OpenEdge 3.0 update my existing PAS for OpenEdge instances?

No. The installer only installs the PAS for OpenEdge runtime in the new location. Existing instances created with the previous generation PAS for OpenEdge must be migrated separately.

For more information, see Migrate existing instances between previous generation PAS for OpenEdge and PAS for OpenEdge 3.0.

Can I update PAS for OpenEdge without upgrading OpenEdge?

Yes. This is one of the primary design goals of PAS for OpenEdge 3.0. Because application server is decoupled from the OpenEdge release cycle, you can apply PAS for OpenEdge updates (security patches, framework upgrades) on their own schedule without touching your OpenEdge installation. For more information, see PAS for OpenEdge 3.0.

After installing PAS for OpenEdge 3.0, what additional step is needed to use it with OpenEdge?

You must run the integration script (oe-pasoe-integrate.sh on Linux or oe-pasoe-integrate.bat on Windows) to configure your OpenEdge DLC installation to use the PAS for OpenEdge 3.0 runtime instead of the previous generation. Place the script and pasplugin.jar in the same directory before running it.

For more information, see Use OpenEdge with PAS for OpenEdge.

Do I need to migrate existing PAS for OpenEdge instances after running the integration script?

Yes. The integration script reconfigures OpenEdge so that newly created instances use the PAS for OpenEdge 3.0 runtime. Existing instances that were created with the previous generation PAS for OpenEdge must be migrated separately by re-registering them.

For more information, see Migrate existing instances between previous generation PAS for OpenEdge and PAS for OpenEdge 3.0.

Will migrating an existing instance affect my application code or instance-specific settings?

No. Re-registering an instance only updates its runtime configuration to point to the PAS for OpenEdge runtime. Application code and instance-specific settings are not changed.

For more information, see Migrate existing instances between previous generation PAS for OpenEdge and PAS for OpenEdge 3.0.

Can I go back to the embedded PAS for OpenEdge after integrating with PAS for OpenEdge 3.0?

Yes. Run the integration script with the --revert flag.

For more information, see Roll back to previous generation PAS for OpenEdge from PAS for OpenEdge 3.0.

After reverting the integration, do I also need to roll back my PAS for OpenEdge instances?

Yes. After reverting the integration (which affects the DLC-level configuration), you should also migrate existing instances back to the previous generation PAS for OpenEdge by re-registering them.

For more information, see Migrate existing instances between previous generation PAS for OpenEdge and PAS for OpenEdge 3.0.