IBM Sterling Order Management Software certified containers

You can review the changes to functions and resources, including stabilization, deprecations and removals that occurred in Sterling Order Management Software certified containers, with links to further information.

November 2022 (10.0.2209.1)

Restructuring of JWT parameters for integration
The JWT parameters, algorithm, issuer, and audience are moved out from the integrated orderService spec of OMEnvironment. These JWT parameters are now included under common.jwt in OMEnvironment. For more information, see Configuring common parameter.

September 2022 (10.0.2209.0)

Support to independently scale deployment replicas
You can now scale the application and agent server deployments manually independent of the Sterling Order Management Software Operator.
JVM capability to adjust memory parameters automatically
The agent JVM is enhanced to use the resource requests and limits that you set on a server, such that it recognizes and adjusts the memory parameters automatically.
Enhanced trust store properties
The security parameters security.ssl.trust.storeLocation and security.ssl.trust.trustedCertDir are enhanced to act independently. This allows you to specify both storeLocation and trustedCertDir properties in security parameter, which are merged to create the trust store. For more information about security properties, see Configuring security parameter.
Build optimization for IBM Sterling Call Center
The build time for IBM Sterling Call Center is improved by optimizing minification. The generateImages includes this optimization OOB, thereby improving image generation time by nearly 50%, when isccs is in the WAR files list.

June 2022 (10.0.2206.0)

Helm chart is deprecated
Helm chart is no longer available for installing Sterling Order Management Software. You can now use the IBM Sterling Order Management Software Operator to install your Sterling Order Management Software. For more information about Operator, see Introduction to IBM Sterling Order Management Software Operator.
Note: All the knowledge centre pages that relates to Helm are marked as legacy.
Adopted Continuous Delivery support lifecycle policy
  • The product lifecycle policy for IBM Sterling Order Management Software has changed from Standard support to Continuous Delivery support. The Continuous Delivery model matches how IBM has been providing updates to Sterling Order Management Software 10.0 since its release in 2018. Aligning the lifecycle support policy to the Continuous Delivery model provides a more accurate representation of Sterling Order Management Software product updates and improved clarity for product support.
  • The new Continuous Delivery version numbering scheme is introduced. The first update to include the numbering is in Q2 2022 which is 10.0.2206.0 where,
    • The first two digits remain 10.0.
    • The third digit indicates the major quarterly update including the two-digit year followed by the two-digit month of the end of the quarter.
    • The fourth digit indicates minor updates and increments sequentially from 0 for each major update.
Note:
  • Continuous Delivery updates will still be made available through Fix Central, the same way that fix packs are published currently.
  • IBM remains committed to world-class product and customer support. The adoption of the Continuous Delivery support lifecycle policy aligns the support policy to the update process used by Sterling Order Management Software from 2018.

Upgrade impact: No.

For more information about adopting the Continuous Delivery support policy, see Adopting Continuous Delivery support policy.

Stack upgrade
  • WebSphere Application Server Liberty
  • JDK
  • Kubernetes
  • IBM Sterling Order Management Software
  • IBM Sterling Call Center
  • IBM Sterling Store Engagement
  • IBM Sterling Web Store
  • Red Hat OpenShift Container Platform

February 2022

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.

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. The flag in server configuration from Applications Manager to auto-terminate the servers is not considered.

Upgrade impact: No.

Enhanced CDT to export/import data
CDT is enhanced to support data export and import for one type of table - config or master - at a time. Running only one type of table at a time, ensures that the CDT runs efficiently and smoothly. For more information, see CDT command-line arguments in text mode.

Upgrade impact: No.

Enhanced InteropHttpServlet to force request validation
A new yfs property, yfs.servlet.requestvalidation.forced.urls is introduced to force request validation on InteropHttpServlet. For more detailed information, see Order management yfs.properties file.

Upgrade impact: No.

Stack upgrade
  • Struts is upgraded to version 2.5.26 for the following applications:
    • IBM Sterling Store Engagement, (Next-generation and Legacy)
    • IBM Sterling Call Center
    • Sterling Business Center
    • System Management Administrator (SMA)
  • Red Hat Universal Base Image (UBI)
  • Kubernetes
  • OpenShift Container Platform
Note: Struts customization is not supported for Sterling Store Engagement, (Next-generation). If any customization exists for an application struts.xml, ensure to upgrade the Document Type Definition (DTD) version to 2.5.

September 2021

Resolved the terminating state of pods

The Helm chart is updated to ensure that the hearbeat records are updated with new entries. This ensures that the application, agent, and integration servers are terminated properly whenever you alter the pod count to control the amount of incoming and outgoing network traffic for these servers.

Configured the restrictive cookie path in Liberty
To avoid cookie crossover across multiple applications of Sterling Order Management Software, the Liberty server is configured to restrict cookies only to context roots. For example, this enhancement ensures that cookies of Sterling Business Center are shared only with the Sterling Business Center application.

For more information about configuring cookie settings, see Configuring a restrictive cookie path in Liberty.

Reorganized Red Hat OpenShift Container Platform topics in IBM Documentation
For a better customer experience, the Red Hat OpenShift Container Platform topics in IBM Documentation are reorganized. You can find the corresponding topic links in the IBM Certified Containers topic.

March 2021

Optimized container image builds
  • The dependency on CentOS image is removed for image generation.
  • The time taken to build om-base image is improved by installing buildah from a cached copy within om-base image that is obtained through Red Hat certified repositories.
  • The time taken to build the om-app image is improved by using Liberty features from a cached copy within om-base image.
Addressed security vulnerabilities
The certified container images are made available with all the recommended security fixes.
Support for encrypted properties
The yfs category properties are now loaded while looking for security.propertyencrypter.class so that the property encrypter class is picked up as expected.
Enhanced generateImages script
The generateImages script is enhanced such that the exported images preserve the name and tag information that are restored when the images are loaded to the target container repository.

December 2020

Enhanced Sterling Order Management Software Helm chart
The Sterling Order Management Software Helm chart is enhanced such that when Ingress is enabled, the Sterling Order Management Software Helm chart is successfully installed.
Routes created for Javadoc
The following routes are created when Javadoc is exposed through Sterling Order Management Software Helm chart:
  • /smcfsdocs/yfscommon/api_javadocs
  • /smcfsdocs/yfscommon/core_javadocs
  • /smcfsdocs/yfscommon/ERD/HTML

September 2020

Updated network policy
The network policy for OpenShift Container Platform is updated to support multiple cloud platforms.
Modified image storage location
The storage location for buildah is updated to be independent of the shared volume.
Simplified data setup job
The data setup job now uses ConfigMap to publish the completion of data setup and is no longer dependent on persistent volume.
Stack upgrade
The following middleware are upgraded to a later version. For more information about the supported version, go to IBM Software Product Compatibility Report website. Open the Detailed system requirements for a specific product page and generate a requirements report.
  • Red Hat Universal Base Image (UBI)
  • Liberty
  • Helm
  • Kubernetes
  • OpenShift Container Platform

April 2020

Helm version 2 is deprecated
Helm version 2 is deprecated. Instead, Sterling Order Management Software supports Helm version 3 that you can install.

March 2020

Red Hat OpenShift Container Platform, version 4.2 not supported
Red Hat OpenShift Container Platform, version 4.2 is no longer supported. Ensure to install OpenShift Container Platform, version 4.3 or later.
Red Hat OpenShift Container Platform download part numbers updated
The Red Hat OpenShift Container Platform download part numbers for both Sterling Order Management Software Professional and Enterprise editions are updated. For more information about the updated part numbers, see Download document.