Removed and deprecated features in 10.1

Software AG's Event-Driven Architecture (EDA) is deprecated. Support for EDA events will be removed in a future release. It is recommended that your Apama applications use digital event types instead, as provided by Software AG Digital Event Services. For further information, see The Digital Event Services Transport Connectivity Plug-in.

Use of the CLASSPATH environment variable to configure the correlator's system classpath is deprecated and will be removed in a future release. It is recommended that you set the classpath on a per-plug-in basis where possible, for example, in the descriptor file for an EPL or JMon plug-in (see Specifying the classpath in deployment descriptor files) or in the configuration file for a connectivity plug-in, JMS or distributed MemoryStore library. For cases where you really need to set the global system classpath, you can use the -J (or --javaopt) option of the correlator tool, along with -Djava.class.path=path (as described in Starting the correlator).

The ConnectivityPlugins.createChain method in EPL has been deprecated. Use ConnectivityPlugins.createDynamicChain instead. See also Connectivity plug-ins enhancements in 10.1.

The --remoteDeploy and --remoteUndeploy options of the dashboard_management tool (see Managing and stopping the data server and display server) have been removed in 10.1. These options relied on third-party technology that has not been officially supported since 5.1.

As of this version, the deprecated EngineManagement API for C can no longer be used. It is recommended that you use the EngineManagement API for C++ instead. See EngineManagement API. Any clients written using engine_client_c.h will need to be rewritten to use engine_client_cpp.hpp instead. This includes clients written in pure C and clients written using the C++ shims defined in the engine_client_c.h file. See also the announcement in Removed and deprecated features in 9.12.

As of this version, the deprecated native Universal Messaging integration can no longer be used. It is recommended that you use the Universal Messaging connectivity plug-in instead. See also Apama integration with Universal Messaging in 9.12.

dynamicChains:
umString:
- apama.eventString:
suppressLoopback: true
description: "@{um.rnames}"
remoteAddress: "@{um.rnames}"
- stringCodec
nullTerminated: true
- umTransport:
channelPattern: ".*"

Removed configuration	New configuration
um.channels.prefix=UM_ um.channels.mode=precreate	managerConfig: channel: prefix: UM_ includePrefixOnUM: true missingChannelMode: ignore
um.channels.prefix=UM_ um.channels.mode=autocreate	managerConfig: channel: prefix: UM_ includePrefixOnUM: true missingChannelMode: create
um.channels.prefix=UM_ um.channels.mode=mixed	managerConfig: channel: prefix: UM_ includePrefixOnUM: true missingChannelMode: create
um.channels.mode=precreate	managerConfig: channel: prefix: "" missingChannelMode: ignore

In the removed configuration, it was possible to configure some channels (without a prefix) to be looked up on Universal Messaging but not created, while also specifying a prefix under which channels would be created. This specific use case is not possible to directly port to the new-style configuration.

Note: The above configuration style which has been removed for the correlator is still used for the IAF (see Defining Universal Messaging properties for the IAF). For communication with the correlator, however, the Universal Messaging transport connectivity plug-in is required, and this connectivity plug-in must be configured to be equivalent to the Universal Messaging properties you have configured for the IAF (see also Communicating with the correlator over Universal Messaging).