What’s New in Progress OpenEdge Command Center 2.1: Modern Administration, Easier Configuration and AI-Ready Operations

For organizations running business-critical applications on Progress® OpenEdge®, effective administration helps keep applications available, environments consistent, operations secure and teams productive. As OpenEdge environments become more distributed, hybrid and automation-driven, administrators need tools that can keep pace.

OpenEdge Command Center (OECC) 2.1 delivers enhancements across six key areas: AI-assisted insight into OpenEdge environments, PAS for OpenEdge transport management, configuration portability, database administration, identity and access control, and streamlined installation and upgrades.

AI-Ready Operations with the OECC MCP Server

One of the most significant additions in OpenEdge Command Center 2.1 is the OECC MCP Server. As AI becomes a greater part of how development and operations teams work, organizations need secure, governed ways to connect enterprise systems with AI-enabled tools and assistants.

The OECC MCP Server gives MCP-compatible AI tools read-only access to information about an OpenEdge environment, including agents, PAS for OpenEdge instances, applications, databases and transports. Teams can use natural language to ask questions such as:

• “Show me all PAS for OpenEdge instances that are currently stopped.”
• “What transports are enabled on the production PAS for OpenEdge instance?”
• “List databases with more than 100 connected users.”

The OECC MCP Server follows the open Model Context Protocol standard, making it compatible with GitHub Copilot, Claude and other MCP-enabled AI assistants.

Security and governance remain central. Because access is read-only, the OECC MCP Server cannot make changes to the environment. It also works with enterprise authentication and role-based access control, so users can access only the information permitted by their assigned roles.

This gives organizations a secure way to explore AI-assisted insights while maintaining control of business-critical OpenEdge environments. It also helps prepare OpenEdge teams for a world in which AI-assisted operations become part of everyday administration.

Simplified PAS for OpenEdge Transport Management

PAS for OpenEdge plays an important role in modern OpenEdge application architectures, but managing transports across environments can be time-consuming.

OpenEdge Command Center 2.1 expands PAS for OpenEdge administration with REST API-based management of REST, APSV, Web and SOAP transports. Administrators can now:

• Configure transport endpoints through OECC APIs.
• Enable or disable transports without editing property files.
• Automate transport management through scripts and pipelines.

Whether managing a few instances or dozens across customer deployments, these capabilities make transport management simpler, faster and more consistent, with less manual effort.

Move Configurations Across Environments with Confidence

Consistency across development, test, UAT and production environments is critical to release quality and operational risk reduction. When teams must manually recreate settings, update files or maintain custom scripts, however, configuration management becomes harder to govern and more prone to error.

OpenEdge Command Center 2.1 introduces the ability to export and import PAS for OpenEdge configurations through OECC APIs. Administrators can:

• Export a PAS for OpenEdge configuration as a structured document.
• Import the configuration into a target environment.
• Reduce the need to manually recreate property files.
• Minimize configuration drift across development, test, UAT and production environments.

For DevOps teams, automation engineers, ISV services teams and enterprise administrators, this provides a more repeatable approach to environment management and a stronger foundation for modern deployment practices. Configuration changes become easier to track, validate and apply in a controlled way.

Greater Database Visibility and Configuration Control

Database administration is another core focus of OpenEdge Command Center 2.1. Administrators need timely visibility into the databases they manage, along with practical ways to update important settings without moving between multiple tools or relying on manual file edits and command-line workflows.

With OECC 2.1, administrators can:

• View database process details, including runtime process information.
• View and update OpenEdge database configuration properties.
• Review important database startup and runtime settings.
• Create, view, update and delete database users and roles.
• Assign roles to users or revoke them as needed.
• Use OECC REST APIs to incorporate database configuration and access management into automated workflows.

These capabilities help database and system administrators manage startup, runtime and access settings more consistently across their OpenEdge environments. They also reduce the need to manually edit configuration files or repeat complex command-line steps.

More Flexible Identity and Access Control

Fine-Grained Access with Custom Roles

Not every administrator needs access to every resource. OpenEdge Command Center 2.1 introduces custom roles, allowing organizations to grant access to specific resources, such as an individual database or PAS for OpenEdge instance, rather than relying only on predefined roles.

Administrators can:

• Create roles scoped to the resources a team or individual needs.
• Create, view, update and delete roles through the Authorization Server APIs.
• Use custom roles with an external identity provider so that access aligns with enterprise policies.

This helps IT and ISV services teams apply least-privilege access across shared or multi-customer environments.

Enterprise Identity Provider Integration

OpenEdge environments often operate within broader enterprise security ecosystems where centralized identity management is essential. Many organizations use external identity providers, including Okta and Microsoft Entra ID, to manage authentication and single sign-on across business-critical applications.

OpenEdge Command Center 2.1 introduces support for external identity provider integration. Organizations can:

• Connect OECC to their existing enterprise identity infrastructure.
• Enable single sign-on, allowing administrators to use their enterprise credentials without maintaining a separate OECC password.
• Align OECC access with existing security policies and role-based access controls.

This provides a more secure and consistent approach to access management across OpenEdge environments while simplifying governance and helping organizations adopt OECC more easily.

Streamlined Installation and Upgrades

Administrative tooling should simplify operations, not create another burden for the teams responsible for managing it. OpenEdge Command Center 2.1 streamlines the OECC Server installation and upgrade experience with:

• Automated in-place upgrades.
• Intelligent configuration merging.
• Automatic backups.

A smoother upgrade experience helps teams begin realizing value sooner and supports broader adoption of modern OpenEdge administration practices.

The Path from OpenEdge Management to OpenEdge Command Center

OpenEdge Command Center continues to expand as the modern successor to OpenEdge Management. With each release, OECC adds capabilities that help customers move toward a more unified, secure and API-first approach to managing their OpenEdge environments.

Organizations currently using OpenEdge Management can begin planning their transition to OECC as Progress continues to expand its modern administration capabilities.

Who Should Upgrade?

Consider upgrading to OpenEdge Command Center 2.1 if:

• You manage PAS for OpenEdge transports manually or through property files.
• You move PAS for OpenEdge configurations between environments with scripts or manual processes.
• You need visibility into database processes without opening a separate tool.
• You need to limit teams’ access to the specific databases or PAS for OpenEdge instances they manage.
• Your organization requires single sign-on and centralized identity management.
• You want to explore AI-assisted OpenEdge operations.
• You are planning a transition from OpenEdge Management to OpenEdge Command Center.

Built for the Teams Managing OpenEdge Every Day

OpenEdge Command Center 2.1 is designed for system administrators, database administrators, application administrators, DevOps engineers, automation teams, IT operations teams and ISV services teams.

For administrators, the value is practical: fewer manual steps, better visibility, greater consistency and a more modern way to manage OpenEdge environments.

For IT leaders, the value is strategic: a stronger operational foundation for modernization, automation and long-term OpenEdge success.

Learn More

Ready to modernize how you manage OpenEdge Command Center? Learn how OECC can simplify administration, improve operational efficiency and help prepare your organization for AI-assisted operations.