Release Notes for Oracle Insurance Gateway Patch 4.23.2.0.1
This document contains the release notes for Oracle Insurance Gateway Patch 4.23.2.0.1.
Version compatibility: Oracle Insurance Gateway Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.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. |
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
Configuration Properties
Ref | Action | Description |
---|---|---|
OIG-3739 |
Added |
ohi.oauth.token.jwt.assertion.param.name Name of JWT assertion parameter used in OAuth token request. It could be different across OAuth server. Default value is "assertion" |
Web Services
Ref | Action | Description |
---|---|---|
OIG-3739 |
Added |
Generic API for OAuthParameter Introduced generic APIs to manage OAuth parameters. Refer /generic/oauthparameters/metadata to know available endpoints to manage OAuthParameter entity |
OIG-3739 |
Modified |
oauthassertionjwtbearergrantconfigurations Supports configuration of OAuth parameters through oAuthClientParameters |
OIG-3739 |
Modified |
oauthclientcredentialsgrantconfigurations Supports configuration of OAuth parameters through oAuthClientParameters |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
36281943 |
3-35703331611 |
OIG-3674 |
OHI Agent will not start when more than 50 agent configurations are defined |
Description: |
If there are more than 50 agent configurations defined in OIG, the agent gets stuck in an endless loop at startup. |
||
Resolution: |
The agent now finds all agent configurations and starts succesfully after. |
||
36331425 |
3-35676286031 |
OIG-3694 |
Add loggers at token refresh code |
Description: |
Add Additional loggers in agent code during token refresh. |
||
Resolution: |
Added loggers in agent code during token refresh. |
||
36323296 |
3-35406309051 |
OIG-3689 |
Add additional loggers when agents are down |
Description: |
Add additional loggers in agent code when it is down. |
||
Resolution: |
Implemented additional loggers in agent code when it is down |
||
36209637 |
3-35422276881 |
OIG-3632 |
Query Step failed in Subflows |
Description: |
When a Subflow configured with a Query step is executed, the Exchange fails with a Null Pointer Exception. |
||
Resolution: |
When a Subflow containing a Query step is executed, the exchange executes successfully without a Null Pointer Exception. |
||
36250783 |
OIG-3659 |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
|
Description: |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
||
Resolution: |
The length of OHI_ID_ARRAY database type is updated to 19 |
||
36270706 |
OIG-3670 |
Unable to edit values in drawer when a field is configured as deeplink |
|
Description: |
It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save |
||
Resolution: |
Edit works fine in Deeplink drawers now and also the values are saved properly on the resource configured as deeplink |
||
36519150 |
3-36337751321 |
OIG-3768 |
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. |
||
36410463 |
3-34612052061 |
OIG-3725 |
JWT bearer grant type is not working |
Description: |
OHI supports both client_credentials and urn:ietf:params:oauth:grant-type:jwt-bearer (shortly referred as JWT bearer) grant types in OAuth, however JWT bearer grant type is not working as expected. |
||
Resolution: |
Fixed logical issues in code to make it working |
||
36416548 |
3-34612052061 |
OIG-3739 |
OAuth parameters should be configurable |
Description: |
OHI product supports only standard OAuth parameters. As its value/name can deviate across OAuth server, OHI application isn’t able to establish connection with OAuth server. |
||
Resolution: |
Introduced capability in OHI product to define custom OAuth parameters. These parameters can be reused across different OAuth clients later. |
||
36309143 |
OIG-3685 |
Exchange gets stuck in collect messages step when there are more than 50 messages to collect |
|
Description: |
In an exchange which invokes an OHI process, if there are more than 50 activity messages to collect, it will keep collecting the same 50 messages over and over, rather than paginate to get the rest of the messages. |
||
Resolution: |
The exchange now correctly paginates through the collected messages and collects all of them. |
||
36204177 |
3-34786906091 |
OIG-3622 |
Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall API is invoked |
Description: |
Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed. |
||
Resolution: |
Dynamic logic byte code is now loaded at the startup of non-master nodes if the invalidateall API was invoked in master node. |
||
36533598 |
3-34871101921 |
OIG-3770 |
Invoking exchange with filename containing diacritics corrupts created datafile name |
Description: |
Invoking exchange with file upload, where the filename contains diacritics, erroneously transforms the filename to some other characters. |
||
Resolution: |
|||
36377464 |
OIG-3713 |
Save and Cancel shortcuts aren’t working for create HRR pages |
|
Description: |
Save and Cancel shortcuts aren’t working for create HRR pages |
||
Resolution: |
Save and Cancel shortcuts will work for create HRR pages also now |
||
36368179 |
OIG-3704 |
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. |