Note |
---|
The Summarisation feature in Data Reporting is supported only for MSSQL database servers. |
Configuring Open Banking Key ManagerOpen the <WSO2_OB_KM_HOME>/repository/conf/finance/open-banking.xml file and add the following configurations below the </Analytics> tag. - Replace the
<WSO2_OB_BI_HOST> placeholder with the hostname of your WSO2 Open Banking Business Intelligence (WSO2 OB BI) server and configure other parameters accordingly. - To publish the statistics set the value of the
<Enabled> tag to true .
Code Block |
---|
| <BIServer>
<MIReporting>
<Enabled>true</Enabled>
<ServerURL>{tcp://<WSO2_OB_BI_HOST>:76127616}</ServerURL>
<Username>admin</Username>
<Password>admin</Password>
</MIReporting>
</BIServer> |
Configuring Open Banking API ManagerConfiguring open-banking.xmlOpen the <WSO2_OB_APIM_HOME>/repository/conf/finance/open-banking.xml file and add the following configurations below the </Analytics> tag. - Replace the
<WSO2_OB_BI_HOST> placeholder with the hostname of your WSO2 Open Banking Business Intelligence (WSO2 OB BI) server and configure other parameters accordingly. - To publish the statistics set the value of the
<Enabled> tag to true .
Code Block |
---|
| <BIServer>
<MIReporting>
<Enabled>true</Enabled>
<ServerURL>{tcp://<WSO2_OB_BI_HOST>:76127616}</ServerURL>
<Username>admin</Username>
<Password>admin</Password>
</MIReporting>
</BIServer> |
Configuring handlersOpen the <WSO2_OB_APIM_HOME>/repository/resources/api_templates/velocity_template .xml file and do the following: Add the APIInvocationLatencyStats handler just after the <handlers xmlns="http://ws.apache.org/ns/synapse"> tag. Code Block |
---|
| <handler class="com.wso2.finance.open.banking.management.information.reporting.data.publisher.APIInvocationLatencyStatsHandler"/> |
Add the APIInvocationDataPublisher handler as the last ob-specific handler, right before the ## end of ob-specific handlers before the APIManagerExtensionHandler line. Code Block |
---|
<handler class="com.wso2.finance.open.banking.management.information.reporting.data.publisher.APIInvocationDataPublisher" />
## end of ob-specific handlers before the APIManagerExtensionHandler |
Note |
---|
Republish all the APIs for the above changes to take effect. |
Multiexcerpt |
---|
MultiExcerptName | InvocationFailure |
---|
| Capturing data during invocation failure scenariosThis is available only as a WUM update and is effective from December 20, 2019 (12-20-2019). For more information on updating WSO2 Open Banking, see Updating WSO2 Products . - 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 the OBErrorDataPublisher class below the sequence key element as shown below: xml
|
Configuring Open Banking Business IntelligenceConfiguring databasesCreate the following databases in your database server to store raw and summarized data. openbank_ob_reporting_statsdb openbank_ob_reporting_summarizeddb
Configuring datasourcesUpdate the <WSO2_OB_BI_HOME>/conf/worker/deployment.yaml file by adding the datasource configurations for OB_REPORTING_DB and OB_REPORTING_SUMMARIZED_DB . - Update the
jdbcUrl , username , password and driverClassName in the datasource entry with your database configurations. - Add the configurations after the
TRA_DB datasource configurations. A sample configuration is given below:
Code Block |
---|
| - name: OB_REPORTING_DB
description: The datasource used to store statistics for OB MI module
jndiConfig:
name: jdbc/OB_REPORTING_DB
definition:
type: RDBMS
configuration:
jdbcUrl: 'jdbc:sqlserver://192.168.108.23:1433;databaseName=openbank_ob_reporting_statsdb'
username: 'root'
password: 'root'
driverClassName: 'com.microsoft.sqlserver.jdbc.SQLServerDriver'
maxPoolSize: 20
idleTimeout: 60000
connectionTestQuery: SELECT 1
validationTimeout: 30000
isAutoCommit: false
- name: OB_REPORTING_SUMMARIZED_DB
description: The datasource used to store summarized data for OB MI module
jndiConfig:
name: jdbc/OB_REPORTING_SUMMARIZED_DB
definition:
type: RDBMS
configuration:
jdbcUrl: 'jdbc:sqlserver://192.168.108.23:1433;databaseName=openbank_ob_reporting_summarizeddb'
username: 'root'
password: 'root'
driverClassName: 'com.microsoft.sqlserver.jdbc.SQLServerDriver'
maxPoolSize: 20
idleTimeout: 60000
connectionTestQuery: SELECT 1
validationTimeout: 30000
isAutoCommit: false |
Adding summarization script- Download the
OB_REPORT_SUMMERIZATION_MSSQl.siddhi script from here. - Place the script in the
<WSO2_OB_BI_HOME>/deployment/siddhi-files directory.
Restart the WSO2 Open Banking Business Intelligence, Key Manager and API Manager servers in the mentioned order, for the changes to take place. |