tigase集群配置搭建官方方法-xmpp通讯协议配备tigase集群开发简单省事-哇谷即时通讯IM源码服务

Server(c2s+s2s+sm+ext2s)集群+MUC(comp)集群

Server1(hostname: vm-128-157)配置

--debug = server,cluster,xmpp.impl
--virt-hosts = xmpp.dev.pajkdc.com
--user-db-uri = jdbc:mysql://10.0.128.115:3307/tigase?user=pajk&password=qawsed123
--user-db = mysql
--admins = admin@xmpp.dev.pajkdc.com
config-type = --gen-config-def
--cluster-mode = true
--cluster-connect-all = true
--cluster-nodes=vm-128-157:yangguo:5277,vm-128-158:yangguo:5277
--sm-plugins =-starttls,+urn:ietf:params:xml:ns:messageConsumeACK,+urn:ietf:params:xml:ns:xmpp-user,-message-archive-xep-0136,-jabber:iq:register,-presence,-http://jabber.org/protocol/stats,-vcard-temp,-jabber:iq:roster,-pep
--comp-name-1 = ext
--comp-class-1 = tigase.server.ext.ComponentProtocol
--external = muc.xmpp.dev.pajkdc.com:yangguo:listen:5270:vm-128-157:accept:ReceiverBareJidLB
--auth-domain-repo-pool=com.pajk.im.repository.ExtraAuthRepositoryMDImpl
--user-domain-repo-pool=com.pajk.im.repository.ExtraUserRepositoryMDImpl
--comp-name-2 = ChannelMsgExtComponent
--comp-class-2 = com.pajk.im.cmp.ChannelMsgExtComponent
--cm-ht-traffic-throttling = xmpp:250k:0:disc,bin:1024m:0:disc
--cm-traffic-throttling=xmpp:2500:0:disc,bin:10m:0:disc
--new-connections-throttling=5222:500,5223:50,5269:100,5280:1000,5290:100
--net-buff-high-throughput=256k

Server2(hostname: vm-128-158)配置

--debug = server,cluster,xmpp.impl
--virt-hosts = xmpp.dev.pajkdc.com
--user-db-uri = jdbc:mysql://10.0.128.115:3307/tigase?user=pajk&password=qawsed123
--user-db = mysql
--admins = admin@xmpp.dev.pajkdc.com
config-type = --gen-config-def
--cluster-mode = true
--cluster-connect-all = true
--cluster-nodes=vm-128-157:yangguo:5277,vm-128-158:yangguo:5277
--sm-plugins =-starttls,+urn:ietf:params:xml:ns:messageConsumeACK,+urn:ietf:params:xml:ns:xmpp-user,-message-archive-xep-0136,-jabber:iq:register,-presence,-http://jabber.org/protocol/stats,-vcard-temp,-jabber:iq:roster,-pep
--comp-name-1 = ext
--comp-class-1 = tigase.server.ext.ComponentProtocol
--external = muc.xmpp.dev.pajkdc.com:yangguo:listen:5270:vm-128-158:accept:ReceiverBareJidLB
--auth-domain-repo-pool=com.pajk.im.repository.ExtraAuthRepositoryMDImpl
--user-domain-repo-pool=com.pajk.im.repository.ExtraUserRepositoryMDImpl
--comp-name-2 = ChannelMsgExtComponent
--comp-class-2 = com.pajk.im.cmp.ChannelMsgExtComponent
--cm-ht-traffic-throttling = xmpp:250k:0:disc,bin:1024m:0:disc
--cm-traffic-throttling=xmpp:2500:0:disc,bin:10m:0:disc
--new-connections-throttling=5222:500,5223:50,5269:100,5280:1000,5290:100
--net-buff-high-throughput=256k

muc1配置

config-type = --gen-config-comp
--user-db = mysql
--admins = admin@xmpp.dev.pajkdc.com
--user-db-uri = jdbc:mysql://10.0.128.115:3307/tigase?user=pajk&password=qawsed123
--virt-hosts = xmpp.dev.pajkdc.com
--comp-name-1 = muc
--debug = server
--comp-class-1 = tigase.muc.MUCComponent
--external = muc.xmpp.dev.pajkdc.com:yangguo:connect:5270:xmpp.dev.pajkdc.com;vm-128-157;vm-128-158:accept

