More Components
Prev | Chapter 61. Tigase as External Component | Next

## More Components

Suppose you want to run more components as external components within one Tigase instance. Let’s add another - PubSub component to the configuration above and see how to set it up.

The way which seems to be most straightforward is just to add another component and another connection to the main server for the component domain:

    config-type = --gen-config-comp
    --debug = server
    --user-db = derby
    --admins = admin@devel.tigase.org
    --user-db-uri = jdbc:derby:/tigasedb
    --virt-hosts = devel.tigase.org
    --comp-name-1 = muc
    --comp-class-1 = tigase.muc.MUCComponent
    --comp-name-2 = pubsub
    --comp-class-2 = tigase.pubsub.PubSubComponent
    --external = muc.devel.tigase.org:muc-pass:connect:5270:devel.tigase.org:accept, \
      pubsub.devel.tigase.org:pubsub-pass:connect:5270:devel.tigase.org:accept

Please note however that we are opening two connections to the same server. This is kind of wasting resources and overcomplicating system. What if we want to run even more components? Opening a separate connection for each component seems to be an overkill.

In fact there is a way to reuse the connection for all component domains running as an external component. The property '--bind-ext-hostnames' contains a comma separated list of all hostnames (external domains) which should reuse the existing connection.

There is one catch however. Connection reusing (hostname binding is defined in XEP-0225 only, hence you must use this protocol for the functionality.

Here is an example configuration with a single connection over XEP-0225 protocol used by both external domains:

    config-type = --gen-config-comp
    --debug = server
    --user-db = derby
    --admins = admin@devel.tigase.org
    --user-db-uri = jdbc:derby:/tigasedb
    --virt-hosts = devel.tigase.org
    --comp-name-1 = muc
    --comp-class-1 = tigase.muc.MUCComponent
    --comp-name-2 = pubsub
    --comp-class-2 = tigase.pubsub.PubSubComponent
    --external = muc.devel.tigase.org:muc-pass:connect:5270:devel.tigase.org:client
    --bind-ext-hostnames=pubsub.devel.tigase.org

Prev | Up | Next
Chapter 61. Tigase as External Component | Home | Chapter 62. Load Balancing External Components in Cluster Mode