Release Notes for Oracle Insurance Gateway Patch 3.22.2.0.3
This document contains the release notes for Oracle Insurance Gateway Patch 3.22.2.0.3.
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-2764 |
Reducing Application Clients Configuration This enhancement enables a user to re-use application clients, configured in the Authorization Server, across OHI REST clients. |
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the .existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install
, make a copy ofohi_install.cfg.template
and name itohi_install.cfg
. -
Edit
ohi_install.cfg
to contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
35164729 |
3-32256677181 |
OIG-3029 |
BP |
Propagate error code from database erros |
Description: |
When OIG encounters a database exception, it responds by logging a generic message. The original exception is lost. |
|||
Resolution: |
Propagate the database exception into the error log. |
|||
35215831 |
3-32256677181 |
OIG-3053 |
BP |
Update passing of properties for a sub exchange as a clob |
Description: |
Starting a sub flow with properties of a length of more then 400 characters, failed the sub flow creation on a database error. |
|||
Resolution: |
The properties for the sub exchange are passed as a clob instead of a string. |
|||
35237996 |
3-30389406341 |
OIG-3057 |
BP |
Event payload CLOB is incorrectly handled as String |
Description: |
The payload of an Event is incorrectly handled as a String although stored as CLOB in the database. |
|||
Resolution: |
The payload of an Event is read from the database using ClobReader in a streaming fashion and later converted to String. In case reading an event fails, the event is skipped and can be reread later using the method readUnhandledEvents(). An error message is also added in logs with the skipped Event Id |