JabberWatcher

JabberWatcher’s configuration is composed of 3 files :

1. jabberswatcher.xml : the main configuration files. it contains jabber connection informations, users and groups definitions.
2. mappings.xml : defines all the commands.
3. logging.properties : log4j configuration.

Jabber connection configuration

JabberWatcher needs a jabber account to conect to.

JabberWatcher can connect to jabber servers, using SSL or not and to GoogleTalk service. This configuration can be done by editing jabberwatcher.xml :

• jabberserver : the server where your account resides.

• jabberport : server’s port (leave default if the server uses the standard jabber’s ports).

• ssl : 1 to connect using SSL, 0 if not.

• jabberid : the jabber’s identifier.

• jabberpassword : the account’s password.

• googletalk: 1 if you use a googletalk account (notes that jabberserver and jabberport will not be taken in account in this case).

Group configuration
Group are defined to allow access to command. With groups, you’re able to define profiles to apply to people.

By default, JabberWatcher use 2 accounts, which is suffisent to begin :

1. admin : can execute all the commands.
2. user : can execute only commands that does involve jabberwatcher’s administration.

User configuration

Users are people allowed to send instant messages (ie commands) to JabberWatcher.

First you must add your own jabber’s account, to be able to start with JabberWatcher.

A user account is composed of :

1. an Id : it is the user’s internal id.
2. a jabberid : it is the jabber’s user account
3. a group : the group to which the user belongs to.

Starting JabberWatcher

To start JabberWatcher, use the shell script : start.sh (UNIX or Linux), or start.bat (Windows).

You can now send basic commands.