Install Application

This section lists the steps that are required to deploy the Oracle Health Insurance application on the Oracle Fusion Middleware WebLogic Server (WebLogic).

For slim installer, the below configuration is similar but these configurations must be done while creating the domains. These configurations can be updated later through WLS via RESTful Management APIs as the slim installer does not deploy the Weblogic admin console. This document explains how to configure the Oracle Health Insurance applications through the WebLogic admin console.

Deployment EAR

In addition to the existing EAR, Oracle Health Insurance products provide light EAR which is placed under lightApplication directory of the release zip. This EAR can be used to deploy for slim installation of the Oracle Fusion Middleware. This EAR does not include the ADF UI.

Creating The WebLogic Work Managers

By default, the WebLogic Server uses the default work manager to handle thread management and perform self-tuning. This default Work Manager is used by an application when no other Work Managers are specified in the application’s deployment descriptors. For additional information, refer the WebLogic documentation on Work Managers.

For example, the following application-specific work managers can be configured for more fine-grained control and work load monitoring of the system:

  • a work manager to control the UI requests, named "wm/ui-work-manager"

  • a work manager to control the Web Services requests, named "wm/ws-work-manager"

  • and a work manager to control the task or activity processing, named "wm/core-work-manager"

If these work managers are not configured, the system issues warnings at startup like the following example and uses the WebLogic default work manager instead:
<Warning> <WorkManager> <BEA-002919> <Unable to find a WorkManager with name wm/core-work-manager. Dispatch policy wm/core-work-manager maps to the default WorkManager for the application OHI-Policies-2.x.x.x.x>

Refer WebLogic documentation on Work Managers to override the behavior of the default work manager.

Create global work managers through the Administration Console using the steps that are listed in the following table in the given order. Make sure to associate the work managers with the managed servers.

Step Configuration Value

1

Minimum Threads Constraint

Name

core-work-manager-min-threads-constraint

Count

16

2

Maximum Threads Constraint

Name

core-work-manager-max-threads-constraint

Count

16

3

Fair Share Request Class

Name

core-work-manager-fair-share-req-class

Fair Share

40

4

Work Manager

Name

wm/core-work-manager

Request Class

core-work-manager-fair-share-req-class

Minimum Threads Constraint

core-work-manager-min-threads-constraint

Maximum Threads Constraint

core-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Stuck Thread Action

Ignore stuck threads

5

Minimum Threads Constraint

Name

ws-work-manager-min-threads-constraint

Count

10

6

Maximum Threads Constraint

Name

ws-work-manager-max-threads-constraint

Count

100

7

Fair Share Request Class

Name

ws-work-manager-fair-share-req-class

Fair Share

60

8

Work Manager

Name

wm/ws-work-manager

Request Class

ws-work-manager-fair-share-req-class

Minimum Threads Constraint

ws-work-manager-min-threads-constraint

Maximum Threads Constraint

ws-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Stuck Thread Action

Ignore stuck threads

9

Minimum Threads Constraint

Name

ui-work-manager-min-threads-constraint

Count

5

10

Maximum Threads Constraint

Name

ui-work-manager-max-threads-constraint

Count

100

11

Fair Share Request Class

Name

ui-work-manager-fair-share-req-class

Fair Share

50

12

Work Manager

Name

wm/ui-work-manager

Request Class

ui-work-manager-fair-share-req-class

Minimum Threads Constraint

ui-work-manager-min-threads-constraint

Maximum Threads Constraint

ui-work-manager-max-threads-constraint

Capacity Constraint

None Configured

Stuck Thread Action

Ignore stuck threads

After configuring the work managers, managed servers have to be restarted.

The work manager configuration, like the minimum and maximum threads constraints and the fair share request factors, can be modified at any time in the WebLogic Admin Console as is required, for example to increase the number of threads used for task processing.

This largely depends on the hardware capacity, system configuration and the load characteristics and typically requires a thorough understanding of the system’s performance.

Configuring The Authentication Providers

