Skip to main content

Enable Early Access (Beta) Package URLs

Description

Starting with FileWave 16.4.0, self-managed Early Access customers must enable Beta package URLs on the FileWave Server before using the Early Access upgrade mechanisms for FileWave Central, Server, Clients, Boosters, or Imaging Virtual Servers (IVS). Early Access, also shown as Beta in FileWave Central, allows package sources that use the server runtime environment to access Beta packages, including integrated package and upgrade sources.

Use this only for FileWave Early Access/Beta testing when directed by FileWave. Early Access packages are intended for validation before general availability.

Plan Central, Server, Client, Booster, and IVS upgrades

Enabling Beta package URLs means the environment is opting into Early Access/Beta upgrade sources, not just changing the label shown in Central. Enable it before starting the Early Access upgrade sequence. After the setting is loaded, FileWave Server uses Early Access/Beta package URLs. Once the Server and FileWave Central are upgraded to 16.4, Central can show the Beta state, Boosters become eligible for Beta upgrades, integrated Client upgrades can target Beta packages, and the 16.4 IVS upgrade workflow can use the matching Early Access package source.

Client upgrades during 16.4 Early Access

At least during the FileWave 16.4 Early Access cycle, keep the macOS and Windows Client Upgrade Filesets in your client-upgrade plan. The newer integrated client upgrade path depends on the client already being at the newer upgrade baseline.

For example, clients running FileWave Client 16.2 need a Client Upgrade Fileset path first. They do not appear in Software Updates > Client Upgrades, and an empty view does not mean they are current. Without a 16.4 Client Upgrade Fileset, you would first deploy a 16.3 Client Upgrade Fileset and then let the automatic/integrated upgrade path continue from there.

The 16.4 macOS and Windows Client Upgrade Filesets are designed to return requirements not met on devices that are already running FileWave Client 16.3 or later, so they can act as a bridge for older clients without replacing the integrated upgrade behavior for clients that already meet the newer baseline.

Schedule the Beta target from the right-click menu. Select the eligible client or group in Client Upgrades, right-click it, and choose Schedule Beta Upgrade. The toolbar scheduling action is for the non-Beta target.

See Upgrading FileWave Clients for sanitized examples of an eligible client, the misleading empty state, and the Beta scheduling menu.

The Client Upgrade Fileset also remains a support-guided fallback during Early Access testing. If the integrated client upgrader does not behave as expected, FileWave Support may direct you to import the Client Upgrade Fileset and adjust its requirement check for a specific recovery path.

After a FileWave Server upgrade, compatible Boosters are automatically scheduled for upgrade. By default, that automatic Booster upgrade is scheduled 7 days after the Server upgrade. For Early Access testing, set the automatic Booster upgrade delay to 0 days before upgrading the Server if you want Boosters to upgrade immediately instead of waiting the default week.

In FileWave 16.4.0 and later, that delay is controlled in FileWave Central > Preferences > Upgrades. The setting is evaluated when the Server upgrade schedules Booster upgrades, so changing it afterward does not retroactively reschedule Boosters that were already queued.

Enable Early Access package URLs

The Server package provides /usr/local/etc/filewave/.env.example. A live .env file may not exist until the environment needs an override; this is normal. Because the filename begins with a period, make sure hidden files are visible when checking the directory.

  1. On the FileWave Server, editchange to the environmentconfiguration file:directory:
cd /usr/local/etc/filewave
    Create .env from the packaged example only if .env does not already exist: 
    sudo test -f .env || sudo cp -p .env.example .env

    Do not overwrite an existing .env file. It may contain other active environment settings. Do not substitute an old .env.bak file for the current packaged example unless FileWave Support specifically directs you to do so.

      Open /usr/local/etc/filewave/.env
        with Addyour preferred editor and add this line on its own line: 
        RUNTIME_ENVIRONMENT=beta
        1. Save the file.
        Confirm the setting appears exactly as expected: 
        sudo grep -n '^RUNTIME_ENVIRONMENT=beta$' /usr/local/etc/filewave/.env
        1. Restart FileWave Server so the runtime environment is loaded:
        sudo fwcontrol server restart

        Continue to the correct upgrade guide

        Do not expect the BETA label before the upgrade. The BETA indicator is new in FileWave Central 16.4. Enabling the Beta package URLs on an earlier Server makes the Early Access packages available, but the existing Central application cannot display that new label.

        Confirm Beta after Central is upgraded

        After FileWave Central is upgraded to 16.4 and connects to a Server using the Beta runtime environment, Central shows BETA in the window title and bottom-right status area. Use this as the post-upgrade confirmation before scheduling Beta Client, Booster, or IVS actions. Clicking the BETA indicator opens this article.

        FileWave Central 16.4 showing the BETA indicator in the window title and bottom-right status area

        Disable Early Access package URLs

        1. Remove this line from /usr/local/etc/filewave/.env:
        RUNTIME_ENVIRONMENT=beta
        1. Save the file.
        2. Restart FileWave Server again:
        sudo fwcontrol server restart

        Notes

        • Early Access and Beta refer to the same testing channel in this context.
        • The server restart is required after enabling or disabling the flag because FileWave Server reads the runtime environment during startup.
        • The short link for this article is https://go.filewave.com/beta.
        Back to top