Scope has been developed using the Java programming language. Building upon the Java platform has enabled Riege Software to provide our customers with a stable environment that is supported natively on all modern desktop platforms (Windows, macOS and Linux).
Applications written in Java require a local installation of the “Java Runtime Environment” provided by Oracle. Until end of 2018, Scope also built upon the “Java Web Start” framework for deployment and updates.
In March 2018, Oracle announced that with the public release of Java 11 in September 2018, the Java Web Start technology was going to be discontinued and removed from the Java Runtime Environment.
To continue to provide our customers with the best Scope experience possible, we have been working on an alternative technology that has come into effect with the release of Scope 11, due in Q4 of 2018.
With release 11, Scope requires the usage of the “Scope Runtime” software application. This application is available as a free download from our website. Executables are provided for Microsoft Windows and macOS. The Scope Runtime application will not be available for Linux-based Operating Systems, however we will provide a solution for these users as well, if requested. Please contact our Scope Support Helpdesk (email@example.com) in this case.
Scope Runtime contains a bundled Java Runtime Environment that is provided exclusively for the purpose of running Scope. In addition, it contains technology developed by Riege Software to replace parts of the functionality that has been provided by the Java Web Start framework. Namely it is responsible for downloading the actual Scope application itself and keep Scope up-to-date.
Scope Runtime is available from Riege Software's website at riege.com/scope/download
There are 3 different versions:
Recommended for Windows 7, 8 and 10 users.
This installs the Scope Runtime in the user profile of the Windows user.
For Apple users.
Recommended for operation in a “Terminal Server”, “Remote Application Service” or “Virtual Desktop” environment such as “Windows Server 2012” or later, “Parallels RAS” or “Citrix Virtual Apps and Desktops”. Scope Runtime for Terminal Servers has been created to work well in a multi-user environment.
There are two key differences to the regular Scope Runtime:
- Scope Runtime for Terminal Servers does not update itself automatically. Updates have to be done manually by a system administrator.
- Scope Runtime for Terminal Servers uses different directories for storing files to make Scope Runtime work well when being used by multiple users.
Scope uses the following directories:
|Target||Description||Windows||Terminal Server||Required Permissions|
|Scope Runtime||Location where the Scope Runtime executable is installed||%LOCALAPPDATA%\Programs\Scope Runtime|
(This may be changed at installation time.)
(This may be changed at installation time.)
|Scope Application||Location where the Scope Application Client is installed||%APPDATA%\RIEGE||%ALLUSERSPROFILE%\RIEGE||Scope Users: Read/Write|
|Scope Data||Location where Scope caches some data locally, like codelists||%APPDATA%\RIEGE||%APPDATA%\RIEGE||Scope Users: Read/Write|
Once Scope Runtime for Terminal Servers has been installed, users simply visit their “Scope Homepage” in a web browser and invoke the “Start” button. Scope will automatically be downloaded (if necessary) and an icon will be created on the Windows desktop.
Custom batch files as well as the “Static Scope Client” are not supported anymore.
System Requirements for the Scope Runtime Environment
Scope Runtime Environment has been extensively tested with Windows 10. There is a special version available for systems running on Windows Server 2012R2, 2016 or 2019.
On the Apple Mac, Scope Runtime Environment supports macOS High Sierra or higher.
At least 500 Megabytes of free RAM is required to run Scope Runtime Environment.
At least 500 Megabytes of free space is required to install Scope Runtime Environment.
Scope Runtime Environment checks for updates upon startup. An active internet connection is required for this. Scope Runtime Environment needs to be able to access the host
getscope.riege.com on port 443. All communication is secured by TLS.
Additionally, Scope Runtime Environment needs to be able to contact the Scope server(s) that it connects to. The address and port is dependent upon your specific configuration, if you encounter any issues our Scope Support Helpdesk (firstname.lastname@example.org) will be more than happy to help.
If you are connecting via the Internet, Scope uses the HTTPS protocol on port 443 to secure the communication between the client and the server. Ensure that your firewall allows this connection and that it does not tamper with its security.
Some firewalls decrypt and re-encrypt the connection. Scope considers this to be a man-in-the-middle attack and will show an error message:
Older version of Scope Runtime (11.6 and before) will show this dialog:
Contents of the Scope Runtime Environment
The Scope Runtime Environment contains:
- A Java Runtime Environment provided exclusively for the purpose of running Scope.
- The “Scope Bootloader” technology that is responsible for keeping your local Scope installation up-to-date.
Scope Runtime Environment keeps itself up-to-date and ensures that you are always using the best version of Java and Scope Bootloader to ensure a maximum of compatibility.
The Scope Bootloader technology has been developed by Riege Software to replace parts of the functionality that have been provided by the discontinued Java Web Start framework.
Namely, the Scope Bootloader is responsible for:
- Downloading Scope
- Keeping the local Scope installation up-to-date
How does Scope Runtime Environment work?
Scope Runtime Environment registers itself as a Protocol Handler for the
scope protocol with the underlying Operating System. When the user clicks on a link designated with the
scope protocol, the contents of the link are handed to the Scope Runtime Environment application which is responsible for starting the Scope Bootloader with these contents.
Frequently Asked Questions
When will Scope Runtime Environment be released?
Scope Runtime Environment will be released to the public with Scope release 11
Where can Scope Runtime Environment be obtained from?
The official source for Scope Runtime Environment is the Riege Software website at https://www.riege.com/scope/download/. There are no other official distribution channels.
Can I install Scope Runtime Environment while I still work with Scope 10?
Yes! Scope 10 will still use a local installation of Java 8, it will not use the version of Java provided by Scope Runtime Environment.
How much disk space does Scope Runtime Environment require?
Scope Runtime Environment itself requires about 250 Megabytes of free disk space. Each version of Scope that is managed by the Scope Bootloader requires an additional 100 Megabytes of free disk space.
Is a local stand-alone Java installation still required for Scope 11?
No. Scope Runtime Environment contains a packaged version of Java that will be used for running Scope.
Do I need to buy support for Java from Oracle to run Scope?
No. Scope Runtime Environment ships with a dedicated Java Runtime Environment based upon the OpenJDK project. You do not have to purchase a license or support from Oracle to run Scope.
What license does the OpenJDK Java Runtime Environment use?
The OpenJDK is licensed under the GNU General Public License, Version 2, with Classpath Exception.
Can I remove local installations of Java from my machine?
This depends. If Scope is the only application that requires Java, then yes. If you have other applications installed that rely upon Java you should contact their respective vendor(s).
Can I run Scope without the Scope Runtime Environment?
Technically yes, but this is not supported by Riege Software. Please contact us to discuss your specific requirements via our Scope Support Helpdesk (email@example.com).
How secure is Scope Runtime Environment?
All binaries provided will be digitally signed by Riege Software.
How does the Scope Runtime Environment determine whether it requires an update?
Upon startup, the Scope Runtime Environment will check the address https://getscope.riege.com/live/updates.xml to decide if an update is available. If applicable, it will download the required update.
Where does the Scope Runtime Environment downloads its updates from?
Currently the updates are hosted on a server that is located in Riege Software's datacenter. Pending demand patterns, we might decide to involve a Content Delivery Network in the future to provide our users with an optimised download experience.
Will future releases of Scope depend upon Scope Runtime Environment?
Yes. Starting with Scope 11, all future versions of Scope will require the Scope Runtime Environment. If this requirement changes, we will make a proper announcement a few months ahead.
How frequently is Scope Runtime Environment updated?
We expect to update Scope Runtime Environment infrequently. Our target is not more than four updates per calendar year (one per quarter). Regular updates will be announced about one month prior to release. Security Updates may be scheduled more frequently. All updates will be announced in a timely manner prior to general availability.
Is a specific version of Scope Runtime Environment required to run Scope?
We will try to keep old versions compatible with future updates of Scope. However we strongly encourage users to always run the latest version to ensure maximum compatibility.
Can I start the Scope Runtime Installer in “silent” mode?
Yes, by adding the flag
-q to the command line. This will install Scope Runtime into the default directory.
11.10 – 2019/MAY/16
- Upgrade to Java 11.0.3.
- macOS: Improve background image of DMG file.
- Windows: Improve display of Scope Runtime version information in the Windows Control Panel.
11.9 – 2019/MAR/05
- Windows 32-bit: Fixed Installer crashing in some Windows 32-bit environments.
11.8 – 2019/FEB/01
- macOS: Fixed the name of the Dock Icon of subsequently started processes.
- Uninstalls any previous versions of Scope Runtime on update.
11.7 – 2019/JAN/29
- Upgrade to Java 11.0.2.
- Show better error messages when the HTTP connection fails due to certificate validation errors.