TIBCO EMS FAQ -2

-
1)       What are the different types of acknowledgement modes in EMS message delivery?

Ans) Auto, Client, Dups_ok, No_ack, Explciit, Explicit_client_dups_ok, Transitional and Local transitional.

2)      What are the different types of messages that can be used in EMS
Ans) Text , Simple, Bytes, Map, XML test, Object, Object ref and Stream.

3)       Tell me about bridges. Why do we use them, Syntax to create bridges, use of message selector?

Ans)  Some applications require the same message to be sent to more than one destination possibly of different types. So we use bridges.

4)      What is the purpose for stores.conf?
Ans) a. This file defines the locations either store files or a database, where the EMS server will store messages or metadata.
b. Each store configured is either a file-based or a database store.

5)       How many modes are the messages written to store file?
2 modes.. sync or async. When absent, the default is async.

6)       What is tibemsd.conf?
Ans) It is the main configuration file that controls the characteristics of the EMS server.

7)       How many delivery modes for messages?
Ans) Persistent, Non-persistent, Reliable-delivery.

8)       What is the maximum message size?
Ans) Ems supports max message size of 512 mb.

9)       Name 3 destination properties and explain them?
Ans) Global, secure, maxmsgs, maxbytes, flowcontrol, sender_name, sender_name_enforced, trace,maxRedelivery.

10)    What are the different modes of installation in Ems?
Ans) a. GUI mode
b. Console mode
c. Silent mode.

11)  What are the messaging models supported by JMS?
Ans) a. Point-to-point
b. Publish-subscribe
c. Multicast.

12)   Tell me about routes? What is the purpose of routes, what kind of destinations can be used in routes?

Ans) Topics and queues m-hops.

13)   What happens if the message expires/exceeded the value specified by maxredelivery property on queue?
If the jms_preserve_undelivered property is set to true, then it moves he message to undelivered message queue, if set to false, the message is deleted by the server.

14)   In how many ways can a destination be created?
Ans) a. Static-created by user
        b. Dynamic-created by ems server on the fly.
        c. Temporary destinations.

 

 

 

15)   What are the wild cards that we use in ems?how do they work for queues and topics?
Ans) *,>
U can subscribe to wildcard topics but can’t publish to them. Where as in case of queues we can’t either send /receive.

16)   Are bridges transitive?
Ans) NO.

17)   Tell me about flow control on destinations?
Ans) sometimes the producer may send messages faster than the consumers can receive them. So, the message capacity on the server will be exhausted. So we use flow control. Flow control can be specified on destinations.

18)   Tell me about flow control on bridges and routes?
Ans) Flow control has to be specified on both sides of bridges where as on routes it operates differently on sender side and receiver side.

19)   Name 3 configuration files and tell me what it consists of?
Ans) a. Queues.conf
         b. Topics.conf
         c. Routes.conf
         d. Factories.conf
          e. Stores.conf
          f. Groups.conf,users.conf,transports.conf.

20)   Name some administrative level destination properties?
Ans) a. View
        b. Create
       c. Delete
       d. Modify
       e. Purge.

21)   How can you change the configuration properties of EMS server?
Ans) You can change in the tibemsd.conf file or you can change using the ems admin console.

22)   What are the permissions that you can grant to users to access queues?
Ans) a. Receive
         b. Send
         c. Browse.

23)   What are the permissions that you can grant to users to access topics?
Ans) a. Subscribe
         b. Publish
         c. Durable
         d. Use_durable.

24)   Tell me about multicasting in EMS?
Ans) a. Multicast is a messaging model that broadcasts messages to many consumers at once rather than sending messages individually to each consumer. EMS uses Pragmatic general multicast to broadcast messages published to multicast enabled topics. b. Each multicast enabled topic is associated with a channel.

25)   What are the advantages and disadvantages of multicasting?
Ans) a. Advantages: as the message broadcasts only once thereby reducing the amount of bandwidth used in publish and subscribe model. Reduces the network traffic.
b. Disadvantages: Offers only last-hop delivery. So can’t be used to send messages between servers.

26)   On what destinations can you use multicast?
Ans) a. Topics.

27)   Suppose, you got an error while accessing a queue, that you don’t have necessary permissions to access the queue. What might be the solution/reason?
Ans) a. The user that is assigned to the queue and the user used while creating.

28)   How does the secondary server know that the primary server is failed?
Ans) a. Based on heartbeat intervals

29)   What is JMS queue requestor?
Ans) a. The JMS Queue Requestor activity is used to send a request to a JMS queue name and receive a response back from the JMS client.

30)   What is JMS topic requestor?
Ans) a. The JMS Topic Requestor activity is used to communicate with a JMS application’s request-response service. This service invokes an operation with input and output. The request is sent to a JMS topic and the JMS application returns the response to the request.

Comments

Post a Comment

Popular posts from this blog

TIBCO EMS FAQ -5

-
131) What happens if the message expires/exceeded the value specified by maxredelivery property on queue? If the jms_preserve_undelivered property is set to true, then it moves he message to undelivered message queue, if set to false, the message is deleted by the server. 132) What are the wild cards that we use in ems?how do they work for queues and topics? *,> We can subscribe to wildcard topics, but cant publish to them. Where as in case of queues we can’t either send /receive. 133) Are bridges transitive? No 134) Tell me about flow control on destinations? Sometimes the producer may send messages faster than the consumers can receive them. So, the message capacity on the server will be exhausted. So we use flow control. Flow control can be specified on destinations. 135) Tell me about flow control on bridges and routes? Flow control has to be specified on both sides of bridges where as on routes it operates differently on sender side and receiver side. 136) Nam...
Read more

TIBCO EMS FAQ -4

-
101) What are the permissions that you can grant to users to access topics? a. Subscribe b. Publish c. Durable d. Use durable 102) What is the difference between Queues and Topics? Queue • Guaranteed Service • Only the Target gets the message (One message per Consumer) • Uses Peer-to-Peer Mode to deliver messages • Blocking • Load Balancing is possible Topic • Reliable Service • Everyone active gets the message (One message may Consumers) • Uses Pub / Sub mode to deliver messages • Non-Blocking • Load Balancing is not possible. 103) What is the use of secured queues and topics? Setting ‘secure’ property to queues/topics can restrict unauthorized users from publishing/sending and subscribing/receiving the messages. 104) What are acknowledgement modes and where do you set them and what is the applicability of each mode? Ans:The acknowledge mode for incoming messages. Can be one of the following: • Auto — the message is automatically acknowledged when it is re...
Read more

TIBCO BW FAQ -2

-
31) What happens if you use check point activity first and confirm next? Ans)In the case of confirmable messages , you must consider the consequences of performing a checkpoint before or after a Confirm activity. If the checkpoint is taken before the Confirm activity, then a crash occurs after a checkpoint but before a confirm, the original message is resent. In this case, the restarted process can no longer send the confirmation. However, a new process is started to handle the resent message, and you can implement your process to handle the restarted and new processes appropriately. If the checkpoint is taken after a Confirm activity, there is potential for a crash to occur after the Confirm but before the checkpoint. In this case, the message is confirmed and therefore not redelivered. The process instance is not restarted, because the crash occurred before the checkpoint. You must consider the type of processing your process definition performs to determine when a checkpoint i...
Read more