Deprecated functionality

If we are migrating from an earlier version of WebSphere Commerce, be aware of the various features that are deprecated from this and earlier releases.

Deprecated features

If a feature is listed as deprecated, IBM might remove this capability in a subsequent release of the product.

Recommended action. Typically, a feature is not removed for one major release or five full years (whichever time period is longer) after the release in which that feature is deprecated. For example, if a feature was deprecated in Version 6 (released June 2006), then IBM can remove the deprecated feature in a major release on or after June 2011. Version 6.0 and Version 7.0 are considered major releases. In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these deprecated features.

WebSphere Commerce SOI services

Working with WebSphere Commerce services involves developing client libraries, new commands, and business logic.
Recommended action: Use the REST service framework to work with the command framework and develop business services. Java Persistence API

Data service layer

The data service layer (DSL) provides an abstraction layer for data access that is independent of the physical schema.
Recommended action: Use the Java Persistence API. See Java Persistence API.

WebSphere Commerce use of Open Applications Group (OAGIS) messaging in the storefront

Previous version of WebSphere Commerce service interfaces were defined using the OAGIS message structure from The Open Applications Group. In WebSphere Commerce Version 9, the storefront no longer uses and BOD services.
Recommended action: Use Rest tag in the storefront. Use the REST service framework to implement new back-end services. See Java Persistence API. BOD services and OAGIS messaging for integration is not deprecated.

Request for Quote (RFQ)

The RFQ functionality, originally introduced in WebSphere Commerce version 5, is deprecated in WebSphere Commerce V9.
Recommended action: Integrate with IBM CPQ to leverage the RFQ functionality in Sterling Configure Price Quote.

ATP inventory model

Available to promise (ATP) inventory allocation, a method of allocating inventory using WebSphere Commerce as the inventory system of record, is deprecated in WebSphere Commerce V9.
Recommended action: Integrate with IBM Order Management using the DOM integration mode.

Return process

The return process and the data model is deprecated in WebSphere Commerce V9.
Recommended action: Integrate with IBM OMS to manage return orders, or reverse orders.

Related concepts
Discontinued functionality in WebSphere Commerce Version 9
What's new in WebSphere Commerce Version 9.0.1.x