Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.2

This document contains the release notes for Oracle Insurance Gateway Patch 4.23.1.0.2.

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.

Enhancements

ID Summary Patch

NXT-28569

Migration of credentials from OPSS to ohistore

4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore.

Documentation Links:
Developer Guide - Credentials
Developer Guide - Keystores

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Post-Deploy phase

Note: This is only required while upgrading to 4.23.2 and migrating from opss/vault to ohistore.

  1. Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "true". This property will allow the end user to access the endpoint to export the secrets i.e. keystore and credentialstore.

  2. To disable exports of the keystore and Credentials, set this property "ohi.credential.migration.enabled" value to "false".

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

NXT-28569

Added

Export Keystores

Export existing keystores

NXT-28569

Added

Export Credentials

Export existing credentials

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

35775565

OIG-3384

Exchanges with autoRecovery which fail generate stacktraces with NullPointerException

Description:

When a process invoked by an integration with autoRecovery true results in failure, the exchange fails as expected. In this case, it is also generating stacktraces with NullPointerException.

Resolution:

The NullPointerException no longer occurs in this case.

36156181

3-35334218641

OIG-3565

Agent fails to start up with logging enabled

Description:

When trying to start the agent with property "agent.rest.client.logging" enabled, a ClassNotFoundException is thrown.

Resolution:

The agent succesfully starts up with the logging property enabled.

Issues that were backported in previous Release / Patch

No backports.