1 Feature Summary
This section describes the feature enhancements in this release.
Supported Retail Integration Products
The Oracle Retail Integration Cloud Service (RICS) is composed of the Oracle Retail Integration Suite of products that are cloud deployable for a customer's integration to Oracle Retail applications and the customer's on-premises or hybrid configurations of third-party applications.
The integration products supported and mentioned in this document are the same as the generally available on-premises versions of the following applications:
-
Oracle Retail Integration Bus (RIB)
-
Oracle Retail Bulk Data Integration (BDI)
-
Retail Financial Integration (RFI)
-
Universal service Mapper (USM).
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module impacted associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore, the potential impact to users is moderate.
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.
-
Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
RIB, BDI, USM, TOOLS, RFI |
Small |
Y |
N |
|
|
RIB, BDI, USM, TOOLS, RFI |
Small |
Y |
N |
|
|
RIB, BDI, USM, TOOLS, RFI |
Small |
Y |
N |
|
|
RIB, BDI, USM, TOOLS, RFI |
Small |
Y |
N |
|
| Infrastructure and Security Compliance | ||||
|
RIB, BDI, USM, TOOLS, RFI |
Large |
Y |
N |
|
| Documentation | ||||
|
RIB, BDI, USM,Tools,RFI |
N/A |
Y |
N |
|
New and Updated Options
RICS Deprecation Readiness Usage Report
A new RICS Deprecation Readiness Usage Report has been introduced for internal administrative use to support deprecation readiness activities. The report is generated automatically by a newly added scheduled job (cron) and consolidates usage information across the following RICS components: RIB, BDI, RFI and USM.
For each component, the report derives relevant usage metrics by analyzing its respective logs and operational data and generates a consolidated view of component usage to assist in deprecation planning and readiness assessments.
Standardize Weblogic Log Format as per Gold Standard
Standardized WebLogic application logging has been implemented for all WebLogic application logs. The logging format adheres to the Gold standard, ensuring consistency across applications and enabling improved log analysis, monitoring, and operational support.
Standardize Tomcat Log Format as per Gold Standard
This ensures consistency and traceability across all Tomcat deployments in compliance with logging standards.
OCI Direct Connect Support in RICS
Transitioning from DBaaS-provisioned Autonomous Databases (ADBs) to provisioning ADBs directly through OCI. This approach provides greater control over the provisioning and management process and aligns with the DBaaS-recommended model for Autonomous Database provisioning going forward.
DBaaS will continue to play a role by provisioning the Autonomous Database Infrastructure (ADBi), including the required networking components such as subnets. Once the ADB infrastructure is in place, RGIU will provision and manage the Autonomous Database instances within that environment.