You can arrange TIBCO Enterprise Message Service servers for fault-tolerant operation by configuring a pair of servers—one primary and one backup.
The primary server accepts client connections, and interacts with clients to deliver messages.
If the primary server fails, the backup server resumes operation in its place.
Configuring Primary and Backup Servers:
The Server name , Configuration files and data store should same for both the servers.
Configuring Primary Server: Here ft_active represents the back up server listening url.
Server = EMS-SERVER-MSS
Listen = tcp://7222
ft_active = tcp://7666
ft_heartbeat = 3
ft_activation = 600
ft_reconnect_timeout = 90
########################################################################
store = C:\tibco\ems\7.0\datastore
authorization = disabled
password =
stores = C:\tibco\ems\7.0\bin\stores.conf
users = C:\tibco\ems\7.0\bin\users.conf
groups = C:\tibco\ems\7.0\bin\groups.conf
topics = C:\tibco\ems\7.0\bin\topics.conf
queues = C:\tibco\ems\7.0\bin\queues.conf
acl_list = C:\tibco\ems\7.0\bin\acl.conf
factories = C:\tibco\ems\7.0\bin\factories.conf
routes=C:\tibco\ems\7.0\bin\routes.conf
bridges=C:\tibco\ems\7.0\bin\bridges.conf
transports =C:\tibco\ems\7.0\bin\transports.conf
tibrvcm=C:\tibco\ems\7.0\bin\queues.conf
durables=C:\tibco\ems\7.0\bin\durables.conf
Configuring Backup Server: Here ft_active represents the Primary server listening url.
Server = EMS-SERVER-MSS
Listen = tcp://7666
ft_active = tcp://7222
ft_heartbeat = 3
ft_activation = 600
ft_reconnect_timeout = 10000
########################################################################
# Persistent Storage.
#
# store: directory to store persistent messages.
########################################################################
store = C:\tibco\ems\7.0\datastore
stores = C:\tibco\ems\7.0\bin\stores.conf
users = C:\tibco\ems\7.0\bin\users.conf
groups = C:\tibco\ems\7.0\bin\groups.conf
topics = C:\tibco\ems\7.0\bin\topics.conf
queues = C:\tibco\ems\7.0\bin\queues.conf
acl_list = C:\tibco\ems\7.0\bin\acl.conf
factories = C:\tibco\ems\7.0\bin\factories.conf
routes=C:\tibco\ems\7.0\bin\routes.conf
bridges=C:\tibco\ems\7.0\bin\bridges.conf
transports =C:\tibco\ems\7.0\bin\transports.conf
tibrvcm=C:\tibco\ems\7.0\bin\queues.conf
durables=C:\tibco\ems\7.0\bin\durables.conf
Start Both the servers then you will find the following statements in server consoles.
In primary server console window:
Backup server 'EMS-SERVER-MSS@D380D075RG' has connected.
In Backup Server console Window:
Server is in standby mode for 'tcp://7222'.
for cross verification stop the primary server then the backup server will be active means the role is reversed.
The primary server accepts client connections, and interacts with clients to deliver messages.
If the primary server fails, the backup server resumes operation in its place.
Configuring Primary and Backup Servers:
The Server name , Configuration files and data store should same for both the servers.
Configuring Primary Server: Here ft_active represents the back up server listening url.
Server = EMS-SERVER-MSS
Listen = tcp://7222
ft_active = tcp://7666
ft_heartbeat = 3
ft_activation = 600
ft_reconnect_timeout = 90
########################################################################
store = C:\tibco\ems\7.0\datastore
authorization = disabled
password =
stores = C:\tibco\ems\7.0\bin\stores.conf
users = C:\tibco\ems\7.0\bin\users.conf
groups = C:\tibco\ems\7.0\bin\groups.conf
topics = C:\tibco\ems\7.0\bin\topics.conf
queues = C:\tibco\ems\7.0\bin\queues.conf
acl_list = C:\tibco\ems\7.0\bin\acl.conf
factories = C:\tibco\ems\7.0\bin\factories.conf
routes=C:\tibco\ems\7.0\bin\routes.conf
bridges=C:\tibco\ems\7.0\bin\bridges.conf
transports =C:\tibco\ems\7.0\bin\transports.conf
tibrvcm=C:\tibco\ems\7.0\bin\queues.conf
durables=C:\tibco\ems\7.0\bin\durables.conf
Configuring Backup Server: Here ft_active represents the Primary server listening url.
Server = EMS-SERVER-MSS
Listen = tcp://7666
ft_active = tcp://7222
ft_heartbeat = 3
ft_activation = 600
ft_reconnect_timeout = 10000
########################################################################
# Persistent Storage.
#
# store: directory to store persistent messages.
########################################################################
store = C:\tibco\ems\7.0\datastore
stores = C:\tibco\ems\7.0\bin\stores.conf
users = C:\tibco\ems\7.0\bin\users.conf
groups = C:\tibco\ems\7.0\bin\groups.conf
topics = C:\tibco\ems\7.0\bin\topics.conf
queues = C:\tibco\ems\7.0\bin\queues.conf
acl_list = C:\tibco\ems\7.0\bin\acl.conf
factories = C:\tibco\ems\7.0\bin\factories.conf
routes=C:\tibco\ems\7.0\bin\routes.conf
bridges=C:\tibco\ems\7.0\bin\bridges.conf
transports =C:\tibco\ems\7.0\bin\transports.conf
tibrvcm=C:\tibco\ems\7.0\bin\queues.conf
durables=C:\tibco\ems\7.0\bin\durables.conf
Start Both the servers then you will find the following statements in server consoles.
In primary server console window:
Backup server 'EMS-SERVER-MSS@D380D075RG' has connected.
In Backup Server console Window:
Server is in standby mode for 'tcp://7222'.
for cross verification stop the primary server then the backup server will be active means the role is reversed.
Tibco implementation process has become easy and the issues associated with it are cleared with the help of the content provided in very few websites like this.
ReplyDelete