MongoDB

Maximo® Application Suite and Suite License Service use MongoDB for user management. The MongoDB instance can run in the Red Hat® OpenShift® cluster or external to it.

Prerequisites

To complete the setup of Maximo Application Suite, note the following MongoDB requirements.

  • The hostnames and ports of the MongoDB servers.
  • The Config db name the database name that is used by MongoDB to store its user IDs.
  • The user credentials for an admin user who has table creation authority.
  • The MongoDB certificate authority (CA) certificates. If your MongoDB cluster uses self-signed CA certificates, you must retrieve them automatically or add them manually when you complete the setting up the Maximo Application Suite.
Note:
  • Starting in 9.0.5 and 9.1, if Maximo Application Suite core and Maximo Manage base are configured on IBM® System/390x architecture, MongoDB is supported as an external service.
  • Starting in 9.0.12 and 9.1, if Maximo Application Suite core and Maximo Manage base are configured on IBM Power (ppc64le) architecture,MongoDB is supported as an external service.

For more information, see Software Product Compatibility Reports (SPCR).

To work with Maximo Application Suite, your MongoDB instance must support the transport layer security (TLS) communication protocol. For more information, see TLS/SSL (Transport Encryption) in the MongoDB documentation.

Federal Information Processing Standard (FIPS)
Starting with Maximo Application Suite 8.10.1, FIPS mode can be enabled. You can continue to use the MongoDB Community Edition for Maximo Application Suite in FIPS mode. However, if you want to have a FIPS compliant MongoDB instance as well, you must use MongoDB Enterprise Edition with your own license.
If FIPS is enabled for Maximo Application Suite, DocumentDB cannot be used as a dependency for Maximo Application Suite because DocumentDB does not support SCRAM-SHA-256 authentication, which is required by Maximo Application Suite in FIPS mode.
Certain components in Maximo Application Suite use the IBM Java™ Semeru Runtime, which has limited cipher support in FIPS Mode.
If the Maximo Application Suite is running in FIPS mode and configured to use the MongoDB instance in FIPS mode, ensure that the subset of ciphers that are supported by IBM Java Semeru are enabled for FIPS mode.
Table 1. Supported ciphers
Ciphers Name (OpenSSL) Cipher suite Name (IANA)
0xC024 ECDHE-ECDSA-AES256-SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
0xC028 ECDHE-RSA-AES256-SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
0xC023 ECDHE-ECDSA-AES128-SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
0xC027 ECDHE-RSA-AES128-SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
0xC026 ECDH-ECDSA-AES256-SHA384 TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
0xC02A ECDH-RSA-AES256-SHA384 TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
0xC025 ECDH-ECDSA-AES128-SHA256 TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
0xC029 ECDH-RSA-AES128-SHA256 TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
0xC00A ECDHE-ECDSA-AES256-SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
0xC014 ECDHE-RSA-AES256-SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
0xC009 ECDHE-ECDSA-AES128-SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
0xC013 ECDHE-RSA-AES128-SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
0xC005 ECDH-ECDSA-AES256-SHA TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
0xC00F ECDH-RSA-AES256-SHA TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
0xC004 ECDH-ECDSA-AES128-SHA TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
0xC00E ECDH-RSA-AES128-SHA TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
Maximo Application Suite 8.9 or earlier

For Maximo Application Suite 8.9 or earlier, you can use the Community Edition of MongoDB. To set up MongoDB Community Edition on the Red Hat OpenShift cluster, use the Maximo Application Suite ansible devops collection.