

Set up Accelerators with WSO2 Identity Server¶

This section guides you to set up and prepare your server to run WSO2 Open Banking Accelerator.

Step 1: Set up WSO2 Open Banking Accelerator for WSO2 Identity Server¶

Copy the extracted accelerator directory into the root directory of the WSO2 Identity Server.

File	Directory location to place the Accelerator
`wso2-fsiam-accelerator-4.x.0`	`<IS_HOME>`

Tip

This documentation will refer to the above-extracted directory of the accelerator as <OB_IS_ACCELERATOR_HOME>.

Step 2: Configure database scripts¶

Note

WSO2 Open Banking Accelerator is compatible with the following DBMSs:

MySQL 8.0
Oracle 19c
Microsoft SQL Server 2022
PostgreSQL 17.2

This section explains how to set up the solution with a MySQL 8.0 database server. For other DBMS, see Setting up databases.

Open the <IS_HOME>/<OB_IS_ACCELERATOR_HOME>/repository/conf/configure.properties file.
Configure the hostnames of the Identity Server.
Configure database-related properties and database names.
Modify the product version in the IS_PRODUCT and PRODUCT_CONF_PATH parameters to match the base product version.

Step 3: Set up the IS server¶

Run the merge script in <IS_HOME>/<OB_IS_ACCELERATOR_HOME>/bin:
On Linux
```
./merge.sh
```
On Mac
```
./merge.sh
```
On Windows
```
./merge.ps1
```
Run the configure file in <IS_HOME>/<OB_IS_ACCELERATOR_HOME>/bin:
Linux
```
./configure.sh
```
On Mac
```
./configure.sh
```
On Windows
```
./configure.ps1
```
If you are using Windows platform...
If you are using Windows platform, since the merge.ps1 and configure.ps1 files are not digitally signed yet, your PowerShell might prevent you from running them normally. In that case, you may need to run these scripts in a PowerShell instance where its execution policy is set to bypass mode.

Use the following command to run these scripts in execution policy bypassed PowerShell environment:
```
powershell -executionpolicy bypass .\merge.ps1
```
```
powershell -executionpolicy bypass .\configure.ps1
```
IMPORTANT: Do not run any other unverified scripts using this method. This is a temporary solution.
Run the database script that resides in the <IS_HOME>/dbscripts/financial-services/event-notifications directory to create database tables for the event notification feature in the fs_consentdb database.

Step 4: Upload Root and Issuer Certificates¶

Upload the root and issuer certificates of OBIE (Sandbox Certificates | Production Certificates) to the client trust stores in <IS_HOME>/repository/resources/security/client-truststore.p12 using the following command:

keytool -import -alias <alias> -file <certificate_location> -keystore <truststore_location> -storepass wso2carbon

Step 5: Start the Server¶

Run the following command in <IS_HOME>/bin:
```
./wso2server.sh
```

Top