Release Notes for Oracle Insurance Gateway Patch 3.22.1.0.9

This document contains the release notes for Oracle Insurance Gateway Patch 3.22.1.0.9.

Version compatibility: Oracle Insurance Gateway Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.1.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

No enhancements.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

35382405

3-31977844691,3-32158818851

OIG-3103

BP

HTTP api metadata caches url from the first api request to get the metadata of a resource

Description:

When metadata of any entity is accessed first time using generic API, it’s generated with absolute URLs and gets cached. Subsequent requests to the same metadata is served from the cache. In multi-node system, accessing metadata from different nodes will return already cached metadata and base URL (hostname and port) mentioned there won’t match with current requests' base URL.

Resolution:

Instead of caching generic API metadata request response with absolute URLs, it gets cached by replacing base URL by placeholder. While returning response for each generic API metadata, cached metadata is processed and placeholder gets replaced by base URL of current request.

Issues that were backported in previous Release / Patch

No backports.