Enable Early Access (Beta) Package URLs

Description

Starting with FileWave 16.4.0, self-managed Early Access customers can enable Beta package URLs on the FileWave Server. Early Access, also shown as Beta in FileWave Central, allows package sources that use the server runtime environment to access Beta packages, including Integrated Custom Package and Integrated Client Upgrade package sources.

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

This setting is changed on the FileWave Server. Self-managed customers need shell access to the server. Hosted FileWave customers should open a Technical Support case so FileWave Operations can handle the hosted-server Early Access process.

Enable Early Access package URLs

1. On the FileWave Server, edit the environment file:

/usr/local/etc/filewave/.env

2. Add this line on its own line:

RUNTIME_ENVIRONMENT=beta

3. Save the file.
4. Restart FileWave Server so the runtime environment is loaded:

sudo fwcontrol server restart

Confirm FileWave Central is using Beta

When Central connects to a server using the Beta runtime environment, FileWave Central shows BETA in the window title and in the bottom-right status area. Clicking the BETA indicator opens this article.

Disable Early Access package URLs

1. Remove this line from /usr/local/etc/filewave/.env:

RUNTIME_ENVIRONMENT=beta

2. Save the file.
3. Restart FileWave Server again:

sudo fwcontrol server restart

Related Early Access articles

• What is the Early Access Program?
• Building Custom Clients During Early Access

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.