The application uses a WebLogic Authentication Provider to connect to a user store for authenticating users. Examples of configurable user identity stores are Oracle Internet Directory (OID) or to a third party LDAP server. This section describes the configuration of an OID or third party LDAP Authentication Provider.

  1. Login to the WebLogic admin console and click the Security Realms link.

  2. Click the myrealm link.

  3. Click the Providers tab.

  4. Click New in order to create a New Authentication Provider

In the WebLogic Production-mode use the Lock & Edit button before clicking the New button.

  1. Change Name and Type to OHIAuthenticationProvider and OracleInternetDirectoryAuthenticator (or to LDAPAuthenticator in case a third party LDAP server is used) respectively in Create a new Authentication Provider page and click the OK button.

    1. Click the OHIAuthenticationProvider link.

    2. Change the Control Flag to SUFFICIENT and click Save.

    3. Click the Provider Specific tab.

    4. Enter/change the values for various fields as shown below and select the option Propagate Cause For Login Exception.

Field Value

Host

LDAP hostname or IP address

Port

LDAP Port or SSL Port if the LDAP is SSL enabled. For example: 3060. In case LDAPS is used, make sure to check the SSLEnabled flag as well.

Principal

LDAP admin principal: For example: cn=orcladmin

Credential

LDAP admin password

Confirm Credential

LDAP admin password

User Base DN

User Base distinguished name. For example: ou=Users,dc=healthinsurance,dc=oracle,dc=com

All Users Filter

For example: (&(uid=*)(objectclass=person))

User From Name Filter

For example: (&(uid=%u)(objectclass=person))

User Name Attribute

For example: uid

Group Base DN

If there are no groups in the LDAP, leave this field empty.
There are a few more properties (or fields in the page) which are not mentioned in the table above. Change the values of those fields to suit the LDAP settings.

  1. Click Save.

  2. Click the myrealm link and then DefaultAuthenticator link. Change the Control Flag to SUFFICIENT and click Save.

  3. Restart the WebLogic Server.

Optionally, verify that the authentication provider is configured successfully (after the WebLogic Server is restarted) by following the steps mentioned below:

  1. Login to WLS Admin Console and click Security Realms.

  2. Click myrealm.

  3. Click the Users and Groups tab

  4. See the list of users from OHIAuthenticationProvider (in addition to the default users from DefaultAuthenticator).

Set Up JDBC Data Sources

The application connects to the Oracle database through a Data Source that needs to be specified in the WLS Server.

For security reasons, the database connections used by the application connect to database schemas that do not own database objects. These schemas are only granted the required privileges to use the objects.

The following sections describe setting up data sources for connecting to:

  • an Oracle database that is running on a single machine

  • an RAC-enabled Oracle database that is running on multiple machines

Data Source for Connecting to an Oracle Database That is Running on a Single Machine

The following table lists details for the Data Source that must be configured in WLS before installing the application for use with an Oracle database that is executed on a single machine (not clustered):

Data Source Parameters Non-Clustered database Explanation

Data Source Type

Generic Data Source

Data Source Name

ohi-application-datasource

Logical name

JNDI Name

jdbc/policiesUserOhiApplicationDS

Used by the application to resolve the Data Source

Database Type

Oracle

Database Driver

Oracle’s Driver (Thin) for Instance connections; Versions:Any

Oracle’s Driver (Thin) for Service connections; Versions:Any

Database Name

SID or service name of the database

If the name of the Oracle driver that was selected contains the words "for Instance connections" enter the SID.

If the name of the Oracle driver contains the words "for Service connections" enter the service name.

Host Name

Name or IP address of the machine where the database is running

Port

Port on which the database is running

Database User Name

ohi_policies_user

Fixed value, do not change

Password & Confirm Password

Password of "ohi_policies_user"

The schema password as selected during the installation

Data Source for Connecting to an Oracle RAC Database That is Running on Multiple Machines

To support Oracle RAC features within the Oracle WebLogic Server, Oracle recommends using the Oracle WebLogic Server GridLink Data Source. A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service targeted to an Oracle RAC cluster. It uses the Oracle Notification Service (ONS) to adaptively respond to state changes in an Oracle RAC instance. An Oracle Database service represents a workload with common attributes that enables administrators to manage the workload as a single entity.

