Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.8

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

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

Additional Upgrade Steps

This section describes the steps that a functional application manager will take during the upgrade. These steps to be performed as an application user who is authorized to access the IPs.

Post-Deploy Phase

  1. Upgrade OHI Agent

    Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.

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

Ref Action Description

OIG-3869

Modified

deliverByAgent step

If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

Bug Fixes

BugDB SR Internal Summary

36733331

3-37002072411

OIG-3869

Exchange incorrectly marked completed during recovery without file delivery to agent

Description:

When an exchange containing a 'deliverByAgent' step fails and is subsequently recovered after resolving the underlying issue, the exchange is incorrectly marked as completed without actually delivering the file via the Agent. This behavior is also observed in sub-exchanges.

Resolution:

  • Delivery by Agent step is now split in three sub steps i.e. check agent availability, delivery by agent and receive notification.

  • Exchange status will now be 'waitingForExternalSystem' instead of 'waitingForAgentToSignoff' during the delivery by agent process.

  • Agent now uses notification endpoint to send the response back to Oracle Insurance Gateway instead of using the sign off and failure integration points.

  • It is now possible to configure 'timeAllowed' type config for the delivery step (using agent) within an integration.

  • For the integrations responsible for delivering large file using an Agent, it is recommended to set a higher allowed time for the delivery step to prevent time outs (default wait time is 5 minutes).

  • If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

37438058

3-34889024331

OIG-4174

NullPointerException upon exchange recovery

Description:

When an activity step fails to return an appropriate response, the exchange can come into a state where recovery is impossible due to a NullPointerException occurring.

Resolution:

If upon recovery the activity notification does not exist, it is fetched with the location header

37161035

OIG-4072

Exchange can be invoked with only retrieve access on exchanges.

Description:

Exchange can be invoked with only retrieve access on exchanges.

Resolution:

Exchanges cannot be invoked with retrieve access alone on exchanges and also the tiles to invoke are hidden.

37248665

OIG-4113

Error when attempting to upload files to OIG

Description:

User experiences 406 (Not Acceptable) Error when attempting to upload files to OIG

Resolution:

It is possible to upload files in OIG without any error.

37093041

3-37860226571

OIG-4061

NPE in Eclipse Integrations

Description:

NPEs are raised for some eclipse integrations when the token is not retrieved successfully

Resolution:

There was a delay in the synchronization process between the keystore and the cache, which could lead to both being out of sync temporarily. The synchronization process has changed to make them consistent.

Issues that were backported in previous Release / Patch

No backports.