Release Notes

Deprecations

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. Typically the depreciation is announced prior to the functionality being removed to give users time to replace the deprecated functionality with the recommended replacement.

Informatica recommends careful reading of each version's release notes to learn which features are being deprecated. If you are upgrading across multiple versions of UM, the deprecations for all intervening versions should be examined.

If you discover that a feature is deprecated which is important to your use case, please contact UM Support.

# Deprecations for 6.17 <-

- UMM. Ultra Messaging Manager is a component that provides a graphical user interface for creating and maintaining UM library configuration files. Due to lack of demand, it is deprecated as of UM version 6.17, and will be removed in a future version. Users of UMM should contact UM Support.

# Deprecations for 6.16 <-

- 32-bit. Support for 32-bit applications and daemons is dropped. See Eliminate 32-bit.

# Deprecations for 6.15 <-

- UN-DEPRECATED: Store Groups. UM version 6.13 announced the deprecation of Store Groups. This decision has been reversed. Store groups will continue to be fully supported into the future.

- REMOVED: "Reduced FD" Store. In UM version 6.13.1, we announced deprecation of the "Reduced FD" Store. In version 6.15 the reduced FD functionality has been removed from the Store. This included the removal of the LevelDB database code from the Store.

- DEPRECATED: Daemon Monitoring Formats. The binary daemon monitoring formats for the Store and DRO are deprecated. The JSON daemon monitoring format for the SRS is deprecated.

  We currently do not plan to remove these deprecated formats, but new monitoring features will not be added to them.

  Informatica recommends transitioning to the "protocol buffer" format for Store, DRO, and SRS. See Monitoring Formats.

# Deprecations for 6.14 <-

- DEPRECATED: "HFX" feature. This is a heavier-weight version of Hot Failover in which multiple contexts are used to receive the duplicated data streams. This provides greater flexibility on selecting different network interfaces to carry the data.

  The feature turned out not to be of interest to our customers. If you use this feature, please contact UM Support.

  See Hot Failover Across Multiple Contexts (HFX).

- DEPRECATED: Enabling daemon statistics on Store and DRO using "<daemon-monitor>". The C-style binary structures format of Store and DRO daemon statistics are enabled with the "<daemon-monitor>" element.

  Informatica requests users to migrate to using the UM configuration file to enable automatic monitoring with Protocol Buffer monitoring format for Store and DRO by setting monitor_format (context) to "pb".

  See Monitoring UM Daemons.

- DEPRECATED: Monitoring Format CSV. Prior to UM version 6.14, the only monitoring formatter available was CSV (comma-separated values).

  Starting in UM 6.14, CSV is deprecated in favor of proto buffs. We do not plan to remove existing CSV functionality, and we will continue to support it in its current state. But we do not plan to enhance CSV in the future.

  To take advantage of new monitoring capabilities, Informatica requests that users migrate to proto buffs.

  See Monitoring Formats.

- DEPRECATED: Monitoring transports UDP and SNMP.

  Starting in UM 6.14, monitoring transports UDP and SNMP are deprecated in favor of LBM. We do not plan to remove existing UDP or SNMP functionality, and will continue to support them in their current states. But we do not plan to enhance UDP or SNMP in the future.

  To take advantage of new monitoring capabilities, Informatica requests that users migrate to the LBM transport.

- DEPRECATED: SNMP Monitoring Agent.

  Starting in UM 6.14, the SNMP Monitoring Agent is deprecated in favor of MCS. We do not plan to remove existing SNMP agent functionality, and will continue to support it in its current state. But we do not plan to enhance the SNMP agent in the future.

  To take advantage of new monitoring capabilities, Informatica requests that users migrate to Monitoring Collector Service (MCS).

- DEPRECATED: Store web monitor.

  Starting in UM 6.14, the Store Web Monitor is deprecated in favor of MCS. We do not plan to remove existing web monitor functionality, and will continue to support it in its current state. But we do not plan to enhance the web monitor in the future.

  To take advantage of new monitoring capabilities, Informatica requests that users migrate to Monitoring Collector Service (MCS).

