5. Configuration

To enable Tigase Unified Archive Component you need to add following block to etc/init.properties file:

unified-archive () {
}

It will enable component and configure it under name unified-archive. By default it will also use database configured as default data source to store data.

Due to fact that Tigase Unified Archive component is extended version of Tigase Message Archiving component it shares configuration properties.

Every configuration property of message-archive component may be set to unified-archive component. In same way every configuration property of message-archive processor may be set to unified-archive processor.

5.1. Support for XEP-0136

To be able to use Unified Archive component with XEP-0136: Message Archiving protocol, you additionally need to enable unified-message-archive-xep-0136 SessionManager processor:

sess-man {
    unified-message-archive-xep-0136 () {
    }
}

5.2. Enabling Jingle call archive

To enable archiving of Jingle calls you need to enable jingle-archive SessionManager processor:

sess-man {
    jingle-archive () {
    }
}

Additionally you may want to replace urn:xmpp:jingle:1 XMLNS in entries stored in Unified Archive. For that you need to set omitJingleXMLNS of jingle-archive processor to true.

If you want to archive also Jingle requests incoming by <message/> stanzas you need to set archiveJingleMessage of jingle-archive processor to true.

5.2.1. Example

In this example we are enabling processor and all it’s options.

sess-man {
    jingle-archive () {
        omitJingleXMLNS = true
        archiveJingleMessage = true
    }
}

5.3. Enabling login history

To enable archiving of login/logout events you need to enable login-history SessionManager processor:

sess-man {
    login-history () {
    }
}