Updating an Install Manually

Updating an Install Manually With a Patch File

Simple Step-by-Step Instructions

📋 Pre-Upgrade Checklist

• [ ] Coordinate upgrade date with customer

• [ ] Schedule training session if needed

• [ ] Review release notes for changes

• [ ] Backup production database (licensed customers only)

🔧 Step 1: Enable Maintenance Mode

Location: /var/www/pcr360/test/public/index.php

1. Open index.php file

2. Find the line: APPLICATION_MAINTENANCE = false;

3. Change it to: APPLICATION_MAINTENANCE = true;

4. Save and upload the file

Result: Only PCR staff can access the application - customers see "Maintenance Mode" screen.

📁 Step 2: Extract Patch Archive

Extract the patch file:

1. Navigate to the patch file location

2. Extract the .tar.gz file:

   CODE

   tar -xzf 2024.2.4-2025.1-MySql.tar.gz
   

3. This creates a folder named 2024.2.4-2025.1-MySql

📁 Step 3: Update Application Files

Source: Extracted “Patches” folder
Destination: Customer server, usually /var/www/pcr360/<environment>

Files to Copy:

Copy ALL files and folders from inside the Patches folder

• After extracting Everything from the archive file

• All subfolders and files inside the Patches directory should be copied

• The entire patch contents should be copied to the base of the PCR-360 environment. This is generally located at either:

  • /var/www/pcr360/test

  • /var/www/pcr360/prod

🔄 Step 4: Deleted Files

Check for a deletes.txt file from the patch:

1. Open controllers/controllers.txt from the patch

2. If the file is empty or doesn't exist, no files need to be deleted

3. If the file contains patches, each file should be removed from the environment

4. This is generally located at either:

   • /var/www/pcr360/test/<path_to_deleted_file>.php

   • /var/www/pcr360/prod/<path_to_deleted_file>.php

🗄️ Step 5: Run Database Updates

Location: SQL360 Repository → Maintenance → [Database Type] → [Version]

Required SQL Files:

From the patch's sql/ folder, run these files in order of the version:

For version 2024.2:

• sql/2024.2/2024.2_default.sql

• sql/2024.2/2024.2_archive.sql

• sql/2024.2/2024.2_metadata.sql

For version 2025.1:

• sql/2025.1/2025.1_default.sql

Run these commands in order:

• Execute each .sql file in your database management tool

• Run them in the order of the versions

• Make sure to run ALL files for each version

🔄 Step 6: Run Custom Controllers

Check the controllers.txt file from the patch:

1. Open controllers/controllers.txt from the patch

2. If the file is empty - no custom controllers to run

3. If the file contains URLs - run each controller URL in your browser

4. Run them in the order listed in the file

🔄 Step 7: Update System Data

Run these URLs in your browser (append to customer's installation URL):

1. Update Menu: /cron/db/update-menu

2. Reload Lists: /cron/db/reload-lists

3. Reload Import Types: /cron/db/reload-import-record-types

🏗️ Step 8: Rebuild Views

Run these URLs in order:

1. Rebuild MT-Views: /update/create/mt-views

2. Rebuild Views: /update/create/views

✅ Step 9: Validate Database

Run these validation checks:

1. Main Validation: /update/validate/

2. SQL Validation: /update/validate/sql

3. Metadata Validation: /update/validate/metadata

4. Archive Validation: /update/validate/archive

If any validation generates SQL output, run that SQL in your database.

💰 Step 10: Test Billing (If Applicable)

Only if this release contains billing changes:

1. Run a test bill before upgrade

2. Record the totals

3. Run a test bill after upgrade

4. Compare totals - they should match (unless billing changes were intentional)

🚀 Step 11: Disable Maintenance Mode

Location: /var/www/pcr360/data/inbound/2024.2.4-2025.1-MySql/public/index.php

1. Open index.php file

2. Find the line: APPLICATION_MAINTENANCE = true;

3. Change it back to: APPLICATION_MAINTENANCE = false;

4. Save and upload the file

🧪 Step 12: Final Testing

• [ ] Log into the application

• [ ] Test a few grids and forms

• [ ] Verify no obvious issues

• [ ] Inform customer that upgrade is complete

📞 Step 12: Customer Communication

• [ ] Notify customer that upgrade is complete

• [ ] Update customer tracking document

• [ ] Address any issues found by customer

• [ ] Schedule production upgrade (if this was test environment)

🚨 Troubleshooting

Common Issues:

• Error 500: Check that all required folders were copied correctly

• Database Errors: Run validation steps again

• Missing Features: Check if all SQL files were executed

• Billing Issues: Compare pre/post upgrade totals

When to Get Help:

• Contact manager if you need to deviate from these steps

• Create Service Desk ticket for code-related issues

• Consult team lead for complex database problems

📚 Additional Resources

• Release Notes: Check for version-specific instructions

• Internal Wiki: Look for upgrade-specific controller processes

• Customer Tracking: Update documentation after each step

Remember: This guide covers the standard upgrade process. Some versions may require additional steps - always check the release notes and internal wiki for version-specific instructions.