Optional: Installing containerized external MonetDB
You can use a containerized external MonetDB instance and use it as a IBM Process Mining database.
Deploying a standalone MonetDB
You can deploy a MonetDB instance through the operator. You can create any number of MonetDB
instances and connect them with a process mining instance.
External MonetDB
It is possible to connect IBM Process Mining with an external instance of MonetDB. See the following configuration example of CRD
configuration:
apiVersion: processmining.ibm.com/v1beta1
kind: ProcessMining
metadata:
name: pm
spec:
processmining:
monetdb:
external:
host: monetdb-srv1-monetdb-service.processmining.svc.cluster.local
database: processmining
user: monetdb
credential:
passwordkey: password
secretname: monetdb-srv1-monetdb-secret
port: 50000
create: falseConfiguring MonetDB CRD
Use the following examples of CRD configuration for MonetDB connection to configure your own instance:
- Basic configuration:
apiVersion: processmining.ibm.com/v1alpha1 kind: MonetDb metadata: name: monetdb-srv1 spec: storage: size: 32 - Add the
datasourcesection under MonetDB in Administration > CRD > processmining > pminstance > YAML:datasources: - name: ds_1 host: "monetdb-srv1-monetdb-service.processmining.svc.cluster.local" database: processmining user: monetdb credential: passwordkey: password secretname: monetdb-srv1-monetdb-secret port: 50000 - name: ds_2 host: "monetdb-srv2-monetdb-service.processmining.svc.cluster.local" credential: passwordkey: password secretname: monetdb-srv2-monetdb-secret - Advanced configuration:
With the advanced configuration, you can provide a PVC that was already created. You can also provide a node selector, which is based on a label forcing the pod to be executed on a specific cluster node.apiVersion: processmining.ibm.com/v1alpha1 kind: MonetDb metadata: name: monetdb-srv1 spec: storage: size: 32 create: false name: monetdb-external-pvc nodeselector: key: targetMonet value: pmComputationNode1
The following list indicates the default connection settings:
- Database: processmining
- User: monetdb
- Port: 50000
- Password:
- Stored in the
<NAME>-monetdb-secretsecret - Data field:
password
- Stored in the
Note: Your password is stored in the secret named
<NAME>-monetd-secret.See Custom resource definition (CRD) and MonetDB Custom Resource Specification, to learn more about advanced CRD configuration for MonetDB.
Enabling MonetDB partitioning
To enable MonetDB partitioning, you need to deploy at least two MonetDB instances.
Note: The name of every next MonetDB instance must be changed sequentially; i.e.
srv2, srv3,
srv4 etc.Use the following CRD configuration to enable MonetDB
partitioning:
apiVersion: processmining.ibm.com/v1beta1
kind: ProcessMining
metadata:
name: pm
spec:
processmining:
monetdb:
external:
host: monetdb-srv1-monetdb-service.processmining.svc.cluster.local
database: processmining
user: monetdb
credential:
passwordkey: password
secretname: monetdb-srv1-monetdb-secret
port: 50000
create: false
datasources:
- name: ds_1
host: "monetdb-srv1-monetdb-service.processmining.svc.cluster.local"
database: processmining
user: monetdb
credential:
passwordkey: password
secretname: monetdb-srv1-monetdb-secret
port: 50000
- name: ds_2
host: "monetdb-srv2-monetdb-service.processmining.svc.cluster.local"
credential:
passwordkey: password
secretname: monetdb-srv2-monetdb-secretNote: For
ds_2, the port is missing because the configuration is using the default
value.See Custom resource definition (CRD), to learn more about CRD configuration.
Note: Your password is stored in the secret named
<NAME>-monetd-secret.