Deprecated and removed features

Features can go out of development or be removed. Check to see whether you are impacted by these changes.

While still supported, a deprecated feature is no longer developed, and its continued use is not recommended. Typically, a deprecated feature is replaced with a new one and eventually removed from the product. If you are using a deprecated feature, migrate to its replacement as soon as possible.

The following tables list the deprecated and removed features. The list starts at the bottom with Operational Decision Manager 8.5.1.0.

The tables use the following column names:

• Feature: The name of the deprecated or removed feature.
• Component: The module that contains the feature, for example, the Decision Center Business console.
• Replacement: When possible, an alternative feature is given for the deprecated feature.
• Deprecated version: Shows the version number of the release in which the feature is first reported as deprecated.
• Removed version: Shows the version number of the release from which the feature is removed. The version is the first release in which the feature is no longer available.

Deprecated features

A feature is deprecated in one version and then removed from a future version. However, it is possible for a feature to be removed without being deprecated in a previous version. This occurs when a product is removed without prior notification.

Table 1. Deprecated features

Feature	Component	Replacement	Deprecated version
Streams	Decision Center	The social stream feature in the Business console has been deprecated. The feature is hidden by default and can be displayed by changing a property. To enable it, see Following streams and posting comments.	9.6.0.0
Archiving tool	Decision Center	Use the cleanup tool. Learn more...	9.6.0.0
vault.enabled	Operational Decision Manager on Certified Kubernetes	Use <secretreference>.name and <secretreference>.type=spc to mount the secret as a SecretProviderClass. Default type remains 'secret' (Kubernetes Secret). If <secretreference> is used as a string, it is treated as the name of a Kubernetes Secret.	9.6.0.0
vault.type	Operational Decision Manager on Certified Kubernetes	Use <secretreference>.type=spc to specify a SecretProviderClass. Default type remains 'secret' (Kubernetes Secret).	9.6.0.0
Ingress NGINX support	Operational Decision Manager on Certified Kubernetes	Ingress NGINX is retired in favor of the Gateway API. The Ingress NGINX documentation is to be removed in a future release. For more information, see Ingress NGINX Retirement: What You Need to Know .	9.6.0.0
IlrSessionRequest#setTaskName and com.ibm.rules.engine.ruleflow.runtime.RuleflowEngineInput#setMainTask(String)	It can be used from different components.	IlrSessionRequest is the interface for session requests. This class is used to execute rulesets in a stateless rule session. Use a decision operation with a defined ruleflow instead.	9.6.0.0
SOAP compatibility modes 7.0, 7.1 and 7.1.1.3 (HTDS)	Rule Execution Server	See Viewing or downloading an HTDS description file.	9.6.0.0
Execution using SOAP + WSDL (HTDS)	Rule Execution Server Note: SOAP 1.1 is supported and not later versions of SOAP.	Use REST API. Learn more...	8.11.1.0
IBM® Db2® for z/OS® for Decision Center	Decision Center	Switch to another supported database.	9.5.0.0
Monitoring API ilog.rules.monitor.*	Rule Designer	None	9.5.0.0
Customization of the Decision Center Business console using PVC	Operational Decision Manager on Certified Kubernetes	To customize the Business console, see Configuring the Decision Center Business console.	9.0.0.1
Decision Warehouse	Rule Execution Server	Emit decision events to a monitoring service, like Apache Kafka or IBM Business Automation Insights. Learn more...	9.0.0.0
Legacy ruleflow editor	Rule Designer	Use the new ruleflow editor. Learn more...	9.0.0.0
Windows COBOL compiler	Rule Designer and Decision Runtime for z/OS	By default, the compiler has been replaced with the Windows Subsystem for Linux®.	9.0.0.0
Intermediate code generation in the decision engine	Decision Center	A decision service with the XOM enabled in Decision Center compiles rules by default to executable code (Java™™ bytecode). Learn more...	9.0.0.0
RetePlus without ruleflow	Rule engine for Decision Server Rules Context: RetePlus execution mode.	Use RetePlus only with default mode. Learn more...	8.12.0.0
Legacy decision table editor	Rule Designer	By default, the components display the new decision table editor. Learn more...	8.11.1.0
XML binding	Rule Designer	Java XOM with JAXB or similar API	8.11.1.0
Execution using REST + XML (HTDS)	Rule Execution Server	Use REST with JSON. Learn more...	8.11.1.0
Decision trees	Decision Server Rules and Decision Center	Use decision tables or ruleflows. Learn more...	8.8.1.0
RetePlus literal and priority ordering modes	Rule engine for Decision Server Rules Context: RetePlus execution mode.	Use RetePlus only with default mode. Use the literal and priority ordering modes with the sequential or the Fastpath algorithm. Learn more...	8.5.1.0