- DEPRECATED: DRO web monitor.

  Starting in UM 6.14, the DRO Web Monitor is deprecated in favor of MCS. We do not plan to remove existing web monitor functionality, and will continue to support it in its current state. But we do not plan to enhance the web monitor in the future.

  To take advantage of new monitoring capabilities, Informatica requests that users migrate to Monitoring Collector Service (MCS).

# Deprecations for 6.13.1 <-

- DEPRECATED: "Datagram Acceleration" feature. This is a little-known (barely documented) experimental feature offered to a few customers. The feature turned out not to be of interest to our customers. See datagram_acceleration_functions (context).

# Deprecations for 6.13 <-

- DEPRECATED: "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 UM Support for advice on migrating to repository type "disk".

- NOT DEPRECATED: Store Groups. UM version 6.13 included a deprecation announcement of multiple Q/C groups. This feature was un-deprecated in 6.15 and will be fully supported in future releases. (At no time was the functionality removed or disabled.)

- DEPRECATED: "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 UM Support for advice on migrating to repository type "disk".

- DEPRECATED: 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.

- DEPRECATED: 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.

- DEPRECATED: 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.

## Platform Deprecations for Daemons <-

Starting with UM version 6.16, no 32-bit components are supported. See Eliminate 32-bit.

Starting with UM version 6.13, there is a reduction in supported platforms for UM daemons.

The UM daemons are:

- Persistent Store (stored)
- DRO (DRO) (tnwgd)
- Unicast Resolver Daemon (lbmrd)
- Stateful Resolution Service (SRS)
- UM Manager (UMM) (ummd)
- UMQ Active MQ broker
- UMDS (umdsd)

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
UMDS Server (umdsd) | YES | no | no

Platforms not mentioned in the above table are not supported for the UM daemon components, including 32-bit Linux, Solaris, AIX, Darwin (MacOS) 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.

# Deprecations for 6.11.1 <-

Attention
  The original 6.11.1 release notes announced the deprecation of certain platforms for UM daemons, claiming that they would be discontinued in UM version 6.12. However, some users requested more time for the transition. Starting with UM version 6.12, these deprecated daemon platforms have not yet been removed, and are therefore still fully supported in 6.12. Starting with UM version 6.13, the UM daemons will no longer be available on certain platforms. See Platform Deprecations for Daemons.

Note
  User applications will continue to be fully supported on all platforms. These deprecations only apply to UM daemon executables, such as the Store Daemon and the Dynamic Router daemon.

UM daemons will continue to be available on the following platforms:

- Persistent Store daemon ("stored"): Linux 64-bit, Windows 64-bit.
- UM Dynamic Router daemon ("tnwgd"): Linux 64-bit, Windows 64 and 32-bit.
- UM Manager daemon ("ummd"): Linux 64-bit, Windows 64-bit.
- UM Resolution daemon ("lbmrd"): Linux 64-bit, Windows 64-bit.
- UM Queue Broker (ActiveMQ): Linux 64-bit, Windows 64-bit.

The planned deprecated daemon platforms are:

- Solaris (X86 and Sparc)
- AIX
- Darwin (MacOS)
- Linux 32-bit
- Windows 32-bit (except Dynamic Router "tnwgd", which will continue on 32-bit)

User applications deployed on these platforms will fully interoperate with daemons running on the reduced set of platforms.

Contact UM Support if any of these planned deprecations interfere with your existing or planned deployments.

# Deprecations for 6.10 <-

## Streaming Deprecations for 6.10 <-

- DEPRECATED: Adaptive Batching. Adaptive batching is still operational, but planned to be removed in a future release.

- DEPRECATED: Explicit Batching. Explicit Batching is still operational, but planned to be removed in a future release.

- DEPRECATED: Hypertopics. HyperTopics is still operational, but planned to be removed in a future release.

- DEPRECATED: 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.

- DEPRECATED: RDMA transport. The "lbt-rdma" selection for transport (source) no longer functions. The underlying third-party library is no longer available from the vendor. Users should use UD Acceleration for Mellanox Hardware Interfaces.

## Persistence Deprecations for 6.10 <-

- Java APIs deprecated:

  - DEPRECATED: UMEBlockSrc class
  - DEPRECATED: LBMContext.setUMQInflight() method
  - DEPRECATED: LBMContext.setUMQMessageStable() method

