What's changed in 2022

Check out what's changed in IBM® Sterling Order Management System 2022.

24 June 2022 (22.2 Minor update 1)

Performance enhancements for real-time dashboards

The performance of Sterling Order Management System is improved in providing real-time updates to data-tier of the Order Hub metrics and the Store Manager dashboard. This update also improves the upkeep of backend database tables that are used for real-time dashboards in the Sterling Order Management System user interfaces - Order Hub and IBM Sterling Store Engagement.

Upgrade impact: No.

27 May 2022 (Release 22.2)

Enhanced REST framework

When Sterling Order Management System APIs are called through the REST framework, if the input is in the JSON format, the output is automatically converted to JSON. In some such scenarios, it cannot be determined whether a child element in the XML is an array item or a child object. To avoid these inconsistencies, the REST framework is enhanced so that you can now enforce an XPath in the XML to define whether the child element is an array item or a child object.

For more information, see Specifying output format for JSON.

Upgrade impact: No.

Stack upgrades
  • IBM JDK - (1.8.0_321)
  • IBM WebSphere Liberty application server -

Upgrade impact: No.

Legacy platformNon-production environment outage
  • Occurs within first 30 minutes of upgrade in Development, QA, MC, and Pre-production environments
  • No outage in Production
Next-generation platformPre-production environment outage
  • Occurs within first 30 minutes of upgrade
  • No outage in other environments such as Development, QA, MC, and Production
Note: The Non-production and Pre-production outage is a one-time exception and will not occur in future upgrades.

31 March 2022 (22.1 Minor update 1)

Enhanced data extracts

Improved the data extract for handling backup database while syncing data during the database maintenance and long running reorganizations.

Upgrade impact: No.

25 February 2022 (Release 22.1)

Enhanced entity deployment

Improved the entity deployment (dbverify) to ignore Db2 reorganizations to run after every alter SQL statement, and run the Db2 reorganizations only for the alters that need mandatory reorganization to be run after the alter SQL statements.

The following alter types do not require reorganization of the table.
  • alter to add constraint (pk)
  • alter to mark table volatile
  • alter to add column
  • alter to increase or decrease column size
  • alter to change/set column default
The following alter types require reorganization of the table.
  • alter to drop column
  • alter to change column data type
  • alter to change column from not null to nullable
  • alter to change column from nullable to not null

Upgrade impact: No.

Enhanced server termination

Improved the graceful termination of agent and integration servers and minimize the impact on RMI communications because of the graceful or hard termination of servers.

Auto-termination of servers is disabled in Sterling Order Management System. The flag in server configuration from Applications Manager to auto-terminate the servers is not considered.

Upgrade impact: No.

Stack upgrades
  • Db2 is upgraded to 11.5.7.
  • Struts is upgraded to 2.5.26 for the following applications:
    • IBM Sterling Store Engagement (Next-generation and Legacy)
    • IBM Sterling Call Center
    • IBM Sterling Business Center
    • System Administration Console (SMA)
    Note: Struts customization is not supported for Store Engagement (Next-generation).

    If an existing customization of struts.xml is available for any of your applications, you must change the DTD version from 2.3 to 2.5.

    For any deployments post the 22.1 upgrade, if you have extended IBM Sterling Business Center web.xml, you must replace the org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter filter class with org.apache.struts2.dispatcher.filter.StrutsPrepareAndExecuteFilter in the \extensions\files\repository\eardata\sbc\extn\web.xml file in the extension.