Installation
Guideline for the installation of IBM Financial Services Workbench
IBM Financial Services Workbench is an add-on to IBM Cloud Pak for Data and runs on RedHat OpenShift.
The following picture shows exemplary the setup of IBM Financial Services Workbench. In this example a Dual Cluster topology is assumed. One cluster for development and testing purposes, one dedicated cluster for production workloads.
IBM Financial Services Workbench requires different third party components:
-
Git Provider- used as a central source code repository (currently GitLab, GitHub Enterprise and Bitbucket are supported).
-
MongoDB- used to store the design data as well as business data for the solutions developed with IBM Financial Services Workbench.
-
OpenShift Pipelines- used to build and deploy solutions.
-
Keycloak - Open ID Connect / SSO Server for the design environment; for deployed solutions the usage of a different OIDC Provider is supported.
-
Apache Kafka to support eventing for solutions (optional)
- OpenShift Service Mesh (optional)
In general, the process consists of these steps:
-
Check you meet the system requirements. See System Requirements
-
Decide which services (that you might already run) you want to use or whether you want to install all required dependencies on your cluster during installation of IBM Financial Services Workbench. This is suitable for small or PoC type deployments. See Installing Third-Party Components
-
Gather all configuration data needed for starting the installation of IBM Financial Services Workbench. See Pre-installation tasks for details.
-
Install and configure IBM Financial Services Workbench. See Installation Process
-
After installation of the core product, configure the installed Solution Hub and Solution Designer, verify that you can login to Solution Designer, configure one or more OpenShift projects as k5 projects. These are used to deploy and run the solutions you develop with IBM Financial Services Workbench. See Post-installation tasks for details.