## Dynamic Router Deprecations for 6.10 <-

- DEPRECATED: Dual-TCP peer links. UM DRO version 6.10 no longer supports dual-TCP peer links. The XML configuration elements '`<tcp>`' and '`<companion>`' will generate errors. Upgrading customers should use <single-tcp> instead.

# Deprecations for 6.8 <-

## Persistence Deprecations for 6.8 <-

- For Persistent Stores, the '`<topic>`' option type value '`regexp`' is deprecated.

- The Round-Robin store failover configuration, which was deprecated in UM 6.7, is now removed from Ultra Messaging 6.8 and is no longer available.

## Queuing Deprecations for 6.8 <-

The following configuration options are deprecated and no longer function.

- umq_flight_size (context)
- umq_flight_size_behavior (context)
- umq_msg_total_lifetime (context)
- umq_message_retransmission_interval (context)
- umq_message_stability_notification (context)
- umq_queue_check_interval (context)
- umq_queue_name (source)
- umq_queue_participants_only (source)
- umq_queue_query_interval (context)
- umq_require_queue_authentication (context)
- umq_retention_intergroup_stability_behavior (context)
- umq_retention_intragroup_stability_behavior (context)
- umq_retention_intergroup_stability_behavior (source)
- umq_retention_intragroup_stability_behavior (source)

The following C API functions are deprecated and no longer function:

- lbm_ctx_umq_get_inflight()
- lbm_umq_ctx_msg_stable()
- lbm_queue_immediate_message()
- lbm_auth_set_credentials()

The following Java and .NET API functions are deprecated and no longer function:

- UMEBlockSrc class
- LBMContext.setUMQInflight() method
- LBMContext.setUMQMessageStable() method

## Dynamic Router Deprecations for 6.8 <-

- The '`<regex-pattern>`' configuration option element is deprecated.

# Deprecations for 6.7 <-

## Streaming Deprecations for 6.7 <-

- The lbmmon_attr_get_contextid() function is deprecated. Instead, use lbmmon_attr_get_objectid().

## Persistence Deprecations for 6.7 <-

- The Round-Robin Store failover configuration is deprecated.

- The '`repository-disk-max-write-async-cbs`' option is deprecated.

# Deprecations for 6.5 <-

## Streaming Deprecations for 6.5 <-

- The Java send methods that accept a callback object (cbArg) are deprecated:

  - send(byte[] message, int messageLength, int flags, java.lang.Object cbArg)
  - send(java.nio.ByteBuffer message, int startPosition, int messageLength, int flags,java.lang.Object cbArg)

  Use the send method that accepts an LBMSourceSendExInfo object instead.

# Deprecations for 6.0 <-

## Streaming Deprecations for 6.0 <-

- 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 otr_request_message_timeout (receiver).

- The Late Join option retransmit_request_generation_interval is deprecated and replaced with new option retransmit_request_message_timeout (receiver). The new option defines an RX give-up interval on a per-message basis.

# Deprecations for pre-6.0 <-

Deprecations for UM versions prior to 6.0.

- Functions lbm_context_set_name() and lbm_context_get_name() are deprecated and no longer have any functionality. Use configuration option context_name (context) instead.

- The constants LBM_SRC_EVENT_UME_REGISTRATION_SUCCESS, LBM_MSG_UME_REGISTRATION_SUCCESS, LBM_SRC_EVENT_UME_MESSAGE_STABLE, LBM_SRC_EVENT_UME_DELIVERY_CONFIRMATION, and the structures lbm_src_event_ume_registration_t, lbm_msg_ume_registration_t. are no longer used.

  Applications must instead use LBM_SRC_EVENT_UME_REGISTRATION_SUCCESS_EX, LBM_MSG_UME_REGISTRATION_SUCCESS_EX, LBM_SRC_EVENT_UME_MESSAGE_STABLE_EX, LBM_SRC_EVENT_UME_DELIVERY_CONFIRMATION_EX, and the structures lbm_src_event_ume_registration_ex_t, lbm_msg_ume_registration_ex_t, lbm_src_event_ume_ack_ex_info_t.

For other deprecations made in pre-6.0 versions of UM, see the Change Log document the UM version 5.3.6 Documentation Set.