Preparing to install IBM Match 360 with Watson
Plan and prepare to install IBM® Match 360 with Watson™.
Required tasks
Depending on your deployment scenario, one or more of the following tasks might be required
before installing IBM Match
360:
- If you are deploying onto a FIPS 140-2 compliant cluster: Configure the cluster to enable IBM Match 360 compliance with FIPS 140-2 (required for FIPS compliance)
- Configure the cluster to enable IBM Match 360 compliance with FIPS 140-2 (required for FIPS compliance)
-
Additional configuration is required to enable IBM Match 360 to be installed and used on a Federal Information Processing Standards (FIPS) 140-2 compliant Red Hat® OpenShift® cluster. For details, see Enabling IBM Match 360 for FIPS compliance.
Required role: To complete this task, you must be a cluster administrator.
Optional tasks
The following tasks are optional before installing IBM Match
360:
- Provide self-defined credentials to use instead of generated credentials
-
By default, the IBM Match 360 installation generates credentials that are used for authenticating the service to IBM WebSphere® Liberty Profile, RabbitMQ, Elasticsearch, and Redis. If you choose, you can define your own credentials to use in place of the generated ones.
Note: Credentials must be at least 8 characters in length and contain at least one lowercase letter, one uppercase letter, and one number. If invalid credentials are provided, the operator logs an error and uses generated credentials instead.Required role: To complete this task, you must be a cluster administrator.
To define and provide your own credentials before installing IBM Match 360, create a secret containing your chosen credentials namedmdm-user-defined-auth
. Use the following format:secrets: user_defined_auth: name: mdm-user-defined-auth elasticsearch: password: elasticsearch.password rabbitmq: erlang_cookie: rabbitmq.erlang-cookie management_password: rabbitmq.management-password password: rabbitmq.password redis: compose_password: redis.compose_password wlp: keystore_pass: wlp.key.store.password
Sample secret template:apiVersion: v1 data: elasticsearch.password: [ENCODED_CRED] rabbitmq.management-password: [ENCODED_CRED] rabbitmq.password: [ENCODED_CRED] rabbitmq.erlang-cookie: [ENCODED_CRED] redis.compose_password: [ENCODED_CRED] wlp.key.store.password: [ENCODED_CRED] kind: Secret metadata: name: mdm-user-defined-auth namespace: $MDM_OPERAND_NAMESPACE type: Opaque
Note: If you prefer to set your self-defined credentials after completing the installation, see Post-installation setup for IBM Match 360 with Watson.