This document lists the software compatible with Oracle Communications Order and Service Management (OSM).
OSM Common Software Compatibility
This section describes the software required to support the Oracle Communications Order and Service Management (OSM) cloud native and traditional deployment.
Table 1-1 Supported Common Software for OSM Cloud Native and Traditional Deployment
Software | Version | Notes |
---|---|---|
Cloud IaaS Support |
Oracle Cloud Infrastructure Amazon Web Services Elastic Computing EC2 Amazon Web Services Relational Database Service (RDS) Amazon Web Services Relational Database Service (RDS) Custom |
Currently, Amazon Web Services Relational Database Service (RDS) lacks the ability to control one-off patches and is not recommended for OSM production deployments. When using Amazon Web Services Relational Database Service (RDS) Custom, Oracle strongly recommends configuring an Active Data Guard standby database in the same Region but different AZ for high-availability. |
Grafana | 10.x (x >=4.2) |
Optional. This is for monitoring purposes. |
Java |
8 update 441 17.0.14 Earlier versions, starting with 8 update 391 (for Java 8) and versions starting with 17.0.9 (for Java 17) are also certified. |
Cloud Native: Java 8 for OSM Fusion Middleware and DB Installer images. Java 17 for OSMGW and RTUX images. Recommended versions as per the manifest file. See "OSM Cloud Native Manifest File". Traditional: Java 8 is applicable for both Linux and Solaris |
Oracle Communications Service Catalog and Design - Design Studio application only | Design Studio 8.0.0.2.3 and later | This is the evolution of Oracle Communications Design Studio. |
Oracle Database (installed as Container Database) | Oracle Database 19c |
Enterprise Edition or Oracle OCI Database Service: Enterprise Edition High Performance / Oracle Grid Infrastructure. Enterprise Edition Extreme Performance may be needed for High Availability (RAC) and Disaster Recovery. Refer to OCI documentation for details on each edition. The database should not be installed on a Microsoft Windows system for a production environment. Microsoft Windows can be used for development, demonstration, and test environments. |
Oracle Database Release Updates (RU), revisions and patches |
19.25.0.0.0 (Highly Recommended) Earlier patches for Oracle Database 19c starting from 19.11.0.0.0 are also supported. |
Although earlier CPUs are supported, Oracle recommends the latest available CPU to avoid security issues. In addition, apply the overlay patches listed in Database Overlay Patches and any other required patches when available. |
Oracle Fusion Middleware Infrastructure | 12.2.1.4 |
Traditional: Fusion Middleware Infrastructure is included in the OSM software media pack. It includes Oracle WebLogic Server, Oracle Coherence, and Oracle Application Development Framework (ADF). |
Oracle Fusion Middleware Patches |
January 2025 CPU and overlay patches (Highly Recommended) Earlier CPUs, starting with October 2023 CPU and overlay patches are also certified. |
Install the patches listed in "Critical Patch Updates and Overlay Patches for Fusion Middleware." Cloud Native: See "OSM Cloud Native Manifest File." Considering the critical fixes delivered with the April 2024 CPU, Oracle highly recommends uptaking the April 2024 CPU or later. Traditional: Patch 29448643 is included in Fusion Middleware 12.2.1.4 and need not be applied again. If you see non-WLS deserialization issues where a value of 100 is not sufficient, then increase the value using the system property as per the following workaround: Set the “-Dweblogic.oif.serialFilter=maxdepth=1000” flag in JAVA_OPTIONS for the managed servers. |
Oracle Instant Client | 19.25.0.0.0 (Recommended) |
Cloud Native: Recommended versions as per the manifest file. See "OSM Cloud Native Manifest File". Traditional: Optional. Used for copying default partition statistics to the partitions for improving performance. Oracle recommends using the latest available version. |
Oracle Linux |
9.x (x >= 3) 8.x (x >= 2) |
Cloud Native: Recommended versions as per the manifest file. See "OSM Cloud Native Manifest File". Oracle Linux is specific to the OSM container images, not for the Kubernetes worker nodes. Traditional: Oracle products certified on Oracle Linux are also supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products. Oracle recommends the latest available update, because later updates may provide modest performance gains. Note: Oracle Applications are developed and tested on Oracle Linux, which is optimized for performance, stability and security. |
Oracle WebLogic Monitoring Exporter |
Cloud Native: As defined in the WKO release Traditional: 2.x (x >= 2.0) |
Optional. Used to see metrics for WebLogic Server in Prometheus. Cloud Native: WME versions used by WKO can be seen in the WKO release notes at: https://github.com/oracle/weblogic-kubernetes-operator/releases Traditional: See WME documentation on GitHub: https://github.com/oracle/weblogic-monitoring-exporter |
Prometheus | 2.x (x >= 51.1) |
Optional. This is for monitoring purposes. |
Web browsers |
Google Chrome 119.0 or later Mozilla Firefox ESR 115.4 or later Microsoft Edge Chromium 118.0 or later |
These apply to the OSM user interfaces. |
OSM Cloud Native Deployment Software Compatibility
Note:
The software listed here are required for OSM cloud native, in addition to the software listed in OSM Common Software Compatibility.Recommended Cloud Native Technology Stack
Note:
Oracle recommends that if you use any of the components listed in this table, then use only the versions of other components listed in this table.Table 1-2 Recommended Versions of Cloud Native Technology Stack
Software | Version | Notes |
---|---|---|
Kubernetes |
1.31.x (x >= 1) 1.30.x (x >= 1) 1.29.x (x >= 1) 1.28.x (x >= 2) 1.27.x (x >= 2) 1.26.x (x >= 2) |
See "Container Platforms for OSM Cloud Native" for further details. |
CRI-O |
1.31.x (x>=0) 1.30.x (x >= 0) 1.29.x (x >= 0) 1.28.x (x >= 2) 1.27.x (x >= 1) 1.26.x (x >= 2) |
CRI-O is required only in Kubernetes runtime environments. |
Docker | 19.03.x (x >= 11) | Docker is required only when building images. |
FluentD | 1.16.x (x >= 1) |
Optional This is for logging purposes. If enabled, the image should be picked from "Kubernetes DaemonSet for FluentD" versions. |
Helm |
3.9.0 or later |
Not applicable. |
Ingress Controller | Ingress Controller version that conforms to your Kubernetes version standard API | Any Ingress Controller that conforms to your Kubernetes version Ingress API and provides annotations needed for OSM as documented in the OSM Cloud Native Deployment Guide. |
Kubernetes Cluster Networking Interface (CNI) | OSM cloud native is certified for the same CNI plugins and versions specified by the WebLogic Kubernetes Operator version listed in this table. | See "WebLogic Kubernetes Operator Documentation" for further details. |
Oracle WebLogic Kubernetes Operator |
4.2.x (x >= 2) 4.1.x (x >= 2) When using Kubernetes versions upto 1.28x 4.0.x (x >= 8)When using Kubernetes versions upto 1.26x |
See the documentation about WKO at: https://oracle.github.io/weblogic-kubernetes-operator/ Note: WKO versions 4.2.5 and later are compatible with OSM 7.5.0.0.7 and later. |
Podman | 4.1.x (x >= 1) | Podman is an alternative to Docker for building images. Oracle recommends using Docker. The OSM cloud native image builder is configured to use Docker, by default. If Docker is not found, the image builder uses Podman. |
OSM Cloud Native Manifest File
The OSM cloud native manifest file tracks updates and patches to the following software:
- Java
- Oracle Fusion Middleware, including patches
- Oracle Instant Client
- Oracle Linux
Oracle updates the manifest files to track Critical Patch Updates for all these components. You are encouraged to uptake the manifests as they are released.
To download the manifest file, see the "OSM Cloud Native Manifest Files (Doc ID 2721663.1)" knowledge article on My Oracle Support.
For information on how to use the manifest file to build your OSM cloud native images, see "Creating OSM Cloud Native Images" in OSM Cloud Native Deployment Guide.
Container Platforms for OSM Cloud Native
OSM cloud native is designed to be agnostic of the underlying cloud infrastructure. It relies on standard APIs, objects and configuration functions from the software products listed in this document. As such, OSM cloud native is certified on any container platform based on a CNCF-certified Kubernetes, provided the version requirements listed in this document are satisfied.
OSM cloud native has been tested on a standard (kubernetes.io) deployment of Kubernetes. OSM cloud native has also been tested on Oracle OCI OKE platform with Oracle Multitenant Database via co-located Oracle Database Service (Bare Metal, VM, and ExaData). OSM cloud native includes specific support for OCI and OKE.
Other Kubernetes distributions and container platforms may impose their own operational, security and configuration requirements. These would have to be addressed as part of the uptake of OSM cloud native, with support from the third party provider.
An important requirement is the presence of an Oracle Multitenant Container Database in close network proximity to the platform, in an environment and configuration that is officially supported by Oracle.
OSM Traditional Deployment Software Compatibility
This section describes the software required to support the OSM components for traditional deployment.
Note:
The software listed here are required for OSM traditional deployment, in addition to the software listed in OSM Common Software Compatibility.Table 1-3 Supported Software for OSM Traditional Deployment
Software | Version | Notes |
---|---|---|
Ant | 1.9.x (x >= 16) | Ant is required for using various tools in the OSM SDK including OSM cartridge management tools. To ensure the tools function correctly, all copies of Ant in use must have the same version number. |
Solaris |
11.x (x >= 3) |
Supported on SPARC platforms only. Note: Check the Oracle Database documentation for any additional operating system patches required to support the database. |
Oracle Application Integration Architecture for Communications Alignment
For Order-to-Activate cartridge compatibility information see Order-to-Activate Cartridge Product Compatibility Matrix (in the OSM Cartridges for Oracle Application Integration Architecture section of the OSM documentation) on the Oracle Help Center website:
http://docs.oracle.com/en/industries/communications/order-service-management/index.html
This document contains information about compatibility between OSM software, OSM Order-to-Activate cartridges, and Oracle Application Integration Architecture (AIA) for Communications. The OSM Order-to-Activate cartridges are used with the Oracle Communications Order to Cash Integration Pack for Oracle Communications Order and Service Management.
For more information about the Order to Cash business process see Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management in the Oracle Application Integration Architecture documentation.
Database Overlay Patches
This section lists database overlay patches. Apply these patches on top of the recommended latest available CPU.
The below table lists database 19.0.0.0 overlay patches.
Table 1-4 Database 19.0.0.0 Overlay Patches
Patch | Description | Details |
---|---|---|
27675947 This patch is included in 19c, but disabled by default. |
ORA-23549: TABLE "SCHEMA"."TABLE" INVOLVED IN REFERENCE PARTITIONING. |
Enables online table redefinition, which is required by
OSM during upgrades. You need to connect with sysdba privileges and
run the following on every database instance to enable the fix:
Note: This patch applies only to the traditional deployment of OSM and is not applicable for OSM cloud native. |
35109397 |
ORA-600 [PMUOCPY2#3: UNHANDLED TYPE] - PMUOCPY2_COPY_RECUR |
After a RMAN Backup and Restore cycle, the database may get corrupt and you might see "Generic OMS Exception" in server logs while trying to open an order from OSM Task client. You need to apply this patch and need to recompile packages, package body, procedures and functions on all OSM schemas (ORDERMGMT,RULE & REPORT). Refer to DOCID 35109397.8 for more details |
Critical Patch Updates and Overlay Patches for Fusion Middleware
OSM is supported on all Oracle Critical Patch Updates. You should install the latest Critical Patch Updates and overlay patches for Fusion Middleware as soon as possible. To download Critical Patch Updates, find out about security alerts, and enable email notifications about Critical Patch Updates, see the Oracle Technology Network website:
https://www.oracle.com/security-alerts/
Table 1-5 lists the January 2025 CPU and Overlay patches.
Table 1-5 January 2025 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 37453807 |
PSU Coherence (12.2.1.4.24) | 37351860 |
ADF Bundle Patch | 37388935 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35965629 |
OPSS for WebLogic Server | 36316422 |
WebLogic Opatch (13.9.4.2.18) | 28186730 |
Fusion Middleware Platform SPU | 36789759 |
Fusion Middleware Thirdparty Bundle Patch | 37374672 |
JDBC 19.25 Bundle Patch | 37258699 |
OSS 19C Bundle Patch | 37297691 |
Cloning SPU for WLS/FMW 12.2.1.4.0 | 37056593 |
Fusion Middleware Control SPU | 36946553 |
Oracle Web Services Manager (OWSM) Bundle Patch | 37035947 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 37202255 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 37284722 |
Oracle Data Integrator Bundle Patch | 37473676 |
Overlay patches |
30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) 37372428 (Password Encryption for RDBMS Security Store) |
Table 1-6 lists the October 2024 CPU and Overlay patches.
Table 1-6 October 2024 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 37087476 |
PSU Coherence (12.2.1.4.23) | 37049907 |
ADF Bundle Patch | 37028738 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35965629 |
OPSS for WebLogic Server | 36316422 |
WebLogic Opatch (13.9.4.2.17) | 28186730 |
Fusion Middleware Platform SPU | 36789759 |
Fusion Middleware Thirdparty Bundle Patch | 37103277 |
JDBC 19.24 Bundle Patch | 36926636 |
OSS 19C Bundle Patch | 37096063 |
Cloning SPU for WLS/FMW 12.2.1.4.0 | 37056593 |
Fusion Middleware Control SPU | 36946553 |
Oracle Web Services Manager (OWSM) Bundle Patch | 37035947 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 36851321 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 36964687 |
Oracle Data Integrator Bundle Patch | 37107206 |
Overlay patches |
30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) 36603199 (Cross domain transaction between Kubernetes domain and on-premises domain failing intermittently with rollback exception) 36627663 (RJVM Diagnostic Notification Messages in the Managed server logs) |
Table 1-7 lists the July 2024 CPU and Overlay patches.
Table 1-7 July 2024 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 36805124 |
PSU Coherence (12.2.1.4.22) | 36725924 |
ADF Bundle Patch | 36700543 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35965629 |
OPSS for WebLogic Server | 36316422 |
WebLogic Opatch (13.9.4.2.16) | 28186730 |
Fusion Middleware Platform SPU | 33093748 |
Fusion Middleware Thirdparty Bundle Patch | 36770738 |
Fusion Middleware Control SPU | 34542329 |
Fusion Middleware JDBC | 33791062 |
Oracle Web Services Manager (OWSM) Bundle Patch | 36769312 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 36553894 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 36741053 |
Oracle Data Integrator Bundle Patch | 36799120 |
Overlay patches |
36842950 (Merge request on top of WLS PSU 12.2.1.4.240704 for bugs 27184424 28334768) 36603199 (Cross domain transaction between Kubernetes domain and on-premises domain failing intermittently with rollback exception) 30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) 35363703 (Fix for logging about non-existing managed servers in dynamic cluster. This is applicable only for OSM cloud native deployments.) |
Table 1-8 lists the April 2024 CPU and Overlay patches.
Table 1-8 April 2024 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 36440005 |
PSU Coherence (12.2.1.4.21) | 36410345 |
ADF Bundle Patch | 36348444 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35965629 |
OPSS for WebLogic Server | 36316422 |
WebLogic Opatch (13.9.4.2.15) | 28186730 |
Fusion Middleware Platform SPU | 33093748 |
Fusion Middleware Thirdparty Bundle Patch | 36468190 |
Fusion Middleware Control SPU | 34542329 |
Fusion Middleware JDBC | 33791062 |
Oracle Web Services Manager (OWSM) Bundle Patch | 36402397 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 36187017 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 36349529 |
Oracle Data Integrator Bundle Patch | 36487966 |
Overlay patches |
28334768 (DMS Metric table) 27184424 (Stuck thread) 30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) 35363703 (Fix for logging about non-existing managed servers in dynamic cluster. This is applicable only for OSM cloud native deployments.) |
Table 1-9 lists the January 2024 CPU and Overlay patches.
Table 1-9 January 2024 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 36155700 |
PSU Coherence (12.2.1.4.20) | 36068046 |
ADF Bundle Patch | 36074941 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35965629 |
OPSS for WebLogic Server | 33950717 |
WebLogic Opatch (13.9.4.2.14) | 28186730 |
Fusion Middleware Platform SPU | 33093748 |
Fusion Middleware Thirdparty Bundle Patch | 36086980 |
Fusion Middleware Control SPU | 34542329 |
Fusion Middleware JDBC | 33791062 |
Oracle Web Services Manager (OWSM) Bundle Patch | 35868571 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 35671137 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 36034300 |
Oracle Data Integrator Bundle Patch | 35861909 |
Overlay patches |
28334768 (DMS Metric table) 27184424 (Stuck thread) 30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) |
Table 1-10 lists the October 2023 CPU and Overlay patches.
Table 1-10 October 2023 CPU and Overlay Patches for Fusion Middleware
Component | Patch Number |
---|---|
PSU for WLS | 35893811 |
PSU Coherence (12.2.1.4.19) | 35778804 |
ADF Bundle Patch | 35735469 |
Additional Fix for ADF Bundle Patch | 34809489 |
ADR for WebLogic Server | 35476067 |
OPSS for WebLogic Server | 33950717 |
WebLogic Opatch (13.9.4.2.14) | 28186730 |
Fusion Middleware Platform SPU | 33093748 |
Fusion Middleware Thirdparty Bundle Patch | 35882299 |
Fusion Middleware Control SPU | 34542329 |
Fusion Middleware JDBC | 33791062 |
Oracle Web Services Manager (OWSM) Bundle Patch | 35868571 |
Remote Diagnostic Agent (RDA) for WebLogic Server 12.2.1.4.0 | 35671137 |
Fusion Middleware Compatibility Patch for JDK8 | 34065178 |
WebCenter Core Bundle Patch | 35751917 |
Oracle Data Integrator Bundle Patch | 35861909 |
Overlay patches |
28334768 (DMS Metric table) 27184424 (Stuck thread) 30319071 (User group association) 31169032 (Export JMS Messages) 31569708 (JMS Orphan Destination routing) 32262098 (3 JDBC Stores in Fusion application pod have no owner) 31676526 (ADB Wallet Dir Connection String Support) 30540494 (RCU creation with RAC for ADB) 30754186 (Improve efficiency for RCU SQL) |
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Communications Order and Service Management Compatibility Matrix, Release 7.5
F60013-06