Installation Directory Structure Overview

The installation directory is organized into clearly defined subdirectories. This directory structure applies specifically to the /opt/protegrity/upgrade directory. Each directory has a specific role during installation, upgrade, rollback, and runtime operations.

bin/ Directory

The bin directory contains the executable component required to perform upgrade and rollback operations. This directory includes:

• The sdkupgrd binary, which is the primary executable used for upgrade and rollback workflows.

• The 10.0.gpg file must be manually added to this directory from ESA and is required for verification purposes.

  For more information about GPG signature verification, refer to GPG Signature Verification.

Note: No additional binaries or scripts are stored in this directory.

data/ Directory

The data directory stores configuration and metadata files that drive upgrade and rollback behavior. It also enables coordination between components. This directory contains:

• sdkupgrd.conf, which is the main configuration file used to provide inputs for:
  • Upgrade operations
  • Rollback operations

Note: The configuration file supports both mandatory and optional settings and is updated as part of upgrade workflows.

• metadata.ini, which acts as a coordination and interaction point between the protector and the agent upgrader. It is used to exchange state and progress information during upgrades and ensures both components remain synchronized.

logs/ Directory

The logs directory is used to store runtime and upgrade‑related logs. It is logically divided into two types of logs with different lifecycles and purposes.

• Agent logs are stored here temporarily. These logs are sent to ESA Insight and are automatically removed once their contents are successfully uploaded.
• A version‑defined subdirectory is used to store protector logs. These logs are retained locally and are not sent to ESA Insight.

active_processes/ Directory

The active_processes directory is used to track currently running protector processes. This directory contains:

• active_pid files, where each file represents an active protector process.
• Each active_pid file includes metadata related to the corresponding running AP Java process.

This directory is used to track running protector instances and to prevent conflicting upgrade or rollback operations. It also provides visbility into currently running processes.