Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.1
This document contains the release notes for Oracle Insurance Gateway Patch 4.23.1.0.1.
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. |
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.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 |
---|---|---|---|---|
35855228 |
OIG-3419 |
BP |
Dynamic logic cache reloads every time on business cache invalidation even if there is no dynamic logic update |
|
Description: |
Dynamic logic cache uses a business process cache which is invalidated on any change in configuration entities (that implements ProcessCacheInvalidating) even though there is no change in dynamic logic itself . On invalidation of the cache , byte code is loaded again for all the dynamic logic which is CPU intensive and can slow down other processes running in parallel during the class loading . |
|||
Resolution: |
The cache invalidation and reloading happens only on change in dynamic logic entity. |
|||
35854453 |
OIG-3412 |
BP |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
|
Description: |
The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time. |
|||
Resolution: |
Load the system property from the database if the loading of system properties is not completed. If loading of system property is completed then load from cache. |
|||
35722659 |
OIG-3355 |
BP |
Exchange fails with NPE at step level timeout when the status of the process is failed |
|
Description: |
When the notification endpoint is not set for OIG, and the external process failed, the exchange fails with Null Pointer Exception at step-level timeout |
|||
Resolution: |
The NullPointerException is handled in this scenario |
|||
35716436 |
OIG-3347 |
BP |
Agent Configuration Integrations - Page is not opening |
|
Description: |
When we click on 'Add' button under tab 'Agent Configuration Integrations' of following pages, the page is not loading completely:
|
|||
Resolution: |
Agent Configuration page doesn’t give console error when clicking on 'Add' button under tab Agent Configuration Integrations |
|||
35731611 |
3-33723635841 |
OIG-3359 |
BP |
Recovery of failed exchanges with Time Guard fails with Optimistic Locking Exception |
Description: |
For Failed and Timed Out exchanges with auto-recovery configured and incomplete Time Guard tasks, recovery operation on exchange fails with Optimistic Locking Exception. |
|||
Resolution: |
For Failed and Timed Out exchanges, incomplete Time Guard tasks are marked as Dismissed. Recovery operation on Failed and Timed Out exchanges with auto-recovery configured no longer fail with Optimistic Locking Exception. |
|||
35958842 |
OIG-3471 |
BP |
Dynamic Logic is not compiled at startup |
|
Description: |
Dynamic logic was not always recompiled at application startup. |
|||
Resolution: |
All dynamic logic is now recompiled at startup. |