Release Notes for Oracle Insurance Gateway Patch 3.22.2.0.2

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

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.

Enhancements

ID Summary Patch

OIG-2593

Improve performance for AS2805_A and AS2805_B integrations

This enhancement improves the performance of the AS2805_A and AS2805_B integrations by allowing users to configure Quote and Authorization integrations without a query step

Documentation Links:
Developer Guide
Developer Guide

OIG-2935

Fusion Job Status Handling

This enhancement supports the following features

  • OIG continues processing for both a failure and a success status of a Fusion import job

  • OIG stores the job status response and makes it available for dynamic logic

  • OIG stores the job ID as a log line

The enhancement is applicable to both FUSIONLOAD and FUSIONSUBM destination.

Documentation Links:
Configuration 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

35190280

OIG-3040

BP

For a failed post process step, a different exchange step is marked as failed

Description:

During an exchange execution, if a Post Process exchange step fails due to a dynamic logic exception, the exchange fails, but a different exchange step is incorrectly marked as failed.

Resolution:

During an exchange execution, if a Post Process exchange step fails, the exchange is marked failed on the correct Post Process exchange step.

35111533

3-32196561261

OIG-2995

BP

Question mark in oig rest destination changed to %3f

Description:

In the path configured in a rest destination containing a question mark sign, it gets converted to its Hex counterpart, i.e. %3F. This causes the formed URL to be incorrect and hence return 404 Not Found when invoked.

Resolution:

Implementation has been done which consumes the path configured in the rest destination as is and does not make any changes to it. This makes sure that the formed URL is correct and hence returns a valid response.

35199134

OIG-3042

BP

Invoking exchange for a null integration version should be possible

Description:

Invoking exchange with null version results in failure in case higher enabled version is present

Resolution:

Invoking exchange with a null version will not result in an error in case a higher enabled version is present. Please note for invoking the null version the header value of ohi-integration-version should "null" string. Further, if this ohi-integration-version contains an invalid value it will lead to OIG-GATE-062 error code.

35203939

OIG-3047

BP

Loggers to see the content of distributed cache at runtime

Description:

No loggers were present to confirm whether the distributed cache storing the member and session information is in sync.

Resolution:

Added logger to confirm whether the distributed cache storing the member and session information is in sync.

35091807

3-32158818851

OIG-2981

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.