See ASAP Compatibility Matrix for a full list of software requirements.

This release includes the following features and enhancements:

• High Availability in Order Balancer

• Support for Secured Communication (TCPS) Access to Oracle Database

• Order Control Application- Searching Orders without Date Range

• Order Control Application- Drop-down List for Parm Label in the Search Criteria

You can now install multiple Order Balancer instances in ASAP traditional and cloud native deployments for high availability. With multiple Order Balancer running, when an instance goes down, the other Order Balancer instances routes the incoming orders to the available ASAP instances in the environment.

For more information about high availability in Order Balancer, see ASAP System Administrator's Guide.

High availability in Order Balancer is also supported in ASAP cloud native deployments. For more information, see ASAP Cloud Native Deployment Guide.

You can now configure Secured Communication(TCPS) Access from ASAP to Oracle Database. This allows ASAP to communicate with the database over a secure channel.

In the Order Control Application (OCA), you can now search orders using any query criteria without specifying the start date and end date. In OCA, in the Work Order Query window, a new check box Use Date Range is added which is selected by default to maintain the existing search criteria. Selecting the check box includes the Start Date and End Date fields in the search criteria. The start date has the default value as the current date and the end date has the default value as the next day of the current date. For example, if the start date is defaulted to the current date 19/12/2022, the end date is 20/12/2022. You can enter the end date to be any date within a week from the start date. If you enter the end date more than a week from the start date, an appropriate error message is displayed.

Deselect the check box Use Date Range to exclude the start date and end date in the search criteria. Deselecting the check box disables the Start Date and End Date fields. You can enter any of the fields to search for the work orders without the date range. All the fields including Use Date Range check box are disabled when WO ID and Parent WO ID are entered.

In the Order Control Application (OCA), in the Work Order Query window, the Parm Label field is now displayed as a drop-down list. The Parm Label field defaults to have no value. You can enter any value in the Parm Label field or click the drop-down list to choose a parameter from the list. The drop-down list displays all the parameters for all the Common Service Description Layers (CSDLs) irrespective of the CSDL selected in the CSDL drop-down list.

This release includes the following features and enhancements:

• Automatically Create ASAP Docker Image and Order Balancer Docker Image

• Restarting the Failed ASAP Instances Automatically

• Zero Downtime Upgrade for Order Balancer in Traditional Deployment

• New Features Supported by ASAP Order Balancer REST Services

You can now automatically build the ASAP Docker image and the Order Balancer Docker image using a single script. You can build multiple ASAP Docker images by updating the asap.properties file accordingly.

For more information, see "Creating the ASAP Cloud Native Image" and "Creating the Order Balancer Cloud Native Image" in ASAP Cloud Native Deployment Guide.

ASAP now supports restarting the ASAP instances automatically to restore the services when an ASAP instance fails. Kubernetes uses liveness and readiness probes to find the failed ASAP instances and restart those instances to restore the services automatically. You configure the readiness and liveness probes in Kubernetes in $ASAP_CNTK/charts/asap/values.yaml file.

For more information on readiness and liveness probes, see "Configuring the Failed ASAP Instances to Restart Automatically" in ASAP Cloud Native Deployment Guide.

In a traditional deployment, you can now upgrade Order Balancer by continuously processing the order requests without any disruption. A newer version of Order Balancer can be installed while the older version is still running. The new incoming order requests are processed by the newer version of Order Balancer after installation, while the in-progress order requests are processed by the older version of Order Balancer. After the in-progress order requests are processed, the older version of Order Balancer is retired and then deactivated. You can undeploy the older version completely or roll back to the older version, if the upgrade fails.

For more information on upgrading Order Balancer, see "Updating and Redeploying Order Balancer" in ASAP System Administrator's Guide.

You can use REST APIs to view and update data about the ASAP member instances in Order Balancer. REST services now support the following new features:

• Add ASAP member instance: Adds the ASAP instance to Order Balancer.

  HTTP Request Type: POST

  URI Path: /ASAPOB/asapinstances

• Remove ASAP member instance: Removes the ASAP instance from Order Balancer for the given instance ID.

  HTTP Request Type: DELETE

  URI Path: /ASAPOB/asapinstances/{instanceid}

For more information on supported REST Services, see "Accessing and Updating Order Balancer using REST APIs" in ASAP System Administrator's Guide.

ASAP 7.4 introduces the ability to deploy, manage, and monitor ASAP in a cloud native environment using container images, Kubernetes clusters, Prometheus, Grafana, and other components.

ASAP cloud native provides a toolkit that includes utility scripts, Helm charts, default configuration files, and samples required to deploy ASAP in a Kubernetes environment, following standard practices such as versioned Helm releases.

For instructions on planning and setting up your cloud native environment, see ASAP Cloud Native Deployment Guide.

For information about the supported versions of required and third-party software, see ASAP Compatibility Matrix.

For information about the differences between ASAP cloud native and traditional deployments, see "Differences Between ASAP Cloud Native and ASAP Traditional Deployments".

ASAP now supports environments with multiple ASAP instances for high availability using the new Order Balancer component. With Order Balancer managing multiple independent ASAP instances, the load is distributed and balanced. You can also deploy new ASAP instances with new cartridges in the same environment without down time. With Order Balancer managing multiple ASAP instances, when an instance goes down, the incoming orders are routed to the other available running instances in the environment.

For more information about Order Balancer and how to set up Order Balancer, see ASAP System Administrator's Guide.

Order Balancer is also supported in ASAP cloud native deployments. For more information, see ASAP Cloud Native Deployment Guide.

You can configure Prometheus to view ASAP metrics. To view ASAP metrics using Prometheus, you configure a scrape job in Prometheus. ASAP metrics scraped by Prometheus can be made available for further processing and visualization using Grafana. ASAP exposes metrics via Servlet APIs. For details about configuring Prometheus for ASAP metrics and viewing metrics in Grafana, see "Managing ASAP Metrics" in ASAP System Administrator's Guide.

You can also use Prometheus and Grafana to view ASAP metrics in cloud native deployments. For more information, see ASAP Cloud Native Deployment Guide.

ASAP 7.4 uses Oracle Analytics Server for generating reports. See ASAP Compatibility Matrix and ASAP Order Control Application User's Guide for more information.

This release of ASAP contains enhancements and bug fixes.

Table 1-1 lists the fixed issues in ASAP 7.4. For fixed issues in ASAP 7.4.0.1 patch (34475066), see the corresponding patch Readme files available on the My Oracle Support website:

https://support.oracle.com/.

This section lists the known issues in this release of ASAP.

Table 1-2 lists and describes the known problems in ASAP 7.4.

The following features are not supported or have been deprecated in the ASAP 7.4 release.

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.