Creating a complete backup before the upgrade ensures you can restore your deployment if validation fails. Follow these steps to backup before stopping the profile and do not store private keys or JWTs in source control:

  1. Set the working directory to the OpenEdge MCP Server installation directory:
    cd "$OEMCP_HOME"
  2. Generate a timestamp and archive the generated profile and server registry:
    
# Create backup archive with timestamp
BACKUP_DATE=$(date +%Y%m%d-%H%M%S)
tar -czf "../${PROFILE}-backup-${BACKUP_DATE}.tgz" \
    "generated/$PROFILE" \
    generated/servers.registry.tsv
  3. Save a known successful tool invocation as functional evidence:
    # Capture known successful tool invocation as functional baseline
./mcpgen client "$PROFILE" --tool "$TOOL" --args "$TOOL_ARGS" --json \
  > "../${PROFILE}-tool-call-pre-upgrade.json"
  4. Confirm that all expected backup artifacts were created before you continue:
    ls -l "../${PROFILE}-backup-${BACKUP_DATE}.tgz" \
      "../${PROFILE}-tool-call-pre-upgrade.json" \

The backup should capture:

  • Profile server configuration
  • Service-account keys and token metadata
  • Certificates (public and private)
  • Prompt files (if used)
  • Context files (if used)
  • File ownership and permissions (preserved by tar, subject to the privileges of the user creating and restoring the archive)