OHI Value-Based Payments
 PreviousHomeNext 
3.2.7 Changing the Context-Root for UI or Web ServicesBook Index3.3.1 User Interface related properties

3.3 Configure OHI Value Based Payments properties file

.ssoA changed version of the ohi-vbp.properties file may be delivered in a new Oracle Health Insurance Value-Based Payments release.

The following tables describe the properties that are maintained in this file.

Category

Parameter

Sample Value

Explanation

File Import

ohi.ws.fileimport.filesrootdirectory

Directory paths used for File Import will be prepended with the given root directory. This is for security reasons, it ensures that files are stored in a specific area only.

Dynamic Logic

ohi.dynamiclogic.classes.directory

Path to directory in which the system generated Dynamic Logic classes are placed.

Dynamic Logic

ohi.dynamiclogic.startup.compile

true

An optional property that determines whether to compile the dynamic logic (those who are not compiled before) at start-up of the application or not. Default value is true.

Trace Files

ohi.incident.rootdir

target/trace

OHI Components makes use of the Logback library for generating log output. In the event of an unanticipated application exception, additional - more detailed exception trace information is written out to an individual exception trace file. The location for these exception trace files is controlled by this property. By default the location "target/trace" relative to the directory where the WebLogic server was started is used.
When changing the value for this property, make sure that the OS user that executes the WebLogic server processes needs to be able to create (and read/write files in) the directory referenced by the property.

Web Service Connection settings

Category

Parameter

Value

Explanation

Web Services

ohi.ws.client.connectiontimeout

Positive integer value
Default: 60000

The time in milliseconds before the attempt to connect to an outbound service times out. A value of 0 means never timeout.

Web Services

ohi.ws.client.readtimeout

Positive integer value
Default: 60000

The time in milliseconds that the client will wait for the server to respond to the request. A value of 0 means never timeout.

Web Services

ohi.ws.client.retrytimeout

For example: 1000

The time in milliseconds that the system will wait before another attempt is made to access a failing service. A value of 0 means no timeout before retrying.

Web Services Validation and Logging

The ohi-vbp.properties file also has properties that determine the behavior of Web Services validation and logging. The following table describes these:

Category

Parameter

Value

Explanation

Web Services

ohi.ws.<ip-name>.request.validate

true or false

If set to true, the request will be validated against an XSD when it is received. For production systems, with extensively tested integrations, the recommended value is false.

Web Services

ohi.ws.<ip-name>.response.validate

true or false

If set to true, the response will be validated against an XSD before sending. For production systems, with extensively tested integrations, the recommended value is false.

Applicability for all OHI Web Services is listed in the following table:

Web Service

ip-name

Relevant properties

Data Access

dataaccessgroup

request.validate
response.validate

File Import

fileimport

request.validate

Provider Import

provider

request.validate
response.validate

Provisioning

provisioning

request.validate
response.validate

Relation Import

relation

request.validate
response.validate

OHI Value-Based Payments URL references related properties

In HTTP API RESTful services links, URL references may be passed. Construction of the URL for these pages is driven by the following parameters:

Category

Parameter

Value

Explanation

User Interface

ohi.vbp.application.baseurl

For example: http://localhost:7001

The base URL for accessing the application, typically includes the machine or loadbalancer, the domain and a port number

Before sending URI's out, the system will encode these. The receiving system is expected to decode the URI.

 PreviousHomeNext 
3.2.7 Changing the Context-Root for UI or Web Services3.3.1 User Interface related properties