Version 7.0 of WebLogic Server provides several features that make it easier to integrate with foreign JMS providers.
WebLogic Messaging Bridge
The WebLogic Messaging Bridge is a part of WebLogic Server that forwards messages from a “source” destination to a “target” destination. Out-of-the-box adapters are provided so that the source and/or target may be a JMS destination. Either end can be a JMS topic or queue, and could be a server running WebLogic Server 5.1 or higher, or a foreign JMS provider. The WebLogic Messaging Bridge also provides interoperability between different versions of WebLogic Server. The WebLogic Messaging Bridge supports two-phase commit transactions using XA for JMS providers that support it, and one-phase commit transactions for providers that do not.
Container-Managed Transactions for Message-Driven Beans
A message-driven bean (MDB) is a special type of Enterprise Java Bean (EJB) that pulls mes-sages from a JMS queue or topic. The EJB container (WebLogic Server) is responsible for connecting to the JMS provider, receiving messages, and passing them to the MDB in the proper transaction context. This allows asynchronous events to be processed by a J2EE-based applica-tion, which was not possible in a standard way before MDBs.. WebLogic Server has supported MDBs since WebLogic Server 6.0. Version 6.0 SP1 of the server added support for foreign JMS providers. However, container-managed transactions could only be used with WebLogic JMS, so a foreign JMS provider could not participate in the WebLogic transaction. WebLogic Server 7.0 allows foreign JMS providers to participate in a WebLogic transaction. If the MDB is set up to support container-managed transactions, and if the JMS provider is config-ured to support XA, then WebLogic Server will use XA to include the JMS provider in the overall WebLogic transaction. This way, it is possible to deploy an MDB that supports “Exactly-once” transactional guarantees, thereby ensuring that each message will be processed once and only once.
WebLogic Messaging Bridge
The WebLogic Messaging Bridge is a part of WebLogic Server that forwards messages from a “source” destination to a “target” destination. Out-of-the-box adapters are provided so that the source and/or target may be a JMS destination. Either end can be a JMS topic or queue, and could be a server running WebLogic Server 5.1 or higher, or a foreign JMS provider. The WebLogic Messaging Bridge also provides interoperability between different versions of WebLogic Server. The WebLogic Messaging Bridge supports two-phase commit transactions using XA for JMS providers that support it, and one-phase commit transactions for providers that do not.
Container-Managed Transactions for Message-Driven Beans
A message-driven bean (MDB) is a special type of Enterprise Java Bean (EJB) that pulls mes-sages from a JMS queue or topic. The EJB container (WebLogic Server) is responsible for connecting to the JMS provider, receiving messages, and passing them to the MDB in the proper transaction context. This allows asynchronous events to be processed by a J2EE-based applica-tion, which was not possible in a standard way before MDBs.. WebLogic Server has supported MDBs since WebLogic Server 6.0. Version 6.0 SP1 of the server added support for foreign JMS providers. However, container-managed transactions could only be used with WebLogic JMS, so a foreign JMS provider could not participate in the WebLogic transaction. WebLogic Server 7.0 allows foreign JMS providers to participate in a WebLogic transaction. If the MDB is set up to support container-managed transactions, and if the JMS provider is config-ured to support XA, then WebLogic Server will use XA to include the JMS provider in the overall WebLogic transaction. This way, it is possible to deploy an MDB that supports “Exactly-once” transactional guarantees, thereby ensuring that each message will be processed once and only once.
No comments:
Post a Comment