Release Notes for Oracle Insurance Gateway Patch 3.22.2.0.10

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

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

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.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

35482174

OIG-3171

BP

Subflows : Main exchange status is not set to Timed Out when exchange timeout is reached

Description:

When the exchange-level timeout occurs for an exchange with subflows, the main exchange stops processing after the set time period. However, it stays in the status 'WaitingForSubExchangesToFinish' (WS) and does not change to 'TimedOut' (T).

Resolution:

When the exchange-level timeout occurs for an exchange with subflows, the main exchange processing stops, and the exchange status changes from 'WaitingForSubExchangesToFinish' (WS) to 'TimedOut' (T).

35589854

OIG-3239

BP

Exchange is not marked Timed Out on receiving notification after exchange timeout

Description:

When the exchange level timeout occurs during the Receive Notification step, the exchange is not marked Timed Out immediately after receiving a notification. Instead, it waits till step-level timeout occurs and then times out the exchange.

Resolution:

When the exchange level timeout occurs during the Receive Notification step, the notification is logged in the step payload. The exchange stops processing, and is marked Timed Out immediately.

Issues that were backported in previous Release / Patch

No backports.