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).

Creating WebLogic Work Managers

By default, 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 more information, check 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 Web Services requests, named "wm/ws-work-manager"

• and a work manager to control 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 will use 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 will map to the default WorkManager for the application OHI-Capitation-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

After configuring work managers, managed servers need 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 WebLogic Admin Console as is required, for example to increase the number 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.

Configuring 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 the New button in order to create a New Authentication Provider

5. 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.

6. Click the OHIAuthenticationProvider link.

7. Change the Control Flag to SUFFICIENT and click the Save button.

8. Click the Provider Specific tab.

9. 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. E.g.: 3060. In case LDAPS is used, make sure to check the SSLEnabled flag as well.
Principal	LDAP admin principal: E.g.: 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	E.g.: (&(uid=*)(objectclass=person))
User From Name Filter	E.g.: (&(uid=%u)(objectclass=person))
User Name Attribute	E.g.: 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 your LDAP settings.

1. Click the Save button.

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

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:

Step 1: Login to WLS Admin Console and click on Security Realms

Step 2: Click on myrealm

Step 3: Click on Users and Groups tab

Step 4: You should be able to 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 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;

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

Data Source for connecting to an Oracle database running on a single machine

The following table lists details for the Data Source that must be configured in WebLogic 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/capitationUserOhiApplicationDS	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_capitation_user	Fixed value, do not change
Password & Confirm Password	Password of "ohi_capitation_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 on the table Connection Pool

3. Expand the Advanced node at the bottom of the page to display all 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 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:

Property	Value
oracle.net.CONNECT_TIMEOUT	10000

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 will be installed through the WebLogic Admin Server 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.

Changing the Context-Root for UI or Web Services

Oracle Health Insurance applications consist 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.

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

JET UI Installation

JET UI and Web Services should be in the same origin. An origin is defined as a combination of URI scheme, hostname, and port number. If the JET UI is on a different origin than the Web Services, the browser will send a preflight OPTIONS request for each actual GET request. Those OPTIONS requests are uncachable, effectively doubling the time needed to get to the data.

Changes That Require Restart

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

Change	Description
Changing default on countries or currencies	If the default country the default currency is changed the a restart is required to have the application adapt to these changes.