Advanced configuration for Helm Charts installation
Use the following YAML to configure your IBM Process Mining instance:
# Process Mining Application Configuration
# General settings for the Process Mining application
processmining:
# Storage configuration for Process Mining data
storage:
# Events storage configuration (persistent volume for event data)
events:
create: false
name: 'pm-repository-events'
# Logging Configuration
# Sets the application log level (DEBUG, INFO, WARN, ERROR)
loglevel: DEBUG
# Task Mining Configuration
# Enables and configures Task Mining features
taskmining:
install: true
agent_plugin: true
# Email Configuration
# Configures SMTP settings for sending email notifications and alerts
email:
from: "processminingdevops@mycompany.com" #this is address for mail sender
user: "processminingdevops@mycompany.com" # user for smtp authentication
password: ""
# SMTP server configuration
smtp:
starttls:
enable: false
required: false
auth: false
host: "smtp.mysmtpserver.com"
port: "25"
socketFactory:
port: "465"
fallback: false
# SendGrid API configuration (alternative to SMTP)
sendgrid:
apikey: ""
# Authentication Configuration
# Configures user authentication method (ldap, saml, or local)
authentication:
mode: "ldap"
# LDAP authentication settings
ldap:
url: "ldaps://my.ldap.server:636"
type: "query"
searchBase : "ou=myorg,o=mycompany.com"
filter: "preferredIdentity"
bindDN: ""
bindPassword: ""
userFilter: "(&(preferredIdentity=%s)(objectclass=person))"
Using Ingress
It is possible to expose the IBM Process Mining URL using a custom URL (for example, https://ipm.mycompany.com) instead of the default route exposed by OpenShift Container Platform.
You must expose the endpoint by using TLS.
Note: To learn how to create a TLS secret, see Kubernetes.io/TLS.
To enable this feature, you must set the following values:
ingress:
host: '<MY FQDN>'
tlsSecret: '<TLS SECRET NAME>'
<TLS SECRET NAME> is the secret that contains the certificates for TLS.