To configure this, the following steps need to be performed. For additional information about GridLink Data Source configuration, refer to the Oracle Weblogic Server documentation.

Configuring The GridLink Data Source

  1. Login to the WebLogic admin server console and click the Services/Data Sources link.

  2. Click New and select the option GridLink Data Source.

    In the WebLogic Production-mode use the Lock & Edit button before clicking on the* New* button.

  3. Change the value of Name to ohi-application-datasource and enter jdbc/policiesUserOhiApplicationDS in JNDI Name. Additionally, select Database Driver: Oracle’s Driver for GridLink Connections Versions:Any and Click Next.

  4. In the Transaction Options page, accept the default settings (Supports Global Transactions and One-Phase Commit) and click Next.

  5. If SCAN (Single Client Access Name) is used for the Oracle RAC database, select the option Enter complete JDBC URL. Else, select the option Enter individual listener information.

  6. In the Connection Properties page either

    • enter the values of various fields as outlined in the table below if option Enter complete JDBC URL is selected:

    Parameters Value Explanation

    Complete JDBC URL

    jdbc:oracle:thin:@{scan-listener-host}:{scan-listener-port}/{service-name}

    JDBC URL using SCAN

    Database User Name

    ohi_policies_user

    Fixed value, do not change

    Password & Confirm Password

    Password of "ohi_policies_user"

    The schema password as selected during the installation

    • or enter the values of various fields as outlined in the table below if option Enter individual listener information is selected:

    Parameters Value Explanation

    Service Name

    Oracle RAC service name

    Host and Port

    hostname1:port hostname2:port

    Individual RAC node details. The format is <HOSTNAME>:<PORT>

    Database User Name

    ohi_policies_user

    Fixed value, do not change

    Password & Confirm Password

    Password of "ohi_policies_user"

    The schema password as selected during the installation

  7. In the Test GridLink Database Connection page, click Test All Listeners to see if the connection is successful. Once the test connection succeeds, click Next.

  8. Enter the details of the ONS client configuration as outlined in the table below and click Next.

    Parameters Value Explanation

    Fan Enabled

    Check-box selected

    Enables the data source to subscribe to and process the Oracle FAN events. This attribute is only applicable for the RAC configurations that publish the FAN notification events using the ONS protocol.

    ONS Nodes

    For example: hostname1:6200,hostname2:6200

    A comma-separated list of the ONS daemon listen addresses and ports to connect to for receiving the ONS-based FAN events.

    ONS Wallet File

    Location of ONS Wallet File (including the file name)

    The location of the Oracle wallet file in which the SSL certificates are stored. Only required when the ONS client is configured to communicate with the ONS daemons using SSL.

    ONS Wallet Password & Confirm the ONS Wallet Password

    The wallet password

    The wallet password attribute that is included as part of the ONS client configuration string. This attribute is only required when the ONS is configured to use the SSL protocol.

  9. Click Test All ONS Nodes to see if the connection is successful. Once the connection test succeeds, click Next.

  10. Select the Targets in the next page and click Finish.

Make sure to specify the managed server as target for the GridLink Data

Setting Advanced Properties for the Data Source

Whether for a single machine or RAC - the Data Source that has been created needs some additional advanced settings.

  1. Select the newly created Data Source

  2. Click table Connection Pool.

  3. Expand the Advanced node at the bottom of the page to display all the properties and set the following:

Property Value

Initial Capacity

0

Test Connections On Reserve

Checked

Test Frequency

300

Connection Creation Retry Frequency

30

Seconds to Trust an Idle Pool Connection

10

Statement Cache Size

The default value is 10. Increasing this to a higher value results in a better performance. Consult WebLogic documentation for more details on this.

Wrap Data Types

Unchecked

Init SQL

When the users are in a different time zone then the database, the session time zone must be set with this statement:

