I expect HermesJMS to be webstart deployed for two types of users, one read only and one read write. A read only user can browse and monitor but cannot put messages, truncate queues etc whereas a read write user has full access to all the features. You can simply run the webstart versions from the homepage or you can deploy locally.
The JNLP file is in $HERMES_HOME/webstart/hermes.jnlp. This directory also contains copies of all the Hermes libraries digitally signed by myself, the libraries in the lib directory are not signed. When configuring for your envionment, you'll need to change the following:
- Change the codebase and href in the jnlp node to point to your installation. I think its best to keep the JNLP file and libraries in the same directory on your web server.
- You no longer need to set the hermes property, HermesJMS will bootstrap a local configuration for a new user in the $HOME/.hermes directory.
- You can support different remote and read only configurations by cloneing the JNLP file and changing the value of the hermes property.
- If you want to sign the libraries with your own coroporate certificate, sign the libraries from the HermesJMS lib directory and replace those from the webstart directory.
- Set the property hermes.restricted to any value and you'll start Hermes as read only.