In addition to the stand-alone Repertoire Designer, there is a Repertoire Remote Designer, that provides a client GUI, but the repository, rendering and generation remains on the server. This menu option takes you to a page where you can launch the Remote Designer, using Java WebStart. You must have Java version 6 or later installed on your client machine in order to use this feature.
Once the Remote tool has been downloaded, which might take a minute or two the first time, depending on the speed of your network connection, it will be cached on your local machine, so subsequent launches will be much faster. If the Remote tool is updated on the server, then a new version will be automatically downloaded to your client next time it is executed.
Launching of the Remote tool depends on the availability of RepertoireRemote.jar, which is placed in web-resources/jnlp. To speed downloading the jar is compressed using Sun's pack200 format, so the file is actually called RepertoireRemote.jar.pack.gz. You can uncompress it manually by running
unpack200 RepertoireRemote.jar.pack.gz RepertoireRemote.jar
The unpack200 program is in your Java bin directory. You don't need to uncompress the file for use with WebStart, but you can unpack and copy this jar to the client and launch it directly from there. In this case, you won't benefit from the WebStart functionality of automatically downloading updates. To launch the jar directly, either double-click on the jar (assuming the jar file type is registered by Java) or by running:
java -jar RepertoireRemote.jar
When the Remote tool is launched from the Server by an authenticated user, it immediately opens a connection to the server. However, if the tool is accessed by an unauthenticated user, or run directly from the client machine, the user will be prompted for their user name, password and server details before being allowed to access the server resources.
When you launch the tool through WebStart, you are connecting the the URL /remote/remote.jnlp on your server. The response is constructed from remote.jnlp.template in the config directory. You can customize this to control advanced WebStart settings. Certain parameters can be passed to the remote URL and will be embedded in the jnlp response.
You can craft specific URLs to launch Remote with these parameters. For example,
/remote/remote.jnlp
?initialFile=/ElixirSamples/Dashboard/Tutorial/
dashboard/SampleDashboard.pml
&maxWorkspace=true(all on one line) will load the SampleDashboard and maximize the workspace.
The initialFile parameter will only work if the user is already authenticated with the server.