Tigase Push Component - FCM provider Configuration - How to install?

Gabriele Mendi
Added over 1 year ago

Hi folks,

anyone can point me to a guide, how to or documentation on how to install and configurare the Push component, in particular pointing to the FCM provider?

I only saw this links online but they assume a lot of knowledge I don't have.

I would need something starting a bit "earlier" ...

Thanks in advance!



Replies (8)

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Hello Gabriele.

Do you have an FCM server setup that you want the push component to connect too? If so, you would add the following to your configuration:

push () {
    'fcm-xmpp-api' () {
        'sender-id' = 'your-sender-id'
        'server-key' = 'your-server-key'

If you are looking to setup FCM hosting, google has some technical documents for that here:

Hope that helps!


Added by Gabriele Mendi over 1 year ago

Hi Dan,

first of all, thanks for your kind reply. :)

I am thinking to use Firebase without a server installation, and I am wondering now if it's possible to do so, putting the sender key and server key I found in the Firebase console.

I only installed twice Tigase, and honestly I have no idea where I should put the piece of text you wrote.

I configured everything in my installation with the and everything works nicely.

Where this "push ()" should be configured?

I didn't find a single document describing it... :(



Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

The push statement can go pretty much anywhere in the file, there's no real required order for components so anywhere will do. Just be sure that it's not under any brackets for other components.

For example:

'sess-man' () {
     amp ()
     jabber:iq:offline ()
push () {
     'sender-id' = ''

Added by Gabriele Mendi over 1 year ago

Wow, so something like that would be acceptable?

There is some documents describing ho to configure in detail?

Thanks a lot


--comp-class-1 = tigase.muc.MUCComponent
--virt-hosts =
--user-db-uri = jdbc:jtds:sqlserver://localhost:4850;databaseName=tigasedb;user=tigase;password=ViaSpezia91;schema=dbo;lastUpdateCount=false;cacheMetaData=false
--user-db = sqlserver
--admins =,
--comp-name-5 = message-archive
--comp-name-4 = rest
--comp-name-3 = proxy
config-type = --gen-config-all
--comp-name-2 = pubsub
--comp-name-1 = muc
--comp-class-6 = tigase.server.websocket.WebSocketClientConnectionManager
--comp-name-6 = ws2s
ws2s/connections/ports[i] = 5290,5291
ws2s/connections/5291/socket = ssl
ws2s/connections/5291/type = accept
--cluster-mode = false
--sm-plugins = +message-archive-xep-0136,+jabber:iq:auth,+urn:ietf:params:xml:ns:xmpp-sasl,+urn:ietf:params:xml:ns:xmpp-bind,+urn:ietf:params:xml:ns:xmpp-session,+jabber:iq:register,+jabber:iq:roster,+presence,+jabber:iq:privacy,+jabber:iq:version,+,+starttls,+msgoffline,+vcard-temp,+,+jabber:iq:private,+urn:xmpp:ping,+basic-filter,+domain-filter,+pep,-zlib
--debug = server
--comp-class-5 = tigase.archive.MessageArchiveComponent
--comp-class-4 =
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-2 = tigase.pubsub.PubSubComponent
--vhost-anonymous-enabled = false
bosh/connections/ports[i] = 5290,5291
bosh/connections/5281/socket = ssl
bosh/connections/5281/type = accept
push () {
     'sender-id' = 'xxxxxx'

Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Oh, it looks like you're still using v7.1.0. Push component is only available on v7.2.0 which is available on nightly builds. Version 7.2.0 uses DSL style configuration which would change the whole layout of your configuration file.

should help you upgrade a test environment. Just note that 7.2.0 is still being worked on.

Added by Gabriele Mendi over 1 year ago

Ahhh, thank you!

That finally makes sense!

Well, now the dilemma is if I should upgrade to 7.2 or not, while it is still in development....

Any experience on 7.2?????

Ciao and thanks


Added by Daniel Wisnewski IoT 1 Cloud over 1 year ago

Most of the major developments are done, we're just catching bugs and fixing them. Can it run stable? well our own servers are getting upgraded and they've worked pretty well. So we're pretty far into development on it, and it's pretty stable now.

Added by Gabriele Mendi over 1 year ago

Hi Daniel,

thanks for the precious feedback.

I guess for me it's time to start trying the 7.2.

Thanks, for now... but I fear I will need a lot of extra help!