Release Notes for Oracle Insurance Gateway Patch 3.22.1.0.2

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

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

Enhancements

ID Summary Description Included in Patch

NXT-25000

Resource representation parameters support through request body

Currently, resource representation influencing parameters are passed in "Accept" header of HTTP request. When number of values passed in header increase and all headers size crosses 8K, server rejects HTTP request.

This enhancement provides an alternative way to pass more than 8K data in resource representation parameters. Instead of passing these parameters in HTTP request header, now these parameters get passed in HTTP request body. This capability is available only for "POST /generic/{entitiy_name}/search" API. This version supports passing parameters in header as well as body. In future releases the parameters in header support will be removed, hence passing parameters will be only supported via HTTP request body. Parameter names are same in body as well as header. In body, these parameters are mentioned under "resourceRepresentation". When body includes "resourceRepresentation", it completely ignores header parameters.

Example 1: Resource representation influencing parameters in HTTP request header only

POST http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

Header - Accept : application/json;fields=officeAddress

Body :

{
    "resource": {
        "q": "dateOfBirth.eq('1900-01-01').and.name.eq('Doe')"
    }
}

"officeAddress" field is additionally included in response along with default resource representation

Example 2: Resource representation influencing parameters in HTTP request body only

POST http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

Body :

{
    "resource": {
        "q": "dateOfBirth.eq('1900-01-01').and.name.eq('Doe')"
    },
    "resourceRepresentation": {
        "fields": "officeAddress"
    }
}

"officeAddress" field is additionally included in response along with default resource representation

Example 3: Resource representation influencing parameters in HTTP request body as well as header

POST http://[hostName]:[portNumber]/[api-context-root]/generic/persons/search

Header - Accept : application/json;fields=homeAddress;expand=all

Body :

{
    "resource": {
        "q": "dateOfBirth.eq('1900-01-01').and.name.eq('Doe')"
    },
    "resourceRepresentation": {
        "fields": "officeAddress"
    }
}

"officeAddress" field is additionally included in response along with default resource representation. "homeAddress" and all the dynamic fields/records of person entity won’t be shown in response even though "expand" parameter is available in header. Because, when "resourceRepresentation" is available in body, header parameters are completely ignored.

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)

Ref Action Subject Description

NXT-25000

Deprecated

Remove the support of resource representation parameters in accept header

Resource representation influencing parameters such as fields, expand, response etc. won’t be supported in the header of HTTP request in one of the next major releases. Hence, these parameters should be passed as request body.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34417477

3-29191461591

OIG-2657

BP

OIG Scheduled Integration stopped working

Description:

OIG scheduled integration stopped working, and only resumed after a disable/enable.

Resolution:

Added more logger statements to capture more information around the scheduler. This will help to analyze the issue when it happen.

Issues that were backported in previous Release / Patch

No backports.