Chapter 84. Short Configuration Guide
Prev |  | Next

# Chapter 84. Short Configuration Guide

Artur Hefczyc <artur.hefczyc@tigase.net> v2.0, June 2014: Reformatted for AsciiDoc. :toc: :numbered: :website: http://tigase.net :Date: 2010-04-06 21:16

Options you most likely have to change at deployment time are:

1. Admin accounts - account names where all admin messages are sent.
2. Hostnames - real and virtual hostnames your server has to serve for.
3. Logs - setting related to log file location and how much information should be logged there.

Please let me know if you think more options should be described here.

Changing configuration using command line tool.

Detailed description of configuration management tool in on project site on the: ////<<configurationManagement2,////Configuration management tool page.

## Admin Accounts

This is the most likely thing to change after you install server and generate default configuration. Actually it is also the easiest option to customize.

And yes, you can just remove entry with admin account: "admin@localhost" unless you really want to keep it. Be aware though all system messages will be sent to ALL admin accounts.

Well, if the account does not exists the message is discarded and a warning is be printed in log file. Again, read it again, the previous sentence…​

It means that the admin account has to be also created in normal way on the Jabber server. Just register it using your Jabber client. The admin accounts setting works just as a forward instruction. So as a result all system and admin messages are forwarded to all admin accounts if they exist.

Obviously you can have as many admin accounts as you like:

    session_1/admins = frank@jabber.example.com, lucy@jabber.example.com,
        mark@jabber.example.com, brenda@jabber.example.com, luck@jabber.example.com

Now, how to do it. First things is to find current settings. To see what are current admin accounts execute the command:

    ./bin/config.sh -c etc/tigase-server.xml -print -key session_1/admins

As a result you can see something like this:

    session_1/admins = admin@yourhost, admin@localhost

As you could read in configuration management too guide '-add' command adds new entries to the list, '-set' command removes old values and sets new one.

As we want to create new admins list for the installation first command would be '-set' command. Let’s say we want set jack@yourhost as your first admin account:

    ./bin/config.sh -c etc/tigase-server.xml -print -key session_1/admins -set -value "jack@yourhost"

As a result program prints new setting:

    session_1/admins = jack@yourhost

All old accounts have been replaced with new account. Now if you wich to add next admin account john@yourhost to the list execute slightly modified command (Note - '-add' instead of '-set'):

    ./bin/config.sh -c etc/tigase-server.xml -print -key session_1/admins -add -value "john@yourhost"

And result:

    session_1/admins = jack@yourhost, john@yourhost

And…​ this is it. You can add more admin accounts the same way.

Prev |  | Next
Chapter 83. Configuration | Home | Hostnames