Phase 2 - Update 243 Testing

Applying Update 243 In Your Own Environment:

We’re pleased to announce that Phase 1 testing is now complete. During this phase, Partners were provided access to their own Update 243 databases hosted on our Cloud Server. This initial stage has successfully identified and resolved a number of issues. While some finalisation work remains on our end, we are now ready to move into the next phase — releasing an update for Partners to conduct specific testing related to custom scripting, custom modifications and general testing against a wider selection of databases .

Originally, our intention was to allow Partners to upload copies of their client databases to our Cloud Server. However, after review, we determined this approach would be impractical as it would limit each Partner to a single database.

As a result, this next phase will be a local update, allowing you to run Update 243 in your own TCP/IP environment. This approach offers a key advantage — you’ll be able to test the upgrade and your custom scripts across multiple databases, providing a more realistic and flexible testing environment.

Since this will be a local installation of Update 243, no cloud server will be involved. Partners will be able to upgrade copies of their client databases locally to fully test their existing custom scripts. This will help ensure confidence — for both you and us — that these customisations will continue to function correctly once your clients are migrated to Update 243.

Importantly, the Update routine will not impact your current 242 environment.

Because this Update is being performed in a separate 243 environment, some steps are unique to this process. These would not normally be required in a standard update.

Please note:

• Testing does not require Firebird 5 unless you specifically wish to test against it.

• If you do wish to run Update 243 with Firebird 5, you will need to have Firebird 5 already installed and configured on a different port to your existing Firebird 2.5 installation.

• Firebird 2.5 will be fully sufficient for the purposes of testing custom scripts.

Prerequisites:

Applying Update 243 – Local Environment Setup Instructions

As we will be using your existing AWS Database License Key for testing, please follow the steps below carefully to prepare and apply Update 243 in your own environment.

1. Save Your Existing License Key

• Log on to your organisation’s AWS Remote Database.

• Navigate to: File → System Configuration → License Key

• Copy and save the displayed License Key into a Notepad file for later reference.

2. Prepare Your Database for Upgrade

• Make a copy of the database you intend to upgrade.

  • This MUST be a 242 database.

  • As a best practice, prefix the copied database name with “243_” (e.g., 243_ClientName).

• If you have any users with workflows linked to a path that includes {AppPath}, ensure you:

  • Copy these workflow files, and

  • If a Workflows folder exists, copy that folder into your new 243 folder.

  • If the Workflow files are pathed with either a Local or UNC path directly to the Ostendo folder (or a folder outside of the Ostendo folder) you will need to amend these paths to include {AppPath} and ensure these files / Workflow folder are located in your 243 folder prior to upgrading the database.

• If you have Custom Reports associated with this database:

  • Locate the company’s Reports folder (under your 242 environment).

  • Copy this folder into your new 243 folder, and rename it to “Reports”.

3. Copy Required Files

From your 242 Ostendo folder, copy the following files into your 243 folder:

• WebView2Loader_x86.dll

• fbclient.dll

4. Update the Ostendo Configuration Utility

• From your 243 folder, run (as Administrator) the file: ostendoconfig.exe

• Go to the Utility Updates tab.

• Locate the record Client Configuration, press Action, and select Download & Update.

• Once the Utility Program has updated, you may be prompted to re-run it.

  • If prompted, run it again as Administrator.

• Return to the Utility Updates tab and update the following components in order:

  • Edge Browser DLL → press Action → Download & Update

  • Database Update Utility → press Action → Download & Update

5. Verify Updates

After completing all updates, your screen should display all components as up to date.

Note: The version numbers shown below may differ slightly from the latest available versions.

6. Update Ostendo

• Navigate to the Ostendo Updates tab.

• Press Action and select Download & Update.

• After the update is complete, your screen should display the latest version of Ostendo.

  Note: The version number shown below may differ from the latest available release.

7. Configure the Local Company Connection

• Select the Companies (Local) tab.

• Tick the Select Company on Startup option. It is also suggested that this same option is selected on the Companies (Remote) tab

• Press the Add button.

  • Complete the company details as follows:

    • Company Name: Enter a name, e.g. 243_ABC.

    • (Optional) Colour: Choose a colour to easily identify this database band.

    • Server / Local Machine: Enter your computer name or server name.

    • Port Number (optional): Specify a port number only if your Firebird installation uses a non-standard port (i.e. different from 3050).

    • Database Path: Browse to and select the database you intend to upgrade.

• Press Save to confirm and store the configuration.

Upgrade Process

8. Launch Ostendo 243

• From your desktop, launch Ostendo 243 using the Ostendo 243 icon.

• When prompted, select the company you configured in the previous step (e.g. 243_ABC). (NB: Do not attempt to Change Company from within an existing 243 session from another database)

9. Update the Database

• You will be prompted to update the database.

• Select Yes to proceed.

10. Appling the Ostendo Update

• Press Get Update to continue.

• The dbupdcloud application will then be invoked

• Answer Yes to the prompt to continue

The Update process will now begin

• We have tested this process on multiple databases on a standalone PC from 1Gb through to 139Gb and on each occasion this process took approx 30 mins to complete

11. Complete the Database Update

• Upon completion, you should Press the Close and Save Log button.

• We recommend renaming the file and saving it. This file may be required later for investigation or troubleshooting purposes..

Post Update Tasks

12. Launch Ostendo 243

• From your desktop, launch Ostendo 243 using the Ostendo 243 icon.

• When prompted, select the company 

13. Acknowledge the Warning Screen

• Upon selecting the company, a warning screen will be displayed.

• Press OK to continue.

14. Enter a New License Key

• PASS “License Expired” screen will appear.

• Press the “I have a new licence key” button.

• Enter the AWS Database License Key you saved earlier in the Notepad File (Step 1)

• Press the Verify button. This will activate your Ostendo 243 environment, allowing you to continue.
   

           


15. Migrate Custom Reports and Graphical Files

• Log on to the Ostendo 243 database.

  • Ensure you type your password in UPPERCASE.

• Navigate to:
  File → System Configuration → Cloud Migration Utilities

• Select both:

  • Migrate Report Files

  • Migrate Graphical Files

• Press OK to import all custom report layouts and graphical files (e.g., workflows) into the updated database.

16. Handling Workflows with {AppPath} References

• If any user workflows are configured with {AppPath} paths, a warning message will be displayed.

• If this message appears, it means the workflows need to be copied into your 243 folder. If you haven’t done this yet, select No, copy the workflows, and then repeat this process.