Previous
3.3.1 User Interface related properties
The following table lists user interface related properties:
|
Category |
Parameter |
Value |
Explanation |
|---|---|---|---|
|
User Interface |
ohi.environment.identifier |
Samples: "User Acceptance Test", "Development". |
Text string that is displayed on the home page of the system that helps the user to identify the environment |
|
User Interface |
ohi.ui.maxrowstoretrieve |
Suggested default is 200. |
Maximum number of rows retrieved to show in a UI table. Note that memory usage and page load times are impacted by this value. |
|
User Interface |
ohi.ui.maxrowstoretrieve.<function code> |
Maximum number of rows retrieved to show in a UI table for an individual page. The value specified overrides ohi.ui.maxrowstoretrieve for that particular page only. The function code is the one shown in the 'About this page' popup. The function code is case sensitive. Example to overrule the system wide setting for the Messages page: Note: it is not possible to change the number of rows shown for an individual LOV. LOV are always restricted by ohi.ui.maxrowstoretrieve |
3.3.1.1 Activity Processing related properties
The following table lists activity processing related properties:
|
Category |
Parameter |
Value |
Explanation |
|---|---|---|---|
|
Activity Processing |
ohi.vbp.processing.node |
Optional. Possible values: true or false. Default value: false. |
If specified as 'true' will initiate the JPA entity manager factory for improved persistence characteristics. Not to be used on nodes that are also used for UI interaction. |
|
Activity Processing |
ohi.jdbc.batchsize |
Optional. Positive integer value. Default: 1000 |
Only applies when ohi.vbp.processing.node=true, controls the size of record batches per DML transaction. This reduces the number of round-trips to the database, thereby improving application performance. The higher this number the more heap memory will be necessary. |
|
Activity Processing |
ohi.processing.yield.default |
Optional. Positive integer value. Default: 3 |
Default time (in seconds) a task will be held back in the processing grid, in between execution steps. This typically is used between parent-child task relationships, where a parent task will has to regularly check on the status of its children. |
|
Activity Processing |
ohi.max.headroom |
Optional. Positive integer value. Default: 2000 |
The maximum number of tasks that is to be loaded into the processing grid, per given activity type (e.g. CALCULATE_RATES). |
|
Activity Processing |
ohi.processing.groupsize |
Optional. Positive integer value. Default: 400 |
The number of tasks to be grouped (when applicable) into a collection of tasks that is to be put into the processing grid as one atomic unit. This complete collection will be processed on one processing node. |
|
Activity Processing |
ohi.processing.loadercount |
Optional. Positive integer value. Default: 1 |
The number of loader tasks to be spawned for a specific activity type, whenever an activity of that type needs to be processed and has child tasks spawned into the grid. These loaders work concurrently on the set of child tasks that are to be spawned. |
|
Activity Processing |
ohi.processing.loaderyield |
Optional. Positive integer value. Default: 3 |
The time (in seconds) a loader task will be held back in the grid, in the event it has reached its maximum number of tasks it is allowed to load and spawn into the grid. |
|
Activity Processing |
ohi.processing.yield.taskcompletion |
Optional. Positive integer value. Default: 3 |
The time (in milliseconds) an (aggregate) task is going to be held back for task loaders to complete their work. |
3.3.1.1.1 Specifying yields, submission count, group size and loader count per activity type
Oracle Health Insurance Value-Based Payments allows to individually specify
some of the aforementioned application properties on a per-activity-type basis.
This provides finer grained control of loading and processing semantics. The way
to accomplish this is to concatenate the mnemonic for the specific activity type
after the specific property key, for example:
ohi.processing.groupsize.SELECT_MEMBER_CONTRACTS=8000
This mechanism is available for the following properties:
- ohi.processing.yield
- ohi.processing.headroom
- ohi.processing.groupsize
- ohi.processing.loadercount
- ohi.processing.loaderyield
For the mnemonic of individual activity types, check the Implementation Guide.
3.3.1.2 Streaming Persistence related properties (applicable for release 2.15.2.0.0+)
The following table lists properties that are related to streaming persistence, an option that will be available from major release 2.15.2.0.0 onwards:
|
Category |
Parameter |
Value |
Explanation |
|---|---|---|---|
|
Persistence |
ohi.persistence.streaming.threads |
Optional. Positive integer value. Default value: see explanation. |
It defaults to the number 1/4th of availableProcessors or 2 whichever is higher. It should generally be set to a fraction of the number of physical cores on the target database machine divided by the number of JVM's writing to that target database machine. |
|
Persistence |
ohi.persistence.streaming.commits |
Optional. Positive integer value. Default value: 1000 |
This is the number of changeSets a write thread will collect before committing to the database. |
|
Persistence |
ohi.persistence.streaming.idlecommit |
Optional. Positive integer value. Default value: 5000 |
If the changeSet commit count has not been reached, write threads will commit whatever changes have been collected periodically. This setting is the amount of time in milliseconds that a write thread will idle before committing any remaining collected changeSets. |
|
Persistence |
ohi.persistence.streaming.queuesize |
Optional. Positive integer value. Default value: 100000 |
In order to contain memory usage, the queue of unwritten change sets is bounded. This key sets the size of the bounded queue. JVMs with more memory can accept larger changeSet queues. When the queue is full, producers will spin periodically attempting to submit to the queue until there is space available. |