What's New in OpenEdge Command Center 2.0

System Administrators and Application Administrators can now install the OpenEdge Command Center server without requiring to manually download and configure MongoDB. In addition, the installer now provides enhanced, intuitive installation screens that guide you through the setup process with minimal effort.

Previously, Administrators had to manually download and install MongoDB before setting up the OpenEdge Command Center server, which created unnecessary overhead in the installation process.

This feature simplifies the installation process and provides a quicker and more reliable installation experience.

For more information, see Install and configure the OpenEdge Command Center server and Troubleshoot installation and configuration issues for OpenEdge Command Center server and agent.

A new component called the Authorization server is introduced in OpenEdge Command Center to manage user access. The Authorization server manages user access to the OpenEdge Command Center server, the OpenEdge Command Center agent and its managed resources, including PAS for OpenEdge instances and OpenEdge databases, and the Authorization server itself, using Role-Based Access Control (RBAC). RBAC determines access to the OpenEdge Command Center components based on assigned roles.

The Authorization server also provides user and role management capabilities. You can create users and assign and remove roles for accessing OpenEdge Command Center components using the Authorization server REST APIs.

For more information, see Authorization server and Create users and manage roles using Authorization server.

All the OpenEdge Command Center components, such as the server, agent, and Authorization server, now communicate over HTTPS only, ensuring transport-level security. Also, OpenEdge Command Center now supports mutual TLS authentication, which validates the identities of both parties involved in communication, so that each party is trusted by the other.

To implement mutual TLS authentication, trusted root CA-signed certificates presented by both parties are verified before establishing a secure connection. So, OpenEdge Command Center provides default certificates to all its components. Alternatively, you can provide them with signed certificates, as described in Configure mutual TLS authentication. If any certificate lacks proper hostname information, you can bypass the hostname validation by disabling the newly-added nohostverify property. Any failures during the mutual TLS authentication process are recorded in the log files.

System Administrators and Database Administrators can now use OpenEdge Command Center to view the schema, users, and system-defined roles information of a running OpenEdge database.

By logging into the selected database from OpenEdge Command Center, they can view these details:

• Schema: Includes tables and columns

• Users: Includes usernames and their associated roles

• System-defined roles: Includes created by, type, and description associated with each role.

For more information, see View schema, users, and roles of a selected database.

System Administrators and Application Administrators can now view and update the configuration of an ABL application deployed on a PAS for OpenEdge instance. The new Edit ABL Application page provides a user-friendly interface to manage configurations, such as MSAgent startup settings, session procedures, logging options, and PROPATH with minimal clicks. Administrators can access the page from either the PAS for OpenEdge Instances page or the ABL Applications page.

For more information, see Edit ABL application.

OpenEdge Command Center now supports deployment of the ABL applications and their associated web applications to the PAS for OpenEdge instances using the OpenEdge Application Archive (OEAR) files.

As a System Administrator or Application Administrator, you can deploy the ABL application along with its associated web applications to the PAS for OpenEdge instance in one go by using this new simplified deployment process.. Previously, OpenEdge Command Center supported only WAR file-based deployment.

For more information, see Deploy ABL application and Manage ABL applications.

The OpenTelemetry (OTel) metric names of OpenEdge resources, PAS for OpenEdge and OpenEdge database, are now standardized based on industry norms.

Previously, the dynamically generated metadata was embedded within metric names, which made it difficult for users to query and filter data in the configured APM tools. Now, the dynamic data is separated into resource-level and metric-level attributes, which makes it easier to query and filter data in the configured APM tool.

Also, a new metric, instance_running_status, is introduced, which indicates the operational status of an OpenEdge resource.

For more information, see OpenTelemetry metrics for OpenEdge database and OpenTelemetry metrics for PAS for OpenEdge.