Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)FrançaisItaliano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

Install the OpenEdge Command Center

Upgrade interruption behavior and recommended actions

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • Install and configure the OpenEdge Command Center server
    • Launch the OpenEdge Command Center server installer
    • Install OpenEdge Command Center server in high availability setup
    • Install OpenEdge Command Center server in console mode
    • Silent installation of OpenEdge Command Center server
    • Start OpenEdge Command Center server
    • Provide MongoDB package for offline installation
  • Install and configure OpenEdge Command Center agent
    • Launch the OpenEdge Command Center agent installer
    • Install OpenEdge Command Center agent in console mode
    • Silent installation of OpenEdge Command Center agent
    • Bootstrap policy file
    • Start the OpenEdge Command Center agent
  • OpenEdge Command Center server configuration
    • Data store configuration file
    • System configuration file
    • Server configuration file
  • OpenEdge Command Center agent configuration
    • OpenEdge Installation configuration file
    • Java properties file
    • Server information file
    • Agent configuration file
  • Configure mutual TLS authentication
    • Enable TLS logs for OpenEdge Command Center
  • Upgrade OpenEdge Command Center server
    • Upgrade OpenEdge Command Center server on Windows and Linux
    • Upgrade additional OpenEdge Command Center server in high availability
    • Upgrade OpenEdge Command Center server in console mode
    • Silent upgrade of OpenEdge Command Center server
    • Upgrade interruption behavior and recommended actions
      • Resume upgrade interrupted during pre-install phase
        • Restore OpenEdge Command Center database
      • Resume upgrade interrupted during install phase
      • Resume upgrade interrupted during post-install phase
  • Upgrade OpenEdge Command Center agent
    • Upgrade OpenEdge Command Center agent on Windows, AIX, and Linux
    • Upgrade OpenEdge Command Center agent in console mode
    • Silent upgrade of OpenEdge Command Center agent
  • Uninstall OpenEdge Command Center server
  • Uninstall OpenEdge Command Center agent
  • View installation log files for OpenEdge Command Center server and agent
  • Troubleshoot installation and configuration issues for OpenEdge Command Center server and agent
    • MongoDB installation fails during OpenEdge Command Center server installation
    • OpenEdge Command Center server fails to start after installation
    • OpenEdge Command Center server or agent uninstallation fails
    • OpenEdge Command Center server or agent reinstallation fails after uninstallation
    • OpenEdge Command Center server startup failure in high availability setup
    • OpenEdge Command Center server upgrade fails to resume after interruption
Table of Contents

Upgrade interruption behavior and recommended actions

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: April 6, 2026
  • 1 minute read
    • OpenEdge Command Center
    • Version 2.1
    • Documentation
Interrupting the OpenEdge Command Center server upgrade leaves the system in a state that depends on the upgrade phase at the time of interruption. This section describes the expected behavior for each phase and recommended actions to continue the upgrade.
Important: Progress recommends not to interrupt the installer during an upgrade. Otherwise, it can leave files and services partially updated and requires manual recovery to resolve.

Identify the system state

Use the following table to determine the system state after upgrade interruption and identify the applicable recovery procedure.

Interrupted phase System state Recovery procedure

Pre-install

  • The installer does not trigger a rollback.
  • The earlier version of server remains listed as installed.
  • The system may remain in a partially prepared state. For example, prerequisite checks are completed.
See Resume upgrade interrupted during pre-install phase

Install

  • The installer triggers a rollback, which uninstalls the existing server binaries.
See Resume upgrade interrupted during install phase

Post-install

  • The installer does not trigger a rollback.
  • The new version of server is listed as installed, but some post‑install tasks, such as service creation or service startup (when the server is installed as a service), or final cleanup may not have completed.

See Resume upgrade interrupted during post-install phase
Contents
  • Resume upgrade interrupted during pre-install phase
  • Resume upgrade interrupted during install phase
  • Resume upgrade interrupted during post-install phase
Alert