Install Application

This section lists the steps required to deploy Oracle Insurance Gateway on the Oracle WebLogic WebLogic Server (WebLogic).

Work Manager and Thread Management Configuration

Oracle Insurance Gateway packages an application scoped configuration for the Work Manager and thread management. This configuration holds (sane) default values that drive how the Weblogic (thread) resources are used for processing.

For more information about Work Managers, see WebLogic Server documentation. For more information about thread management configuration, like executor services and thread factories, see Configuring Concurrent Managed Objects section.

Whenever the default configuration of one or more of these elements needs changing, create or use a deployment plan. A deployment plan for an existing application, like Oracle Insurance Gateway, can be generated using the Weblogic tooling.

For more information, see Create and Use a Deployment Plan in the Oracle WebLogic Server.

The configuration, such as the minimum and maximum thread constraints and the fair share request factors can be modified at any time in the WebLogic Remote Console, for example, to increase the number of threads used for task processing.

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

Default Work Manager and Thread Management Configuration Values

What follows is a breakdown of all default values for configuration elements that drive the Weblogic (thread) resource utilization.

Work Manager - Wm/ws-work-manager

This Work Manager is used by Oracle Insurance Gateway to deal with intake that comes in at the HTTP API layer, typically /api.

Table 1. Work Manager - Wm/ws-work-manager
Config Element Name Default

fair-share-request-class

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

60

min-threads-constraint

ws-min-threads

10

max-threads-constraint

ws-max-threads

100

capacity

ws-capacity

600

Work Manager - Wm/core-work-manager

This Work Manager is used by the Oracle Insurance Gateway for background processing (of exchanges).

Table 2. Work Manager - Wm/core-work-manager
Config Element Name Default

fair-share-request-class

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

40

min-threads-constraint

core-min-threads

16

max-threads-constraint

core-max-threads

100

capacity

core-capacity

500

Work Manager - Wm/jersey-work-manager

This Work Manager is used by the Oracle Insurance Gateway for background (scheduled) processing done from within Jersey.

Table 3. Work Manager - Wm/jersey-work-manager
Config Element Name Default

fair-share-request-class

jersey-work-manager-fair-share-req-class

60

min-threads-constraint

jersey-min-threads

10

max-threads-constraint

jersey-max-threads

200

capacity

jersey-capacity

500

Executor Service - JerseyExecutor

This executor service is used by the component responsible for autonomously polling the exchange status, to provide a seemingly blocking/synchronous interaction flow over an inherently asynchronous mechanism of processing exchanges.

Table 4. Executor Service - JerseyExecutor
Config Element Default

dispatch-policy

wm/jersey-work-manager

max-concurrent-long-running-requests

10

long-running-priority

5

Executor Service - JerseyScheduledExecutor

This executor service is used by Jersey to track time and generate time-outs as part of blocking/synchronous interaction flows.

Table 5. Executor Service - JerseyScheduledExecutor
Config Element Default

dispatch-policy

wm/jersey-work-manager

max-concurrent-long-running-requests

10

long-running-priority

5

Thread Factory - OigThreadFactory

This is a thread factory that is explicitly used by the scheduler component of the Oracle Insurance Gateway.

Table 6. Thread Factory - OigThreadFactory
Config Element Default

max-concurrent-new-threads

5

priority

5

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. Log in to the WebLogic Remote Console and click the Edit Tree.

  2. Expand the Security drop-down.

  3. Select Realms.

  4. Select myRealm.

  5. Select Authentication Providers.

  6. Click the New to create a new Authentication Provider.

  7. On the Create a New Authentication Provider page, enter the following fields:

    • Name: OHIAuthenticationProvider

    • Type: OracleInternetDirectoryAuthenticator or LDAPAuthenticator if a third‑party LDAP server is being used.

  8. Change the Control Flag to SUFFICIENT and click Create.

  9. Click the Authenticator Parameters tab.

  10. Enter or change the values for various fields as shown below and

    Table 7. Configuring The Authentication Providers
    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.

  11. Click Save.

  12. Click the myrealm link and then DefaultAuthenticator link.

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

  14. 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. Expand the Security drop‑down list.

  2. Click Realms.

  3. Click myRealm.

  4. Select the Users and Groups tab.

  5. Verify that the list shows 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 configured in the WebLogic domain.

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.

Data sources can be configured for the following database installations:

  • 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 the WebLogic before installing the application for use with an Oracle database that is executed on a single machine (not clustered):

Table 8. Set up JDBC Data Sources
Data Source Parameters Non-clustered Database Explanation

Data Source Type

Generic Data Source

Data Source Name

ohi-application-datasource

Logical name

JNDI Name

jdbc/oigUserOhiApplicationDS

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_oig_user

Fixed value, do not change

Password & Confirm Password

Password of "ohi_oig_user"

The schema password as selected during the installation
Table 9. Data Source for Operational Reports for Connecting to an Oracle Database that is Running on a Single Machine
Data Source Parameters Non-Clustered database Explanation

Data Source Type

Generic Data Source

Data Source Name

ohi-operational-reporting-datasource

Logical name

JNDI Name

jdbc/oigReportingExtractUserDS

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_oig_rpt_user

Fixed value, do not change

Password & Confirm Password

Password of "ohi_oig_rpt_user"

The schema password as selected during the installation

Setting Advanced Properties for the Data Source

The Data Source that has been created needs some additional advanced settings.

  1. Select the newly created Data Source

  2. Click the table Connection Pool

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

Table 10. Setting Advanced Properties for the Data Source
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 than 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:

Table 11. Driver Property
Property Value

oracle.net.CONNECT_TIMEOUT

10000

Installing the Oracle Health Insurance Application Through the WebLogic Remote Console

Oracle Health Insurance applications are delivered in a so-called Java Enterprise Archive (EAR) which is installed through the WebLogic Remote Console. In order to do that, take the following into account:

  • Make sure to select the option Install this deployment as an application.

  • If the application is deployed to a cluster, in the Select deployment targets page, select the correct cluster as target.

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": {}
}

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:

Table 12. Changes That Require a Restart
Change Description

Changing default currencies

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