TIBCO EMS: Destination Features

TIBCO EMS: Destination Features

 

1. You can set a secure mode for access control at the queue or topic level

 

2. You can set threshold limits for the amount of memory used by the EMS

 

 

3. You can route messages sent to destinations to other servers

 

4. You can also create bridges between destinations of the same or different types to create a hybrid messaging model for your application

 

 

5. You can control the flow of messages to a destination

 

6. You can exchange messages with other message services.Queues can receive TIBCO Rendezvous and TIBCO SmartSockets messages. Topics can either receive or send Rendezvous and TIBCO SmartSockets messages

 

 

7. You can set queues to be exclusive or non-exclusive. Only one receiver can receive messages from an exclusive queue

 

8. You can specify a redelivery policy for queues. When messages must be redelivered, you can specify a property on the queue that determines the maximum number of times a message should be redelivered

 

 

9. You can trace and log all messages passing through a destination

 

10. You can include the user name of the message producer in the message with sender_name and sender_name_endorced

 

 

11. Administrator operations can use wildcards in destination names

 

12. You can set the failsafe mode on a topic or queue to direct the server to write persistent messages to disk synchronously to guarantee messages are not lost under any circumstances.

 

 

13. You can specify that a consumer is to receive batches of messages in the background to improve performance

EMS: Setup Fault Tolerance

 

 

 

EMS: Setup Fault Tolerance

 

Here is the summary to setup fault tolerance servers, tcp://ems1:7222 and tcp://ems2:7222 for example,

 

 

1. In server ems1,ems2, change the property server to same values EMS-SERVER for example.

 

b.      In server ems1, change ft_active to tcp://ems2:7222. In server ems2, change ft_active to tcp://ems1:7222. 

 

 

c.      In both servers, set properties ft_heartbeat, ft_actiation, ft_reconnect_timeout in file tibemsd.conf. The values can be different in bot servers.

 

d.      Make sure both servers use the shared configuration files (users.conf, groups.conf and others) except tibemsd.conf and shared state files(meta.db, async-msgs.db,sync-msgs.db). tibemsd.conf should have 2 copies seperately in both servers. In server ems1, setup 2 folders for configuration and shared state files. Copy all configuration files to the configuration folder named Con for example. Copy all shared state files to another one named DataStore for example.

 

e.      In server ems1, ems2, map above folders to a same driver, like Z: for example.

 

f.      In server ems1,ems2, set properties users, groups, topics, queues, acl_list, factories, routs, bridges, transports, tibrvcm, durables like below to let the server know where to get those configuration files.

users   =  Z:/Con/Configureusers.conf

groups = Z:/Con/groups.conf

 

g.      In server ems1, ems2, set properties store value like below

store=Z:/DataStore

Note that above property only specify the folder path

 

h.      In servers ems1,ems2, set the property store_minimum_sync, store_minimum_async  to the same value

 

i.      If authorized property is set enabled, create a TIBCO EMS id/password pairs. The id should be same as the server property value. In this example, create id named EMS-SERVER. And set the password property accordingly in servers ems1, ems2. 

 

j.      Restart TIBCO EMS service in both servers to validate the settings.

 

All properties above can be founder in  tibemsd.conf file.

 

 

祖国生日快乐

祖国生日快乐

 

祝愿我们伟大祖国繁荣昌盛!!!

祝愿我们伟大的民族长盛不衰!!!