A customer is developing a custom application that involves a multistep provisioning process for a new account. There is a custom Java client application that is generating multiple JMS messages as…

Question

Options

• AUpdate the client application that is creating the JMS messages to use Unit of Work.
• BConfigure a WebLogic Cluster for Distributed JMS.
• CUpdate the client application that is creating the JMS messages to use Unit of Order.
• DEnable XA Transactions on the JMS Connection Factory used by the client application.
• EEnable Load Balancing on the JMS connection factory used by the client application.

• A
  11% (4)
• B
  56% (20)
• E
  33% (12)

Explanation

C: Message UnitofOrder is a WebLogic Server valueadded feature that enables a standalone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a UnitofOrder and requires that all messages from that unit be processed sequentially in the order they were created. D Transactions required for parallel processing. A: Many applications need an even more restricted notion of a group than provided by the Message UnitofOrder (UOO) feature. If this is the case for your applications, WebLogic JMS provides the UnitofWork (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, an JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete. * WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names: weblogic.jms.ConnectionFactory weblogic.jms.XAConnectionFactory

No community discussion yet for this question.