These instructions are preliminary, and a bit "rough and ready".
Connecting to your QRISdata Mediaflux Desktop
Your QRISData Mediaflux Desktop is accessed using the Arcitecta Desktop tool (also known as "Hydrogen") running in your web browser. The recommended procedure for connecting to the QRISdata Mediaflux installation is as follows:
- Visit https://mediaflux.qriscloud.org.au/desktop/?dti=no
- Login as follows:
- Domain: "qrisdata" (this could change)
- User: QSAC username
- Password: QSAC password
The left sidebar of the Mediaflux Desktop has the main Desktop tools. The top one allows you to read and search the Mediaflux manuals.
Note: the URL above runs the Desktop with DTI disabled. This is recommended for end users, unless they specifically need the DTI functionality. The reason is that DTI requires a Java install and Java plugin. Installing these things, and configuring the user's browsers is daunting, and not recommended unless the user is capable of providing their own Tier 0 / 1 support.
Limitations / Bugs
The following are known limitations / features / bugs of Mediaflux Desktop (DTI=no):
- Importing by dragging an entire directory tree only works on Chrome. For other browsers, the import stalls. (Apparently, it is a limitation of the HTML5 File API.)
Aterm is the preferred Mediaflux tool for doing Mediaflux system management tasks. It can also be used by collection owners and end-users who have QSAC credentials and have been granted collection access.
The aterm tool is a Java application that is distributed as a JAR file which you can download from the Mediaflux server. The prerequisites are:
- A Java JDK or JRE installation. Java 6 or later is sufficient, but we recommend that you use a recent release, and ensure that it is patched with the latest security patches. (You do not require a Java plugin for your web browser to run aterm.)
- An X11 installation. X11 is a standard part of current Linux desktop distros, and is available in the Utiliities folder on Mac OSX. Free 3rd party X11 software is available for Windows.
To install aterm:
- Open a web browser.
- Enter https://mediaflux.qriscloud.org.au/mflux/aterm.jar
- Save the file; e.g. on Linux your ~/bin directory might be a good place.
- At a command prompt, run "java -jar ~/bin/aterm.jar" ... or wherever you saved the JAR, and a window will launch, showing a "Login" popup.
- Enter the following in the "Login > Login" panel:
- Server: "mediaflux.qriscloud.org.au"
- Transport: "HTTPS"
- Port: "443"
- Domain, User and Password as above.
Using aterm is outside of the scope of this document. However help information is available in the following places:
- Typing "help" at the aterm command prompt will list all commands that the server makes available to you.
- Typing "help <command.name>" will print the command's self-documentation. The same information can be seen on the Mediaflux server's web portal:
- Visit https://mediaflux.qriscloud.org.au/mflux.
- Click on the Help link.
What is DTI?
DTI stands for desktop tool integration (or something like that). If you run the Mediaflux Desktop with DTI enabled you get a number of advanced features including:
- drag and drop files between your local machine and Mediaflux filespaces,
- bulk file upload via the desktop, and
- use of Arcitecta's high performance file transfer protocol.
The downside is that DTI is implemented as a Java application that your web browser needs to be able to launch. This requires that the user has a Java installation on their desktop / laptop, and that the Java plugin is properly enabled ans authorized.
Assuming that you have installed Java and enabled the Java plugin, then you can connect to the Mediaflux using the URL https://mediaflux.qriscloud.org.au/desktop/ - note that the "?dti=no" query is no longer required.
If DTI is working properly, the Desktop will display "DTI:active" or "DTI:active (unverified version)".
If DTI is not working, there may be clues in the "DTI:..." field. Some of the things to consider:
- Is Java installed on the user's machine properly? Is it a recent version? Has it changed recently; e.g. via an automated system update?
- Is the Java plugin installed?
- Is the Java plugin enabled for this browser session?
- Is SELinux in "enforcing" mode? (This stops the DTI application talking to the local file system. The workaround is to switch to "permissive" mode for the duration of the Mediaflux session!)
According to the current documentation:
- If you want to use DTI, you need an up-to-date Java 7 or Java 8 installation. (Indeed, if you are using Firefox as your browser, you typically need the very latest patch release, as Firefox aggressively disables Java plugins with known security issues.)