OHI Value-Based Payments
 PreviousHomeNext 
3.3.1 User Interface related propertiesBook Index3.4 OBIEE Artefacts

3.3.2 Properties related to specific Activities

The following table lists activities related properties:

Category

Parameter

Value

Explanation

Activity Notification

ohi.activityprocessing.notification.endpoint

Optional. Sample:
ohi.activityprocessing.notification.endpoint=
http://machine:port/api/generic_notification_service

RESTful Service endpoint URL for delivering the response notification after activity processing is completed. OHI Components applications will use a PUT operation.

Activity Notification

ohi.activityprocessing.notification.endpoint.<ACTIVITY_TYPE_CODE>

Optional. Sample:
ohi.activityprocessing.notification.endpoint.
SELECT_TRANSACTIONS_IN_SET=
http://machine:port/api/specific_notification_service

Activity type specific RESTful Service endpoint URL for delivering the response notification after activity processing is completed. OHI Components applications will use a PUT operation.

GenerateFinancialMessageActivity

ohi.processing.groupsize.GENERATE_FINANCIAL_MESSAGES

Positive value. Default is 500

Utilized for Generate Financial Message activity grouping It decides how many sub-activities will run in one transaction to improve performance.

This directly groups child activities according to groupSize

Allowed values: Positive integer value

GenerateFinancialMessageActivity

ohi.financialmessage.endpoint.request

Samples:

http://machine.domain:port/financialmessage

For sending out financial message in Generate Financial Message Activity. For MessageBased requests

GenerateFinancialMessageActivity

ohi.financialmessage.datafile.notification.endpoint

Samples:

http://machine.domain:port/financialmessage/datafile

For sending out financial message data file creation notification in Generate Financial Message Activity. For FileBased requests

ResendFinancialMessageActivity

ohi.resendfinancialmessage.endpoint.request

Samples:

http://machine.domain:port/resend/financialmessage

For re-sending financial messages in Resend Financial Message Activity. For Message based requests

ResendFinancialMessageActivity

ohi.resendfinancialmessage.datafile.notification.endpoint

Samples:

http://machine.domain:port/resend/financialmessage/datafile

For re-sending financial message data file creation notification in Resend Financial Message Activity. For FileBased requests

SupersedeActivity

ohi.processing.groupsize.SUPERSEDE_REVERSE

Positive value. Default is 500

Utilized for Financial Processing (Supersede) activity grouping. It decides how many sub-activities will run in one transaction to improve performance. This directly groups child activities according to groupSize. Allowed values: Positive integer value

SelectTransactionsInSetActivity

ohi.processing.bucketsize.SELECT_TRANSACTIONS_IN_SET

Positive value. Default is 500

Utilized for Select Transactions In Set activity bucketing. It decides how many sub-activities will run in one transaction to improve performance.This one utilizes a technical table to bucketise the working set. Allowed values: Positive integer value

3.3.2.1 Single Sign-On related properties

The following table lists properties that need to be set when OHI Components application take part in Single Sign-On (SSO) scenarios:

Category

Parameter

Value

Explanation

Security

ohi.security.sso.required

Boolean value. Default is false.

The application will reject traffic without an SSO header.

Security

ohi.security.sso.enabled

Boolean value. Default is false.

The application will check for an SSO header, and if one is not found, present the user with a login screen.

Security

ohi.security.sso.header

(OPTIONAL) String value, defaults to OAM_REMOTE_USER for use with Oracle Access Manager.

The header value in which to check for an SSO principal if it is not mapped via servlet security.

Security

ohi.security.sso.provisionOnDemand

(OPTIONAL) Boolean value, default is false.

If this is set to true, when a user is SSO authenticated but does not exist in the application, it will be provisioned in the application immediately.

Security

 ohi.security.sso.provisionOnDemandDylo

(OPTIONAL) String value.  Default is empty.

If this is set to a code,  the function dynamic logic the code references will be run to customise an auto-provisioned user.

Security

ohi.security.sso.provisionOnDemandRole

(OPTIONAL) String value.  Default is empty.

If this is set to a code, it will be used to lookup the security role to be added by default to auto-provisioned users.

 PreviousHomeNext 
3.3.1 User Interface related properties3.4 OBIEE Artefacts