muc2配置

config-type = --gen-config-comp
--user-db = mysql
--admins = admin@xmpp.dev.pajkdc.com
--user-db-uri = jdbc:mysql://10.0.128.115:3307/tigase?user=pajk&password=qawsed123
--virt-hosts = xmpp.dev.pajkdc.com
--comp-name-1 = muc
--debug = server
--comp-class-1 = tigase.muc.MUCComponent
--external = muc.xmpp.dev.pajkdc.com:yangguo:connect:5270:xmpp.dev.pajkdc.com;vm-128-157;vm-128-158:accept

Tigase MUC思路(引用于Tigase作者Kobit)

As far as I know there is no such thing like a persistent member of the MUC room. This is not a part of the protocol hence it is not implemented anywhere. Even if we had created something like that in our MUC server it would not work with any XMPP client. The whole idea behind MUC is to allow for communication between ONLINE users. Therefore, once the user logs off it is removed from the MUC. However, most of the XMPP clients have a feature to save a MUC bookmark and automatically join the room after login to the XMPP Server. The MUC room has quite extensive configuration settings, you can list users who are allowed to join the room, you can make the room password protected, you can assign different roles to different users. All of this is supported by our MUC.

注意事项:上面的配置，由于是一个完整的分布式环境，所以特别需要注意网络状况。特别是在server端开启本地端口，监听外部component服务链接的时候。尤其是使用无线网络的笔记本电脑，有时候无线网络会导致里面的java代码不能绑定本地端口的情况。面对这种情况，请大家将无线网络断开重连。

Tigase XMPP Server configuration properties

sm-plugin说明

标准错误代码

扩展code(XMPPErrorCodeExtension枚举)，如果大家定义了，请加在此处。 ERROR_TH(4031, "cancel", "登陆过于频繁或者流量过大")

MUC相关技术

• XEP-0004: 数据表单，用来交换数据。

CS和SM分离

• tigase中是可行的，但是目前架构没有这样做。这样做会增加网络开销，目前此方案，不是很好，待尝试。

使用到得XEP

• XEP-0184: Message Delivery Receipts，该扩展对server没有任何要求，只要client端支持就行。
• XEP-0004:表单数据，用来交换数据，form类型[http://xmpp.org/registrar/formtypes.html]
• XEP-0198:server端的消息确认，tigase中的配置，它的存在的意义在http://op-co.de/blog/posts/XEP-0198中已经描述的非常详细。
• XEP-199
• XEP-0114:Jabber组件协议

群聊室的属性

我们设计的群已经不是标准的xmpp群了，下面的属性是对于smack或者标准的xmpp群有意义的。

• 房间名称|muc#roomconfig_roomname
• 描述|muc#roomconfig_roomdesc
• 允许占有者更改主题|muc#roomconfig_changesubject
• 最大房间占有者人数|muc#roomconfig_maxusers
• 其 Presence 是 Broadcast 的角色|muc#roomconfig_presencebroadcast
• 列出目录中的房间|muc#roomconfig_publicroom
• 房间是持久的|muc#roomconfig_persistentroom
• 房间是适度的|muc#roomconfig_moderatedroom
• 房间仅对成员开放|muc#roomconfig_membersonly
• 允许占有者邀请其他人|muc#roomconfig_allowinvites
• 需要密码才能进入房间|muc#roomconfig_passwordprotectedroom
• 密码|muc#roomconfig_roomsecret
• 能够发现占有者真实 JID 的角色|muc#roomconfig_whois
• 登录房间对话|muc#roomconfig_enablelogging
• 仅允许注册的昵称登录|x-muc#roomconfig_reservednick
• 允许使用者修改昵称|x-muc#roomconfig_canchangenick
• 允许用户注册房间|x-muc#roomconfig_registration
• 房间管理员|muc#roomconfig_roomadmins
• 房间拥有者|muc#roomconfig_roomowners

哇谷工作台  哇谷云     哇谷科技    即时通讯     IM下载    IM功能与价格