Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.5
This document contains the release notes for Oracle Insurance Gateway Patch 4.23.1.0.5.
| 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. |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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 | Summary |
|---|---|---|---|
36519149 |
3-36337751321 |
OIG-3767 |
Agent is picking up files before file upload is complete. |
Description: |
Agent does not check if uploaded file is complete. This can cause errors in the OIG exchange because of incomplete uploaded file. For example, when an enrollment file is uploaded Agent picks it up before the file upload is complete. This can cause errors when uploading to policies. |
||
Resolution: |
Agent now uses Apache Camel to detect change lock on uploaded files. It will wait until file upload process is completed. The file must be atleast 2000ms old before Agent can attempt to acquire the read lock. |
||
36323282 |
3-35406309051 |
OIG-3688 |
Need to add additional loggers when Agents are down. |
Description: |
Added logs in agent code to find out ConnectTimeoutException. |
||
Resolution: |
|||
36088798 |
3-34871101921 |
OIG-3518 |
Using diacritics in filenames during an exchange process corrupts the resulting datafile name |
Description: |
Invoking an exchange with file upload, where the filename contains diacritics, erroneously transforms the filename into different characters. |
||
Resolution: |
By incorporating stranded encoding for UTF-8 and ISO_8859-1 in multiform requests, filename with diacritics in not getting corrupted. |
||
36331423 |
3-35676286031 |
OIG-3693 |
Add addional loggers during agent token refresh . |
Description: |
Added additional loggers during token refresh in agent code. |
||
Resolution: |
|||
36368188 |
OIG-3705 |
Dismissed timeguard tasks are picked up for processing and marked complete after 5 minutes |
|
Description: |
When an exchange fails before it times out, the time guard task (responsible for timing out the exchange) is set to status 'Dismissed', but keeps waiting for its configured time out. If the exchange is recovered before the time guard task is triggered to run, it will time out the recovered exchange too early (as per the original time out). |
||
Resolution: |
Dismissed time guard tasks are now properly dismissed and will not affect quickly-recovered exchanges. |
||