Release Notes for Oracle Insurance Gateway Patch 3.22.2.0.8

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

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-3085

Dynamic Logic Statistics Integration Point enhanced to retrieve statistics ordered by total allocated memory

To retrieve statistics ordered by total allocated memory, use the GET call: http://<host>:<port>/<context-root>/dynamiclogicstatistics/allocatedmemory This call retrieves the dynamic logic statistics ordered by total allocated memory per dynamic logic code. Also, three new statistics are added: totalAllocatedMemory, maxAllocatedMemory, avgAllocatedMemory.

Documentation Links:
Developer Guide - Retrieve Statistics Ordered By Total Allocated Memory
Developer Guide - At the end of the table 3 new statistics

OIG-3110

Increase Exchange Step Sequence to 5 Digits

This enhancement increases the Sequence column on Exchange Steps from 3 digits to 5 digits. This is relevant when a subflow is triggered which creates 1K+ sub-exchanges. For instance, when OHI premium billing is run per group client and there are 1K+ group clients. A sub-exchange will be created per group client, leading to 1K+ sub-exchanges.

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

35474828

3-33308653451

OIG-3165

BP

Fusion Step times out due to Time Guard task for preceding step

Description:

Whenever there is an Extract/Activity/Process step before the Fusion step in an Exchange, the Time Guard task for a preceding step incorrectly marks the Fusion step as TimedOut.

Resolution:

The Time Guard task for the preceding step does not execute in the context of the current Fusion step or change the step status.

35424450

3-32971314811

OIG-3136

BP

Exchanges executed in a sub-flow get stuck in New status

Description:

Exchanges executed in a sub-flow get stuck in New status. Currently, both the synchronous and non-synchronous exchanges are being submitted directly, i.e. without queuing.

Resolution:

Queue non-synchronous exchanges and process synchronous exchanges directly.

Issues that were backported in previous Release / Patch

No backports.