1-8 Configuring and Managing JMS for Oracle WebLogic Server
■
Reliable Web Services integration with JMS as a transport, as described in Using Web Services Reliable Messaging in Programming Advanced Features of JAX-RPC
Web Services for Oracle WebLogic Server.
■
Automatic transaction enlistment of non-WebLogic JMS client resources in server-side applications via JMS resource-reference pooling. See Enhanced Java
EE Support for Using WebLogic JMS With EJBs and Servlets in Programming JMS for Oracle WebLogic Server.
■
Integration with Oracle Tuxedo messaging provided by WebLogic Tuxedo Connector. See How to Configure the Oracle Tuxedo Queuing Bridge in the
WebLogic Tuxedo Connector Administration Guide for Oracle WebLogic Server.
■
The WebLogic JMS C API enables programs written in C to participate in JMS applications. This implementation of the JMS C API uses JNI in order to access a
Java Virtual Machine JVM. See WebLogic JMS C API in Programming JMS for Oracle WebLogic Server.
■
Oracle Streams Advanced Queuing AQ provides database-integrated message queuing functionality that leverages the functions of the Oracle database to
manage messages. WebLogic Server interoperates with Oracle AQ using a Foreign JMS and JDBC data source configuration in a WebLogic Server domain. Both local
and remote JMS clients can use Oracle AQ destinations from WebLogic JNDI. See
Chapter 7, Interoperating with Oracle AQ JMS.
1.6 New and Changed JMS Features
This section includes new and changed features for recent patch sets of WebLogic Server:
■
Section 1.6.1, WebLogic Server 10.3.4.0 New and Changed Features
■
Section 1.6.2, WebLogic Server 10.3.3.0 New and Changed Features
■
Section 1.6.3, WebLogic Server 10.3.2.0 New and Changed Features For a comprehensive listing of the new WebLogic Server features introduced in this
release, see What’s New in Oracle WebLogic Server.
1.6.1 WebLogic Server 10.3.4.0 New and Changed Features
This release includes the following new and changed features:
■
Weighted Distributed Destinations are deprecated in WebLogic Server 10.3.4.0. Oracle recommends using Uniform Distributed Destinations.
■
Partitioned Distributed Topics provide the ability to load balance messages to members which provides a highly scalable and available publishing mechanism.
See Section 4.5.2.4, Configuring Partitioned Distributed Topics.
■
Unrestricted Client ID Policy allows more than one JMS connection can use the same Client ID. See
Section 4.6, Configure an Unrestricted ClientID.
■
Shared Subscriptions allow multiple subscribers to share the same subscription which enables parallel processing of messages of a single subscription. See
Section 4.7, Configure Shared Subscriptions.
■
New Message-Driven Bean MDB activation configuration properties, configuration permutations, and the deployment actions that provide high
availability and parallel processing. See Configuring and Deploying MDBs Using
Introduction and Roadmap 1-9
Distributed Topics in Programming Message-Driven Beans for Oracle WebLogic Server.
1.6.2 WebLogic Server 10.3.3.0 New and Changed Features
This release includes the following new and changed features:
■
The following internal methods of weblogic.jms.extensions.WLMessage have been included in Oracles public documentation, but have been removed:
– public void setSAFSequenceNameString safSequenceName;
– public String getSAFSequenceName;
– public void setSAFSeqNumberlong seqNumber;
– public long getSAFSeqNumber;
Your applications should not use these internal methods. Internal methods may change or be removed in a future release without notice.
■
The JMSDestinationAvailabilityHelper API provides a means for getting notifications when destinations become available or unavailable. These APIs are
for advanced use cases only. Use this helper only when standard approaches for solving WebLogic distributed consumer problems have been exhausted. See
Using the JMS Destination Availability Helper APIs with Distributed Queues in Programming JMS for Oracle WebLogic Server.
1.6.3 WebLogic Server 10.3.2.0 New and Changed Features
