Release Notes for Oracle Insurance Gateway Patch 3.20.3.0.5
This document contains the release notes for Oracle Insurance Gateway Patch 3.20.3.0.5.
Version compatibility: Oracle Insurance Gateway Release 3.20.3.x is only compatible with other Oracle Health Insurance applications release version 3.20.3.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.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 |
---|---|---|---|---|
32441805 |
3-25027449221 |
OIG-1682 |
BP |
OIG Access Restriction 'IG0004' is missing in 3.20.3.0.x release |
Description: |
IG0004 is removed in 3.20.3 release and deprecated. IG0004 should be removed through liquibase so that customers won’t get error while migrating |
|||
Resolution: |
A liquibase script is provided to remove ACCESS RESTRICTION 'IG0004' since it is not used anymore from 3.20.3 release |
|||
32467138 |
OIG-1692 |
BP |
Boilerplates are missing from seeddata in 3.20.2.0.0 release |
|
Description: |
In release 3.20.2.0.0 the below listed boilerplates are deleted from seed data. DOMAIN_DESTINATIONTYPEGATEWAY_REST, DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT, DOMAIN_TOKENVALIDATIONMETHOD_OAM_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_OAUTH2_ENDPOINT, DOMAIN_TOKENVALIDATIONMETHOD_JWKSET, DOMAIN_DESTINATIONTYPEGATEWAY_FILEUPLOAD, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_SINGULAR, DOMAIN_DESTINATIONTYPE_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB, DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB, DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM, DOMAIN_DESTINATIONTYPEGATEWAY_SFTP, DOMAIN_DESTINATIONTYPEGATEWAY_AGENT, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPFINISH, DOMAIN_AGENTCONFIGTYPE_OUT-FOLDER, DOMAIN_AGENTCONFIGTYPE_IN-FOLDER, OIG_GATEWAYAGENTCONFIGURATIONINTEGRATION_TITLE_PLURAL, CUSTOM_EXCHANGE_FIELD_PAYLOAD, DOMAIN_DESTINATIONTYPEGATEWAY_SOAP, DOMAIN_INTEGRATIONSUBSTEP_SUBFLOWSTEPSTART, DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS |
|||
Resolution: |
The following boilerplates are added back in 3.20.3.0.3 patch since they are still used in OHI. DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM |
|||
32468706 |
OIG-1693 |
BP |
Task is stuck in 'PROCESSING' status if the node leaves the cluster |
|
Description: |
Currently if a node fails, its tasks are not failover-ed to other nodes, they remain in status Processing. |
|||
Resolution: |
In case a node fails, all its tasks will be failover-ed correctly to the other nodes with this fix. |
|||
32446318 |
OIG-1683 |
CMT - Error while importing HICAPS/HEALTHPOINT Integrations |
||
Description: |
Integrations in OIG have a unique key on type, code and version. Config Migration Import was not taking care of the composite unique key and hence the bug. |
|||
Resolution: |
Config Migration Import is changed to take the composite unique key in account while importing. |