To access a provider you must give enough configuration to create a session. This includes the connection factory for your provider and any Connection details. You can either do this explicity or use the JNDI browser, we recommend the browser as its far easier and less error prone.
Configure yourself a JNDI initial context as described in Using JNDI. Double click on the context to browse its content. The following shows the contents of a JBoss and WebLogic context:
Right click on a ConnectionFactory and create a session from it. You can then right click on the destinations you want and using the Add to menu item, select the session to reference them from. The tree is also drag enabled so you can just drag administered objects into the session tree.
Select the sessions node in the main sessions tree, right click and select New session or use the icon in the configuration toolbar. Replace the name with one of your own and choose the connection factory for it. If your factory is not in the combo box then check your provider configuration and hermes.log, it will often be because its not available from the loader - read more about class loading in Hermes here. After selecting your factory, add each property that it needs by right clicking in the table and selecting Add property. As well as the standard JMS properties, you may also need to specify and configure a plugin to access non JMS features. You can read more about plugins in the Provider plug-ins page.
Here are two examples of the dialog, one with and one without JNDI.
When you've added all the properties, go on to the Destinations panel in the dialog and add in any destinations. Alternatively use the or icons in the configuration toolbar to add a new queue or topic respectively.
Note This feature is deprecated and will be removed.
In the session dialog you can enable the audit feature of Hermes. This is a simple way in which all messages added or removed to a destination are logged. When enabled a directory structure (under the .hermes directory) matching this pattern is created:
hermes-username-date/session-id/destination
In each of these directories are files called add|remove-timestamp. These messages can then be resent to the same or another destination using Hermes.