What's New in OpenEdge Command Center 2.1

Administrators can now create, retrieve, update, and delete custom roles for OpenEdge Command Center agents through the Authorization Server APIs. Custom roles apply to only the resources that the administrators choose, unlike predefined system roles that provide access to all the resources. Thus, with custom roles, administrators can grant users the least-privilege access to only the specific resources that an OpenEdge Command Center agent manages, such as an OpenEdge database or a PAS for OpenEdge instance.

For more information, see Create and manage custom roles and Authorization Server REST API Reference.

OpenEdge Command Center now supports user authentication through an external identity provider that complies with OpenID Connect (OIDC). You can configure Microsoft Entra ID or Okta, or any other identity provider for OpenEdge Command Center to enable single sign-on, centralized user management, and multi-factor authentication enforced by identity provider for your organization. Users sign in through the identity provider and their OpenEdge Command Center permissions are determined by the app roles that they are assigned in the identity provider.

You can use the SWITCHAUTHMODE utility on the OpenEdge Command Center server to store and activate authentication configurations and to return to local authentication when required. At a time, only one authentication mode is active, and an inactive configuration is retained so that you can activate it again without entering its configuration values again.

For more information, see Learn about external identity provider (IdP) authentication and SWITCHAUTHMODE utility.

System Administrators and Application Administrators can now use an MCP-compatible AI client to retrieve authorized information from OpenEdge Command Center. The OpenEdge Command Center MCP server provides:

• Read-only tools for viewing authorized information about server nodes, Agents, OpenEdge installations, PAS for OpenEdge instances, applications, transports, and databases.
• Prompts that guide the MCP client in using read-only tools to review and summarize information about your OpenEdge Command Center environments.

The MCP Server is included with the OpenEdge Command Center Server installation. It does not modify OpenEdge Command Center resources. It uses:

• The authentication mode configured for OpenEdge Command Center
• The authenticated user’s existing roles and permissions to control access to information

For more information, see Learn about the OpenEdge Command Center MCP Server.

OpenEdge Command Center now supports database configuration management through REST APIs. As a Database Administrator, System Administrator, or DevOps Engineer, you can create, view, update, and delete configurations. You can also retrieve database summary details and database parameters for an OpenEdge database.

Previously, you could perform these tasks only through OpenEdge Management, command-line utilities, or by manually editing database configuration files. With REST APIs, you can now easily manage configurations across the General, Background Writers, After Image Management, International, Advanced, Diagnostics, Statistics, SQL Configuration, SSL Configuration, and Agent categories.

This feature reduces manual configuration-file changes and helps minimize configuration errors, while enabling you to automate database configuration tasks through REST APIs.

For more information, see OpenEdge Command Center REST API Reference.

Administrators can now manage OpenEdge database users, roles, and role assignments through OpenEdge Command Center REST APIs. They can create, update, view, and delete database users and roles, and assign or revoke one or more roles for a user.

Previously, administrators could only view the schema, users, and roles of a selected OpenEdge database. However, it did not provide a way to create, update, or delete the database users or roles, or to manage role assignments.

This feature simplifies database access management by allowing you to centrally create and manage database users and roles through OpenEdge Command Center APIs. It improves consistency and security across environments, supports automation, and provides a foundation for future user interface enhancements.

For more information, see OpenEdge Command Center REST API Reference.

Administrators can now reset the password for the OpenEdge Command Center database user account by using the resetoeccdbpassword utility. The utility can be run on a standalone server or the primary server in a high-availability setup. This enhancement enables administrators to change the database password in accordance with organizational security policies.

For more information, see RESETOECCDBPASSWORD utility.

OpenEdge Command Center now provides real-time process details for a running OpenEdge database, including details of CPU and memory consumption, broker process details, and the number of connected database users through REST APIs.

Previously, Database Administrators, System Administrators, or DevOps Engineers could retrieve this information only through OpenEdge Management or command-line tools. With the REST APIs, they can now easily monitor database health and automate database health checks.

For more information, see OpenEdge Command Center REST API Reference.

OpenEdge Command Center now supports managing APSV transport for a PAS for OpenEdge instance through REST APIs. Previously, System Administrators or Application Administrators could manage APSV transport only by using separate PAS for OpenEdge utilities.

For more information, see OpenEdge Command Center REST API Reference.

OpenEdge Command Center now supports managing REST transport for a PAS for OpenEdge instance through REST APIs. Previously, System Administrators or Application Administrators could manage REST transport only by using separate PAS for OpenEdge utilities.

For more information, see OpenEdge Command Center REST API Reference.

OpenEdge Command Center now supports managing SOAP transport for a PAS for OpenEdge instance through REST APIs. Previously, System Administrators or Application Administrators could manage SOAP transport only by using separate PAS for OpenEdge utilities.

Now, they can also use OpenEdge Command Center APIs to perform the following SOAP transport management tasks:

For more information, see OpenEdge Command Center REST API Reference.

OpenEdge Command Center now supports managing web transport for a PAS for OpenEdge instance through REST APIs. Previously, System Administrators or Application Administrators could manage web transport only by using separate PAS for OpenEdge utilities.

Now, they can also use OpenEdge Command Center APIs to perform the following web transport management tasks:

For more information, see OpenEdge Command Center REST API Reference.

OpenEdge Command Center now supports exporting the supported PAS for OpenEdge run-time configurations as portable JSON files and importing them into one or more registered target PAS for OpenEdge instances through REST APIs. You can select PAS for OpenEdge configuration files, ABL applications, and Web applications for export, and use application mappings when the source and target names differ.

Before importing a configuration, OpenEdge Command Center verifies compatibility between the source and target environments. The import also supports dry-run mode, per-target results, and automatic backup and restoration to help you review and apply configuration changes safely.

The export excludes sensitive and environment-specific properties. These properties are not applied during import and you must configure them separately in the target environment.

For more information, see OpenEdge Command Center REST API Reference.