Selecting The Default Application

You can set the default application you see when you log into OpenGroupware via the "Display" section of the preferences application. Here you can adjust the order of applications displayed in the dock, as well as remove an application outright. The application which appears at the top of the dock is the application that the OpenGroupware interface will default to when you log in.

For instance, you can set it to the "Calendar".

  1. Log into OpenGroupware.

  2. In the "Misc" dock (menu) on the left of the page click "Preferences"

  3. In the "Preferences Viewer" application click "Display" under "Application Preferences".

  4. Under "Dock" you see the applications that appear in the application dock.

  5. Click the up and down arrow to re-arrange the order of the applications. The application at the top of the list will be displayed automatically when you login to OpenGroupware. If you move the "Calendar" to the top of the list, the calendar will be displayed immediatly when you log in.

  6. When you have completed rearrainging the applications click the "save" button at the bottom of the page.

  7. Click the "Logout" link in the "Misc" dock on the left hand side. You should be returned to the default application you selected once you log back in. If you are using BASIC authentication then you should log back in immediately after clicking "Logout".

NOTE: You will notice a short horizontal line in the dock list under the application icons. This may have applications listed below it. Moving applications beneath this line hides them in the dock (they will still be operational but will not appear for selection). If you don't use a Palm Pilot, for instance, you can move the "Palm Syncronization" application below the line so that it does not appear in the dock.


XMPP Notification From OpenNMS

OpenNMS is a sophisticated and feature rich enterprise ready network monitoring solution (NMS). OpenNMS will monitor your systems via SNMP for performance information as well as availability by performing actual service requests such as HTTP requests. One of the most important features of any NMS is the ability to notify administrators when something has gone wrong either by e-mail, page, or some other means. OpenNMS supports a variety of notification methods (and you can add your own), and since version 1.2.1 this includes XMPP (aka "Jabber").

The configuration of XMPP notification is very simple assuming you have a functioning XMPP server (I strongly recommend Wildfire, formerly known as JIVE Messenger). You need to edit the xmpp-configuration.properties file in $OPENNMS_HOME/etc. This file contains three parameters: xmpp.server, xmpp.user, and xmpp.pass.

xmpp.server is the hostname of your XMPP server.

xmpp.user is the username (JID) that OpenNMS will use when connecting to the server.

xmpp.pass is the password that corresponds to the provided JID.

That is it! So the contents of this file might simply look like:

xmpp.server = gourd-amber.morrison.iserv.net
xmpp.user = opennms
xmpp.pass = thepassword

Obviously, since the password is provided in this file in plain text, you should ensure that the account used to authorize this connection has very limited privileges.

In the user configuration section of the "Admin" link (available in OpenNMS when you are logged in as a user posessing the administrative role) you can enter the user's JID in the "XMPP Address" field. This enables that user to receive XMPP notifications.

Note: It is important to recognize that the OpenNMS never is "present" as far as the XMPP service is concerned. It only sends messages. Therefore it will not appear in the roster of the users IM client, if the user is blocking messages from entities not on her or his roster/buddy-list then they will never see the messages from the OpenNMS service.

The last step in making all this work is that you must enable the "xmppMessage" command in the desired destination path(s). The configuration of "Destination Paths" is located within the "Configure Notifications" section of the "Admin" portion of the OpenNMS web interface. Simply select the notification path you want to generate the XMPP notices and make sure the "xmppMessage" command is highlighted in the commands multiselect widget.

Once XMPP messages are rolling out you will see messages in the notifd.log file like:

2006-01-05 02:45:41,244 DEBUG [Thread-598] ClassExecutor: Going for the class in stance: org.opennms.netmgt.notifd.XMPPNotificationStrategy
2006-01-05 02:45:41,244 DEBUG [Thread-598] ClassExecutor: org.opennms.netmgt.not ifd.XMPPNotificationStrategy class created: class org.opennms.netmgt.notifd.XMPP NotificationStrategy
2006-01-05 02:45:41,308 DEBUG [Thread-598] NotificationTask: command xmppMessage return code = 0

This is also the place to look if you don't believe your messages are getting through.

Resetting An Account's BIE Password

BIE users and their passwords are stored in the USERS table of the internal Hypersonic database. If you happen to end up with an account that is locked out of BIE because they forgot their password or tried the wrong time too many times you can reset their status and password by modifying the database. The login is stored in the "USERNAME" field, the passphrase is stored encrypted in the "PASSPHRASE" field, and there is also a "STATUS" field that must be "ACTIVE" for the user to be able to login. So to reset an account's BIE password:

  1. Stop the BIE service

  2. Start the embedded Hypersonic client.

  3. Execute the following command, replacing the value of the USERNAME field with the login whose password you wish to reset.

    SET PASSPHRASE = '46f94c8de14fb36680850768ff1b7f2a',
    WHERE USERNAME = 'adam'

  4. Choose Options / Commit in the Hypersonic client's menu.

  5. Exit the Hypersonic client.

  6. Start the BIE service.

  7. Login!

Note: This resets the account to the default BIE password of 123qwe