Deprecated and removed features
See which features are no longer developed, and which have been removed since the last major release.
A deprecated feature is still supported, but it is no longer developed and its continued use is not recommended. Typically, a new feature replaces the deprecated feature, which is eventually removed from the product. If you are using a deprecated feature, migrate to the replacement as soon as possible.
The following table lists the deprecated and removed features. Each listed feature is shown with the following information:
- Component: The module that contains the feature, for example, the feature modeling decision services is in the component Decision Center Business console.
- Replacement: When possible, an alternative feature is given for the deprecated feature.
- Deprecated version: Shows the version number of the Operational Decision Manager release in which the feature is first reported as deprecated.
- Removed version: Shows the version number of the Operational Decision Manager release from which the feature is removed. The version is the first release in which the feature is no longer available.
| Feature | Component | Replacement | Deprecated version | Removed version |
|---|---|---|---|---|
| Old decision table editor | Decision Center and Rule Designer | By default, the components display the new decision table editor. 
Learn more... |
8.11.1 | Not applicable |
| Old Intellirule rule editor | Decision Center | By default, the Business console displays the new rule editor.
Learn more... |
8.11.1 | Not applicable |
| XML binding | Rule Designer | Java XOM with JAXB or similar API | 8.11.1 | Not applicable |
| Java 8 | Decision Server Rules and Decision Center | ODM might not support Java 8 in future releases. ODM might similarly not
support frameworks and tools that are based on Java 8 (for example, WebSphere Application Server
traditional support).
Learn more... |
8.11.1 | Not applicable |
| WebSphere Application Server traditional | Decision Server Rules and Decision Center | The recommended application server is WebSphere Liberty.
Learn more... |
8.11.1 | Not applicable |
| Guided editor | Rule Designer | Use the new rule editor.
Learn more... |
8.11.1 | Not applicable |
| 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 | Not applicable |
| Execution using REST + XML (HTDS) | Rule Execution Server | Use REST with JSON.
Learn more... |
8.11.1 | Not applicable |
| XU memory profiler | Rule Execution Server | None | 8.11.1 | Not applicable |
| Decision Server Insights | Decision Server Insights | None | 8.10.5.1 | 8.11.0 |
| Decision Center Enterprise console | Decision Center | Decision Center Business
console
Learn more... To configure fine-grained permissions, use the
Decision Center REST API. |
8.10.5.0 | 8.11.0 |
| Installation Settings Wizard | Decision Center Enterprise console | Use the REST API for creating a data schema. Alternatively, you can use Ant
tasks.
Learn more... |
8.10.5.0 | 8.11.0 |
| Business Intelligence and Reporting Tools (BIRT) | Rule Designer | None | 8.11.0 | 8.11.0 |
| Decision model services | Decision Center Business console | Automation Decision Services
Learn more... |
8.10.5.0 | Not applicable |
|
Oracle WebLogic Server |
All modules |
Move to another supported application server. |
8.10.0 | Not applicable |
| Token-based authentication in Decision Center REST API | Decision Center | The Decision Center REST
API provided a custom token-based authentication scheme. This scheme is replaced with OpenID
Connect, and removed in 8.11.0. These REST API endpoints are no longer included: /token
(POST) and /token(DELETE).
Learn more... |
8.11.0 | 8.11.0 |
|
Java™ Management Extensions (JMX) public API for RuleApp and ruleset management in Rule Execution Server |
Decision Server Rules |
Use session management for local or the REST API for remote use.
Learn more... Note: The JMX public API for Rule Execution Server notification is not deprecated. You can still
use this part of the API.
|
8.10.0 | Not applicable |
|
Classic rule engine |
Decision Server Rules and Decision Center |
The decision engine replaces the classic rule engine. Information on migrating
to the decision engine is available here:
Learn more... See the section for information on how the decision engine
compares with the classic rule engine: |
8.9.0 | Not applicable |
|
Custom business rule languages |
Decision Server Rules and Decision Center |
The recommended approach is to use the business action language. If this is not sufficient,
consider technical rules. |
8.8.1 | 8.11.0 |
|
Rule and decision table templates |
Decision Server Rules and Decision Center |
Copy and paste rule artifacts in the Decision Center Business console. |
8.8.1 |
|
|
Decision trees |
Decision Server Rules and Decision Center |
Use decision tables or ruleflows. |
8.8.1 | Not applicable |
|
Classic rule projects |
Decision Server Rules and Decision Center |
Classic rule projects must be migrated to decision services for continued
use. For migration instructions, see 8.10.5: Migrate classic rule projects to decision services. |
8.8.0 | 8.11.0 |
|
Decision Validation Services and Scenario Service Provider |
Decision Server Rules and Decision Center |
Use testing and simulation features in the Decision Center Business console.
Learn more... |
8.8.0 | 8.11.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 | Not applicable |
|
COBOL code generation |
Rule Designer and Decision Center |
Use the COBOL migration wizard in Rule Designer to migrate rules for COBOL projects to decision services. |
8.5.0 | 8.11.0 |