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.

Documentation Links:
Configuration Guide - Setup Overview
Configuration Guide - Sub-flow
Developer Guide - Predefined Methods
Developer Guide - Exchange Integration Point
Operations Guide - Exchange Integration Selection

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.

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:

  1. update the code of the integration version(s), eg by prefixing the code with the version

  2. nullify the version attribute

  3. once the upgrade is performed

    1. add version

    2. update the integration code to the original code

This is needed because the version datatype is changed from string to number during upgrade.

Configuration Properties

This section intentionally left blank.

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)

Data Conversion

This section intentionally left blank.

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

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

No bugs.

Issues that were backported in previous Release / Patch

No backports.