SQL ALTER SESSION SET TIME_ZONE = '<time zone>', where <time zone> is the name of an Oracle RDBMS supported time zone.
The time zone names can be found in V$TIMEZONE_NAMES.

Set the following driver property:

Property Value

oracle.net.CONNECT_TIMEOUT

10000

Installing the UI Customization Library through WebLogic Admin Server Console

This is not required while setting up through slim middleware.

To enable the creation of site-level UI Customizations, without having to change Oracle Health Insurance applications itself, an initially empty library called custom.oracle.healthinsurance.policies needs to be installed before the Oracle Health Insurance application can be installed.

  1. Login to the WebLogic Admin Server console (for example:).

  2. Click the Deployment link and then click the Install button as shown in the following screenshot. If the Install button is disabled, click the Lock & Edit button first (in the upper left section of the page).

  3. Select the path where the library custom.oracle.healthinsurance.policies.war file is located (<OHI_ROOT>/lib) and click Next as shown in the following sample screenshot:

  4. Select the option Install this deployment as a library and click Next as shown below:

  5. Ensure that the General - Name is set to custom.oracle.healthinsurance.policies as shown below. This is the name the Oracle Health Insurance Application refers to when loading the library, so this is the name under which it must have been installed. The version numbers differ from what is shown in the screenshot below. The Oracle Health Insurance Application automatically loads the highest version of all installed libraries with this deployment name. Then click Next.

  6. Click Finish. See a success message as shown below. The library is now installed.

if selected the Lock & Edit in step 1, click Activate Changes.

The following section describes the installation of the Oracle Health Insurance application.

Installing The Oracle Health Insurance Application Through the WebLogic Admin Server Console

Oracle Health Insurance applications are delivered in a so called Java Enterprise Archive (EAR) which is installed through the WebLogic Admin Server Console. In order to do that, perform the following steps.

  1. Login to the Admin Server console (for example:).

  2. Click the Deployment link and then click the Install button as shown in the following screenshot:

  3. Select the path where the EAR file is located and click Next as shown in the following screenshot:

  4. Select the option Install this deployment as an application and click Next as shown below:

  5. Click Finish. The Oracle Health Insurance application is now installed.

  6. To deploy the application to a cluster, in Select deployment targets page, select the Clusters target as shown below:

Installing The Oracle Health Insurance Application Through REST API

Post :http://<HOST-NAME>:<PORT-NUMBER>/management/weblogic/latest/domainRuntime/deploymentManager/deploy
{
"name": "<OHI-APPLICATION-NAME>.",
"applicationPath": "<PATH-OF-OHI-APPLICATION-EAR>",
"targets": ["<NAME-OF-CLUSTER>"],
"plan": "<PATH-OF-PLAN.xml>",
"deploymentOptions": {}
}

Changing the Context-Root for UI or Web Services

Oracle Health Insurance applications consists of multiple modules. Each module is shipped with a default context-root. To change the default context-root of an Oracle Health Insurance application web application or an Oracle Health Insurance application web service, deploy the application with a customized deployment plan.

Refer to the section Configuring Applications for Production Deployment in the "Weblogic Fusion Middleware Deploying Applications to the "Oracle WebLogic Server" guide for details.

Changing User Session Timeout

An Oracle Health Insurance application uses the WebLogic Server’s default session timeout - which is 3600 seconds(1 hour). For security or resource (memory) usage reasons, change this to a shorter value. See section Configuring Applications for Production Deployment in the "Weblogic Fusion Middleware Deploying Applications to Oracle WebLogic Server" guide how to do this.

Changes That Require a Restart

There are some changes to the system that require a restart for the changes to take effect. Following is the list of such changes:

Change Description

Add/Remove Insurable Entity Types

If new insurable entity types are added then the system needs to create and assign dynamic tables for the type which requires a restart. If insurable entity types are removed then these tables need to be removed which also requires a restart.

Changing default currencies

If the default currency is changed then a restart is required for the application adapt to these changes.

Setting/Changing dateFormat fields in Countries page

If the dateFormat fields is/are changed the Countries page, a restart is required for the application adapt to these changes.