To connect to Qube! MobileServer, you can use any browser, though, MobileServer serves up pages that are designed to be used by touch interfaces such as those found on smart phones and tablets. You start, then, by pointing your device's browser at the URL that was provided by the server at startup. The URL will be http:// or https:// followed by the hostname or (more likely) IP address of the machine that is running the server, followed by a ':' and then the port number on which the server is running (which, by default, is 8080).
In this example, we are running the server on the supervisor which is at 192.168.0.55. The server was started with the --allow-control option so that we have access to kill and/or retry failed frames for our own jobs. Using --allow-control implies the use of SSL which means the URL for the server will be https://192.168.0.55:8080 - make special note of the use of https rather than http. If you started with SSL (the default on OS X and Linux), then you must use https. If you started without SSL (the default on Windows), you must use http.
We then start this example by pointing our device's browser at https://192.168.0.55:8080/. Assuming you are not using an existing certificate, when the server started, it generated its own. Being that the certificate is unknown, your browser should challenge you with some sort of dialog about the untrusted certificate. This is normal - simply accept the certificate and continue.
After you accept, if you started with --allow-control and/or --authenticate, you will be challenged for your password.
After you successfully authenticate (or if authentication is not enabled), you will be presented with a list of jobs on the farm:
Note that at the top of the screen is displayed "Jobs - All" indicating that the jobs of all users are being displayed. If you would rather see only your jobs (or only a specific user's jobs), tap the gear icon at the top of the screen. This will bring you to the settings tab where you set a username and click "show only user's jobs." Click "Save Settings" and these settings will be set in your active session.
Now if you tap on the "Jobs" arrow at the top of the screen, you will be shown a jobs layout with one important difference - the username will be displayed at the top and only that user's jobs will be displayed in the job list:
Each job shows a status icon, the job ID and the job name. The orange line at the base of each job is the job's progress bar.
Tapping on any job will show you the details of that job:
At the top of this screen, you'll see the job's progress bar. Below that, you'll see details of the job. You may examine the job's package, but there is no other information available. This is done largely for reasons of security. With that said, an admin is free to edit the templates that serve up these pages to display more information, like job logs or rendered images.
Being that the server running the example was started with --allow-control and being that the job in question is owned by the user logged into the device, there are control buttons visible at the bottom of the screen: "Kill" and "Retry Failed".
"Kill" does exactly that -- it kills the job without allowing the currently running frames to finish.
"Retry Failed" re-queues all frames that failed and sets the job back into a pending state so that it may start running again.
In either case, you will be prompted before you take action:
If you choose to log out, you may do so by tapping the gear icon at the top of the screen. If you do not see a gear icon, go back to the main jobs list. Staying logged in has no ill effects on the server, though it may be a security concern.