Webcasts
Abstract
This Support Technical Exchange (STE) session is designed to strengthen understanding of the IBM Sterling OMS Containers setup and OMS Operator, through in-depth technical insights, which will cover how the OMS Operator streamlines deployment using CRDs and a declarative model, enabling automated lifecycle management. Includes end-to-end deployment flow, environment setup (dev→prod), use of op_util for install/validation (online & air-gapped), image/catalog management (tags vs digests), and image customization with build tools.
Though this session mainly focuses on IBM Sterling OMS Container setup, it will be useful for others as well in understanding the baseline technical concepts around it.
Content
Webinar Session Details:
Title: IBM Sterling OMS Operator Deep Dive Series: Session 1 - Deployment & Automation Simplified
Schedule: Tuesday, June 23rd, 2026, 10:00 AM - 11:00 AM Eastern Time (US & Canada)
Session Speakers:
Chiranjeevi Dasegowda - Senior Support Engineer, IBM Sterling OMS Support
Tin Vo - Senior Software Developer, IBM Sterling OMS Development
Session hosts:
Jitendra Buge - Technical Lead, IBM Sterling OMS Support
Cathrin Christo Sagayarajan - Technical Support Engineer, IBM Sterling OMS Support
Questions and Answers:
Question: We are on IBM Sterling OMS NextGen SaaS. Can we use the features discussed in this session?
Answer: This session is specific to OMS deployed on containers, where you own and manage the Kubernetes cluster and the OMS operator. In the NextGen SaaS version, all of this is handled automatically by IBM. You do not need to manage the operator, catalog sources, image mirroring, or any of the deployment configurations covered today. If you are on SaaS, we (IBM) team manage this on your behalf.
Question: When an operator rollback is performed in production, how are database schema changes rolled back?
Answer: It is important to distinguish between two different things here. This session covered operator rollback, rolling back the operator controller deployment itself, which is the binary that manages your OMS environment. That rollback does not touch the database at all.
Rolling back the OMS application code and database schema is a separate activity entirely, and for that you should follow the same best practices you already have in place today for OMS upgrades. take a full database backup before upgrading, validate in a lower environment first, and ensure you have a tested restore procedure before touching production. Nothing changes about that process when running on containers. The operator manages the deployment mechanics, but your OMS application upgrade and rollback discipline remains the same as it always has been.
Question: Can I deploy an OrderHub instance using the OMS operator that connects to an on-premises OMS running as DIY containers, and also connects to SIP containers hosted on a different Kubernetes cluster?
Answer: Yes, OrderHub and Call Center support standalone deployments. You can deploy OrderHub using the operator and point it at an external OMS by providing the OMS admin URL in the configuration. The OMS instance itself does not need to be operator-managed or on the same cluster. Cross-cluster connectivity is your responsibility to establish at the network level, but the operator supports this topology.
Question: Can I use the same fix pack version for example 10.0.2503.0, with the new stable catalog images, the same way I used it with the v1.0 catalog?
Answer: Yes, the fix pack versions are compatible with both catalog images. The catalog image is just the channel through which OLM discovers available operator versions, the operator binary itself is the same. That said, IBM recommends migrating to the stable catalog so you receive automatic notifications when newer versions become available. The v1.0 catalog will be deprecated and stable is the path forward.
Question: When will the v1.0 catalog images be deprecated?
Answer: IBM has indicated the v1.0 catalog images will be deprecated soon, but no specific date has been published. Watch the What's New in Containers section of the IBM documentation, deprecation announcements will appear there first.
https://www.ibm.com/docs/en/order-management-sw/10.0.0?topic=new-in-containers
In the meantime, plan your migration to the stable catalog images now rather than waiting for a forced cut-over.
Question: What are the minimum CPU and memory requirements for OMS pods?
Answer: There is no single fixed answer, requirements depend on your business volume, the number of concurrent users, order throughput, and your performance SLOs. IBM's recommendation is to baseline with the reference numbers in the product documentation and then validate through performance testing against your projected load before going to production.
Reference: IBM Documentation — Meeting the system requirements
NOTE -
Presentation
Multimedia
Was this topic helpful?
Document Information
Modified date:
30 June 2026
UID
ibm17276088