Release Notes
|
To make UM more maintainable, functionality is sometimes removed from UM. Informatica understands that this can be disruptive to users, so we try to restrict such deprecations to features that, to our knowledge, are not needed by our users.
Informatica recommends careful reading of each version's release notes to learn which features are being deprecated.
If you discover that a feature is deprecated which is important to your use case, please contact Informatica Support.
"Reduced FD" Stores. The Store configuration option repository-type of "reduced-fd" is now deprecated, and will be removed from a future UM version. Users of "reduced-fd" are advised to contact Informatica Support for advice on migrating to repository type "disk".
Store Groups. The Store organization method of creating multiple Q/C groups is deprecated and may be removed from a future release. Users of multiple groups are encouraged to migrate their source configurations to use a single group of Stores for Q/C.
"No Cache" Stores. The Store configuration option repository-type of "no-cache" is now deprecated, and will be removed from a future UM version. Users of "no-cache" are advised to contact Informatica Support for advice on migrating to repository type "disk".
Arrival Order Delivery, No Reassembly Deprecation. The Arrival Order, Fragments Not Reassembled feature (ordered_delivery 0) is still operational but may be removed in a future release.
Users are advised to use Arrival Order, Fragments Reassembled (ordered_delivery -1) instead.
Application Headers Deprecation. The Application Headers feature is still operational but may be removed in a future release.
Users are advised to use Message Properties instead.
UM configuration attribute "application_data" and the corresponding <application-data> XML configuration element. This feature was never fully implemented, and it is now formally deprecated and may be removed in a future release.
As of UM version 6.13, there is a reduction in supported platforms for UM daemons.
The UM daemons are:
Starting with UM version 6.13, the daemons will only be supported on the following platforms:
Daemon | Linux 64 | Windows 64 | Windows 32 |
---|---|---|---|
Persistent Store (stored) | YES | YES | no |
DRO - Dynamic Routing Option (tnwgd) | YES | YES | YES |
Unicast Resolver Daemon (lbmrd) | YES | YES | no |
SRS - Stateful Resolution Service | YES | YES | no |
UMM Ultra Messaging Manager (ummd) | YES | YES | no |
ActiveMQ broker | YES | YES | no |
Platforms not mentioned in the above table are not supported for the UM daemon components, including 32-bit Linux, Solaris, AIX, IBM Power CPUs.
Note that there is no change in support for applications. UM daemons running on the reduced set of platforms will be able to service applications running on the full range of supported platforms.
Starting with UM version 6.13, the UM daemons will no longer be available on certain platforms.
UM daemons will continue to be available on the following platforms:
The planned deprecated daemon platforms are:
User applications deployed on these platforms will fully interoperate with daemons running on the reduced set of platforms.
Please contact support if any of these planned deprecations interfere with your existing or planned deployments.
Adaptive Batching. Adaptive batching is still operational, but planned to be removed in a future release.
Explicit Batching. Explicit Batching is still operational, but planned to be removed in a future release.
Hypertopics. HyperTopics is still operational, but planned to be removed in a future release.
TCP-LB. The "bounded_latency" selection for transport_tcp_multiple_receiver_behavior (source) is still operational, but planned to be removed in a future release.
Java APIs deprecated:
Configuration options deprecated:
<tcp>
' and '<companion>
' will generate errors. Upgrading customers should use <single-tcp> instead.
For Persistent Stores, the '<topic>
' option type value 'regexp
' is deprecated.
The following configuration options are deprecated and no longer function.
The following C API functions are deprecated and no longer function:
The following Java and .NET API functions are deprecated and no longer function:
<regex-pattern>
' configuration option element is deprecated.
The Round-Robin Store failover configuration is deprecated.
repository-disk-max-write-async-cbs
' option is deprecated.
The receiver configuration options retransmit_request_generation_interval (receiver) and otr_request_duration (receiver) have been deprecated. Late join and OTR now track a total duration for each message that begins when a receiver sends the first retransmission request for the message. See retransmit_request_message_timeout (receiver).
Option otr_request_duration (receiver) is deprecated and replaced with the new option otrrequestmessagetimeoutreceiver.
Deprecations for UM versions prior to 6.0.