Enabling Data ReportingFollow the steps below to enable Data Reporting. - Open
<WSO2_OB_APIM_HOME>/repository/conf/finance/open-banking.xml and <WSO2_OB_KM_HOME>/repository/conf/finance/open-banking.xml files. - Under the
<DataPublishing> sub-element set the <Enabled> parameter to true to enable the feature. - Replace the
<WSO2_OB_BI_HOST> placeholder with the hostname of your WSO2 OB BI server and configure the other parameters accordingly.
Code Block |
---|
| <BIServer>
<DataPublishing>
<!-- Include all configurations related to Data publishing -->
<!-- Enable data publishing in WSO2 Open Banking-->
<Enabled>true</Enabled>
<!-- Server URL of the remote BI server used to collect statistics. Must
be specified in protocol://hostname:port/ format. -->
<ServerURL>{tcp://<WSO2_OB_BI_HOST>:7612}</ServerURL>
<!-- Administrator username to login to the BI server for data publishing. -->
<Username>admin@wso2.com@carbon.super</Username>
<!-- Administrator password to login to the BI server for data publishing. -->
<Password>wso2123</Password>
</DataPublishing>
</BIServer> |
Configuring Open Banking Business IntelligenceConfiguring databases The following databases store raw and summarized data. Make sure they are available in your database servers. - Configuring datasources
- Modify the
OB_REPORTING_DB and OB_REPORTING_SUMMARIZED_DB datasources in <WSO2_OB_BI_HOME>/conf/worker/deployment.yaml file. - Update
jdbcUrl , username , password and driverClassName in the datasource entries with your database configurations. A sample is given below:
Code Block |
---|
| - name: OB_REPORTING_DB
description: The datasource used to store statistics for OB Reporting module
jndiConfig:
name: jdbc/OB_REPORTING_DB
definition:
type: RDBMS
configuration:
jdbcUrl: 'jdbc:mysql://localhost:3306/openbank_ob_reporting_statsdb?autoReconnect=true&useSSL=false'
username: 'root'
password: 'root'
driverClassName: 'com.mysql.jdbc.Driver'
maxPoolSize: 20
idleTimeout: 60000
connectionTestQuery: SELECT 1
# Use below for oracle database
# connectionTestQuery: SELECT 1 FROM DUAL
validationTimeout: 30000
isAutoCommit: false
- name: OB_REPORTING_SUMMARIZED_DB
description: The datasource used to store statistics for OB Reporting module
jndiConfig:
name: jdbc/OB_REPORTING_SUMMARIZED_DB
definition:
type: RDBMS
configuration:
jdbcUrl: 'jdbc:mysql://localhost:3306/openbank_ob_reporting_summarizeddb?autoReconnect=true&useSSL=false'
username: 'root'
password: 'root'
driverClassName: 'com.mysql.jdbc.Driver'
maxPoolSize: 20
idleTimeout: 60000
connectionTestQuery: SELECT 1
# Use below for oracle database
# connectionTestQuery: SELECT 1 FROM DUAL
validationTimeout: 30000
isAutoCommit: false |
Data Reporting v3.1.2 Info |
---|
This is available only as a WUM update and is effective from June 10, 2020 (06-10-2020). For more information on updating WSO2 Open Banking, see Updating WSO2 Products. |
Follow the steps below to update to Data Reporting v3.1.2: - To capture data from the
/token endpoint, configure the Synapse Token API in WSO2 API Manager.- Open the
<WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/api/_TokenAPI_.xml file. Add the following property under the <inSequence> tag: Code Block |
---|
| <property name="api.ut.backendRequestTime" expression="get-property('SYSTEM_TIME')"/> |
Add the following handlers in the given order under the <handlers> tag: Code Block |
---|
| <handler class="com.wso2.finance.open.banking.management.information.reporting.data.publisher.APIInvocationLatencyStatsHandler"/>
<handler class="com.wso2.finance.open.banking.management.information.reporting.data.publisher.ReportingDataHandler"/> |
- To capture PSU’s online banking and mobile banking data, update the Adaptive Authentication script as follows:
- Open the
<WSO2_OB_APIM_HOME>/repository/conf/finance/common.auth.script.js file. Add the following variable at the beginning of the file. Set its value according to the flow you want to capture data. Possible values are: Online Banking, Mobile Banking Code Block |
---|
| var psuChannel = 'Online Banking'; |
Add psuChannel as a parameter to the reportingData function as given below. Make sure to update all the reportingData function invocations in the script. Code Block |
---|
| reportingData(context, "AuthenticationAttempted", false, psuChannel); |
Data Reporting API If you're using a customised consent authentication web application, you may use the Data Reporting API to publish events from the application. Invoke the Data Reporting API in all the relevant places to publish the PSU and authorisation data to the reporting databases. In the following scenarios, events are captured using the consent authorisation web app: - The user visiting the consent page
- After the user authorising/denying the consent
For sample requests, see Data Reporting API. Multiexcerpt |
---|
hidden | true |
---|
MultiExcerptName | InvocationFailure |
---|
|
Capturing data during invocation failure scenarios- Go to the
<WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/sequences directory. Create an XML file named api_invocation_fail_data_publisher.xml with the following content: xmlOpen the <WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml file and add the OBErrorDataPublisher class under the sequence tag. Open the <WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/sequences/_auth_failure_handler_.xml file and add the OBErrorDataPublisher class below the sequence key element as shown below: xml
|
|