Release Notes for Oracle Insurance Gateway Patch 3.22.2.0.7

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

Version compatibility: Oracle Insurance Gateway Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.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

ID Summary Patch

AUT-2744

Improved memory management

The Application Health Check status 429, informs the load-balancer or client programs that no new requests should be sent anymore, when the free memory goes below the threshold limit as set by the system properties. When the memory state becomes low, lower, or critical, then depending on the state either no new background processing tasks are started, or they are rejected, or terminated.

OIG-2617

Recover timed-out ayschronous exchanges

This enhancement expands the recovery feature to timed-out exchanges to support scenarios where the recovery process by starting a new exchange is not possible or undesirable.

Use Case: Premium Billing Integration An exchange is timed out during financial message transformation. At this point it is not possible to start a new exchange for the same integration because OHI Policies considers the financial messages as handled and will therefore not send the same financial messages to OIG again. Instead, the time out value for the dynamic logic is increased and the timed-out exchange is recovered.

Documentation Links:
Developer Guide
Operations Guide

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

35452349

3-33108720861

OIG-3148

BP

Failure in enabling dynamic logic cache across the cluster nodes

Description:

Dynamic logic executables cache wasn’t getting enabled across cluster nodes after CMT import.

Resolution:

Ensured to have all the prerequisites available to enable cache in other nodes

35328581

OIG-3093

BP

The number of items in shared Eclipselink caches is maximized

Description:

The shared Eclipselink caches could grow unlimited, which resulted in memory shortage. To prevent that, the number of items in such a cache is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size.

Resolution:

The number of items in shared caches is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size.

35403886

3-33001662451

OIG-3112

BP

Additional logging in token retriever code

Description:

Logger were missing in the code where PRODA token is retrieved

Resolution:

Added logger to code catering to PRODA token retrieval.

Issues that were backported in previous Release / Patch

No backports.