1 Feature Summary
This chapter describes the feature enhancements in this release.
Note:
The non-sequential version number of this Oracle Retail application is intentional.Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Process Orchestration and Monitoring Cloud Service update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module 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.
-
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.
Table 1-1 Noteworthy Enhancements
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
Job Agent |
Large |
Disabled |
Yes |
|
|
User Interface |
Small |
Enabled |
No |
Hybrid CFS and GBUCS Deployments
As the RGBU prepares for customers to migrate from GBUCS to CFS, there is a need for a transitional period where POM and one or more POM-using applications have migrated to CFS while other POM-using applications remain behind on GBUCS until they are also ready for migration. In POM version 21.0.003, POM supports this sort of hybrid deployment. In version 19.1.010, POM was modified to deploy the necessary POM Agent on GBUCS which will work with POM on CFS.
Once the hybrid setup is complete, customers who currently call POM APIs need to switch the endpoint authentication mode from Basic Auth to OAuth. Customers need to refer to the ‘Invoking POM Services Using OAuth’ chapter of the ‘POM 21.0.003 Implementation Guide’ for information regarding using the OAuth mode of authentication when calling POM APIs.
Once the hybrid setup is complete and an application is ready for migration to CFS, Oracle will configure POM to switch from GBUCS to CFS.
Execution Engine Popup Screen Changes
The Execution Engine popup screen is accessed from the Batch Monitoring screen’s right status sidebar by clicking on the Execution Engine Admin link. In the current version of POM, an administrator has the ablity to see the engine’s status, change the engine’s configuration and start or shut down the engine. In version 19.1.010, this popup is simplified to only show the engine’s configuration. Accordingly, the link to the popup has been changed from Execution Engine Admin to Execution Engine Config.
The following changes have also been made to the popup:
-
The configuration (Execution Service Polling Interval, Monitoring Service Polling Interval, and Thread Pool Size) has been modified from being updatable to being read-only. The default configuration setting has proven to be stable and requires no post-deployment changes. Oracle will always be able to change this configuration, if it is ever needed.
-
The Status was removed, as the Execution Engine should always be ready to execute tasks.
-
The Start and Shutdown buttons were removed, as the Engine’s state is now strictly system-managed rather than administrator-managed.