Release Notes for Oracle Insurance Gateway Patch 3.22.1.0.5
This document contains the release notes for Oracle Insurance Gateway Patch 3.22.1.0.5.
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. |
Enhancements
ID | Summary | Patch |
---|---|---|
OIG-2731 |
Integration Version This enhancement expands the integration version feature to enable better support for (migration of) updates to integration configuration. |
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
Additional Upgrade Steps for Installation
The following phases are defined:
|
Stage: pre-upgrade
1) Action: run the following script that checks existing integrations where integration version is not null.
select id ,code, version, type from oig_integrations_b where version is not null;
If integrations with version values are present, nullify the version attribute of the integrations.
If this leads to a unique key violation, perform the following steps:
-
update the code of the integration version(s), eg by prefixing the code with the version
-
nullify the version attribute
-
once the upgrade is performed
-
add version
-
update the integration code to the original code
-
This is needed because the version datatype is changed from string to number during upgrade.
Web Services
Ref | Action | Description |
---|---|---|
OIG-2731 |
Added |
api/exchanges Added the option to invoke an exchange for a specific integration version using HTTP header ohi-integration-version |
OIG-2731 |
Modified |
generic/integrations updated datatype of version attribute from string to number(5) |
Dynamic Logic
Ref | Action | Description |
---|---|---|
OIG-2731 |
Modified |
Read events predefined methods Predefined methods for reading events now include integration matching logic that compares integration code instead of integration id. Predefined methods: readUnhandledEvents() readEvents() readEvents(Timestamp from, Timestamp to) When these pre-defined methods are used in dynamic logic it is required to re-compile the groovy logic with invalidateall operation of dynamic logic IP. |
UI Changes
Ref | Action | Description |
---|---|---|
OIG-2731 |
Modified |
Invoke Exchange Included Integration Version in Integration dropdown when invoking an exchange through the User Interface |
OIG-2731 |
Modified |
Integrations Added Version dropdown 'Create New Version' button that prepopulates a new integration payload based on the integration in context/viewed Added attribute 'version' to floorplan Added version to floorplan as a label |
OIG-2731 |
Modified |
Select Migration Sets Included version in pop-up page to select migration items |