As of Ultra Messaging Queuing 6.8, some queuing features are deprecated and some UMS features are unavailable to brokered contexts. Also, you cannot use all variations of some features.
Deprecated Features <-
The following UMQ features are deprecated and also unavailable:
-
Source Dissemination
-
Parallel Queue Dissemination
-
Serial Queue Dissemination
-
UMQ Queue Browsing
-
Automatic source resubmission on failover
-
Numeric index IDs for Indexed Queuing
Deprecated Functions and Methods <-
As of UMQ 6.8, the following C API functions are deprecated:
The following Java and .NET API classes and methods are deprecated for Ultra Messaging 6.8 or later:
-
UMEBlockSrc class
-
LBMContext.setUMQInflight() method
-
LBMContext.setUMQMessageStable() method
Unavailable Features <-
Ultra Messaging queuing applications can use some Ultra Messaging functionality, but some functionality is unavailable with Ultra Messaging queuing.
You cannot use Ultra Messaging queuing with the following Ultra Messaging core functionalities:
-
Acceleration - DBL
-
Acceleration - UD
-
Explicit Batching
-
FD Management
-
Hot Failover (HF)
-
Hot Failover Across Contexts (HFX)
-
Implicit Batching
-
Late Join
-
Multicast Immediate Messaging (MIM)
-
Multi-Transport Threads
-
Off-Transport Recovery (OTR)
-
Request and Response
-
Source Side Filtering
-
Spectrum
-
Transports other than type broker
-
Ultra Load Balancing (ULB)
-
Ultra Messaging Desktop Services (UMDS)
-
Ultra Messaging Spectrum
-
Ultra Messaging System Monitoring
-
UMCache
-
UMP stores
-
DRO
-
UM SNMP Agent
-
Ultra Messaging Wildcard Receivers
You cannot use brokered contexts with the following functions or methods:
Limited Ultra Messaging Functionality <-
Use the following rules and guidelines when you use Ultra Messaging queuing with Ultra Messaging core functionalities:
-
When you use queuing, you cannot set configuration option fd_management_type (context).
-
Ultra Messaging queuing systems do not fragment messages.