Release Notes for Oracle Insurance Gateway Patch 3.22.1.0.6
This document contains the release notes for Oracle Insurance Gateway Patch 3.22.1.0.6.
| 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. |
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 | BP | Summary |
|---|---|---|---|---|
34876914 |
OIG-2888 |
BP |
Resources cannot be searched, when the code starts with 25 |
|
Description: |
For resources having code starting with 25, when we try to search for these resources in the Jet UI, the search never gets completed. When checking the console, the API call is returning a 400 Bad request as a status. |
|||
Resolution: |
Users can now perform a search for resources with the 25% |
|||
34942377 |
OIG-2917 |
BP |
OptimisticLockingException when updating lastlogintimestamp of the user |
|
Description: |
Updating lastLoginTimestamp is controlled by a system property ohi.ws.last.login.update.threshold i.e the lastLoginTimestamp is not updated if the user logs-in multiple times with in the same hour.But if there are concurrent requests next second after this hour, both the API/IP requests try to update the same user record, system throws 500 error in this case. This causes problem in updating the LASTLOGINTIMESTAMP |
|||
Resolution: |
Error thrown by the system is ignored in case there are concurrent requests to update the same user record. The LASTLOGINTIMESTAMP will be set according to the first request that updates the user record amongst all the incoming concurrent requests. |
|||
34511523 |
3-30011124551 |
OIG-2702 |
BP |
Header Key reading should be case insensitive |
Description: |
Headers keys are case-insensitive, whereas exchange properties are case-sensitive. This discrepancy leads to issues while reading properties in dynamic logic or in the code. |
|||
Resolution: |
The exchange properties are case-insensitive now. |
|||
34863755 |
3-31424455971 |
OIG-2884 |
BP |
Additional logging in case of non 20x response in a delivery step |
Description: |
If delivery fails, the exchange log for the failure only shows the HTTP status code and not the full response body for message OIG-GATE-011. |
|||
Resolution: |
If delivery fails, the exchange log for the failure will show the response body. |
|||