Release Notes for Oracle Health Insurance Product Definition Patch 3.21.3.0.2

Enhancements

ID	Summary	Description	Included in Patch
NXT-21416	Use Vault as alternative secrets store with WebLogic deployments	Next to Fusion Middleware / WebLogic Oracle Platform Security Services (OPSS), OHI applications also support HashiCorp Vault as alternative secrets store. See the Installation Guide for details.	3.22.1.0.0
NXT-24489	JSON Re-Indexing Package	This enhancement introduces the package OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG, that creates an oracle text index OHI_REF_SHEET_LINE_IDX1 on OHI_REFERENCE_SHEET_LINES table in Oracle 19c format with Sync frequency option. This package needs to be executed in the Post-upgrade stage.	3.22.1.0.0

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: pre-upgrade: Application is still running pre-undeploy: Application is stopped, but not undeployed. post-undeploy: Application is undeployed. Database is backed up post-upgrade: Released upgrade script has run. post-deploy: New application is deployed and is up and running.

Stage: post-upgrade

A new OHI_REFERENCE_SHEET_LINES_INDEX_MAINTENANCE_PKG has been provided as part of the patch. Post upgrade of the patch login as ohi_<app>_owner and execute the below command to recreate the index.

begin
  ohi_reference_sheet_lines_index_maintenance_pkg.create_index(1);
end;
/

Configuration Properties

Ref	Action	Subject	Description
NXT-21416	Added	ohi.vault.environment.identifier	To distinguish secrets on a per OHI application instance basis
NXT-21416	Added	ohi.secure.secrets.store	The type of store the OHI application uses for secrets
NXT-21416	Added	ohi.vault.kv.secrets.engine	By default, OHI applications assume that Vault’s Key-Value secrets engine is enabled at root path "secret"
NXT-21416	Added	ohi.vault.address	Vault address. Must use HTTPS
NXT-21416	Added	ohi.vault.clientpem.url	Resource URL to Vault Client pem
NXT-21416	Added	ohi.vault.token	Vault token
NXT-21416	Added	ohi.vault.pem.url	Resource URL to Vault pem
NXT-21416	Added	ohi.vault.clientkeypem.url	Resource URL to Vault Client Key pem
NXT-21416	Added	ohi.vault.namespace	OHI specific Vault namespace section, under the path determined by properties ohi.vault.kv.secrets.engine/ohi.vault.namespace to look for secrets

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
34746903	3-31048463001	PRD-3020	BP	Entering Location Type Values Manually Returns Error
Description:		Entering location type values manually returns error.
Resolution:		In service definitions, manual values can be entered in Location Types field.

Issues that were backported in previous Release / Patch

No backports.