Deploying the Health application

You deploy the Maximo Health operator responsible to control the Maximo Health deployment process and to maintain and update the application as necessary.

Procedure

  1. From the Suite catalog, on the Applications tab, select the Maximo Health tile, and review the information on the Setup page.
  2. In the Maximo Health deployment options dialog, choose to deploy Maximo Health as a part of Maximo Manage or without Maximo Manage. If you choose to deploy as part of Maximo Manage, click Deploy as part of Manage and complete the steps to deploy and activate Maximo Manage. If you choose to deploy without Maximo Manage, click Deploy without Manage and proceed to step 3. The following steps describe how to deploy Maximo Health without Maximo Manage.
  3. In the Administer application upgrades window, in the Upgrade strategy field, select one of the following upgrade strategies.
    Option Description
    Channel subscription
    1. To make sure that updates are automatically offered when an updated version is added to a channel, select Channel subscription. You can choose whether this update occurs automatically with a new version or requires manual approval. If you choose an automatic upgrade strategy through Channel subscription, required downtime might occur before you have a chance to review changes in the new version or fix pack, back up the database, or take other preparatory action. Therefore, for production Maximo Health deployments, set the approval mode to Manual. You can then be alerted about the availability of an update directly in the IBM® Maximo Application Suite application catalog, in the Maximo Health tile. However, the update is not started until you trigger it yourself. In this case, you can be better prepared by reviewing the changes, running backups of the Maximo Health configuration and custom resource definitions, scheduling the update, and communicating the scheduled downtime to users.
    2. In the Channel field, select a channel.
    3. In the Custom source field, specify a source.
    4. In the Channel details section, select whether to approve the update automatically or to require manual approval.
    5. Click Subscribe to channel.
    Manual
    1. To manually update the application when you are notified that an updated version is available, select Manual.
    2. In the Version field, select a version.

      Maximo Manage and Maximo Health are deployed by using the same processes. To start the deployment, even if you are deploying without Maximo Manage, you must select the current Maximo Manage version. During activation, you select the Maximo Health version.

    3. Click Deploy version.
  4. Configure the database connection information for Maximo Health.
    1. In the Integrations and dependencies section, on the Database connection tile, select Configure.
    2. In the Database connection page, click Configure.
    3. Under JDBC connection information, specify the following fields:
      Note:

      If you are upgrading from Maximo Asset Management to Maximo Application Suite, refer to the maximo.properties file of your Maximo Asset Management folder to get the values for hostname, port, database name to use in the jdbc url as required by .

      1. If you want to use an SSL-enabled connection, you can specify this field by using one of the following JDBC URL formats. Ensure that the Port that is used contains the SSL-enabled port of the database.
        Oracle Database
        TCPS is the protocol to use for Oracle SSL connections. For Oracle SSL database connections in Maximo Health, you must specify SID=<TNS Service ID>. You can use the following URL as an example:
        jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(Host=mymaximodb.com)(Port=2484))(CONNECT_DATA=(SID=MAXDB)))
        Microsoft SQL Server Database
        For SQL Server SSL database connections in Maximo Health, you must specify encrypt=true. Ensure that you use a semicolon to end the JDBC connection string. You can use the following URL as an example:
        jdbc:sqlserver://mymaximodb.com:1433;databaseName=MAXDB;encrypt=false;
        IBM Db2® database
        For Db2 SSL database connections in Maximo Health, you must specify sslConnection=true. Ensure that you use a semicolon to end the JDBC connection string. You can use the following URL as an example:
        jdbc:db2://mymaximodb.com:50001/MAXDB:sslConnection=true;
        1. In the User name field, specify the database username.
        2. In the Password field, specify the database user password.
        3. Ensure that you select the SSL Enabled option.
      2. If you want to use non-SSL enabled connection, specify the Connection string field by using one of the following JDBC URL formats, depending on the database you are using.
        Oracle Database
        You can use the following URL as an example:
        jdbc:oracle:thin:@mymaximodb.com:1521:MAXDB
        Microsoft SQL Server database
        You can use the following URL as an example:
        jdbc:sqlserver://mymaximodb.com:1433;databaseName=MAXDB;integratedSecurity=false;encrypt=false;
        IBM Db2 database
        You can use the following URL as an example:
        jdbc:db2://mymaximodb.com:50001/MAXDB
        1. In the User name field, specify the database username.
        2. In the Password field, specify the database user password.
        3. Ensure that you do not select the SSL Enabled option.
    4. Optional: In the Additional driver options section, in the Driver options field, add more driver options, which are separated by a semicolon.
      • Typically, you can specify JDBC options as part of the URL for the database. However, in some cases you might want to specify JDBC options in the Driver options field.
      For example, your URL might exceed the maximum length that is allowed, or you might want to configure a JDBC option that cannot be included in the connection URL. You cannot specify the same JDBC option in both the URL and the Driver options field. If you do, JDBC driver errors might cause the connection to fail.
      • If you specify an extra JDBC option for your database, the CustomProxyDriver acts as a proxy driver that routes the database requests to the actual driver for your type of database.
    5. If you chose to use an SSL-enabled database connection, in the "Security > Certificates (optional)" section, click Add+ to display the fields to include in your database certificate.
      1. In the Alias field, specify an alias name to identify the certificate, for example, DB2WHcert.
      2. In the Certificate content field, copy and paste your certificate in the format that is mentioned in the field content. You can retrieve a PEM certificate for your database. The file must be a Base-64 encoded X.509 file. You do not need to retrieve a private key. For more information, see the documentation for your database. After you copy and paste the text into the field, including the BEGIN CERTIFICATE, and END CERTIFICATE text, click Confirm.
    6. If you chose to use an SSL-enabled database connection, in the "Security > Certificates (optional)" section, click Add+ to display the fields to include in your database certificate.
      1. In the Alias field, specify an alias name to identify the certificate, for example, DB2WHcert.
      2. In the Certificate content field, copy and paste your certificate in the format that is mentioned in the field content. You can retrieve a PEM certificate for your database. The file must be a Base-64 encoded X.509 file. You do not need to retrieve a private key. For more information, see the documentation for your database. After you copy and paste the text into the field, including the BEGIN CERTIFICATE, and END CERTIFICATE text, click Confirm.
    7. Click Save. The Database connection page is closed.
    8. Click in the Database connection tile to verify your database connection. Expand the Status icon that is loading in the "Configuration-scope-Workspace-application" section to display some tiles. Click Select once the Status icon is ready to close the page.
      Note: Click Save and Select in the previous step if you do not want to wait for the database connection verification after you complete the fields.
    9. If you plan to deploy Maximo Optimizer, see Deploying Maximo Optimizer.
    10. In the Components section, select Maximo Health and for the version, select 8.6.0.
  5. In the Integrations and dependencies section, on the IBM Watson Studio tile, specify details of the Watson™ Studio.
    • If you have configured Watson Studio, click View and then click Select.
    • If you have not configured Watson Studio, click Configure, select a scope, specify the details and then click Save and select.
  6. Click Show advanced settings to view and specify the configuration settings, such as database, server bundle, language settings, and others. In the Database section, clear the System managed checkbox and manually configure the database.
    Schema
    Enter the name of the schema that is configured in your database. For more database configuration information for Maximo Health, see Setting up your database.
    Encryption secret (optional)
    This value is optional if you are deploying Maximo Health in your database for the first time, and your database is not encrypted. You must enter your encryption keys for this parameter. For more encryption settings information, see Database encryption.

    In the Key/Value table, click Add property +. In the Key column, enter MXE_SECURITY_CRYPTOX_KEY and in the Value column, enter your encryption key value.

    In the Key/Value table, click Add property +. In the Key column, enter MXE_SECURITY_CRYPTO_KEY and in the Value column, enter your encryption key value.

    Table space
    If the default value does not match your database configuration, enter the name of the table space that was configured in your database. For more database configuration information for Maximo Health, see Setting up your database.
    Index space
    If the default value does not match your database configuration, enter the name of the index table space that was configured in your database. For more database configuration information for Maximo Health, see Setting up your database.
    Db2 Vargraphic
    If you use Db2 and you plan to install a language other than English for your base language or as an additional language, select this option. If you intend to add more languages later, select this option during your initial deployment. This option does not affect the Maximo Health deployment if it is selected and you are using a database other than Db2.
    Bypass upgrade version check
    Select this option to skip validation of the IBM Maximo Asset Management version you are upgrading to . Select this option to continue a failed upgrade that failed during the maxinst or updatedb process.
  7. If you want to set Maximo Health with a language different from English or include other languages in your Maximo Health deployment, clear the System Managed checkbox in the Languages section.
    Then, in the Base field, select your preferred language to be the base language and in the Additional field, order the list of other languages. For more information, see Language support.
    Note: If you are selecting other languages, make sure that you do not select a language in the Additional field that was selected in the Base field. For example, if you set the base as EN, do not select EN in the Additional field.
  8. If you want to include specific customizations through a customization archive, clear the System managed checkbox in the Customizations section. In the File address field, specify the location of the customization archive and if you must enter credentials to access the file, specify them in the Credentials (optional) field. For more information, see the related sections in Customizing the application.
    1. In the Customization section of the configuration window, specify the URL for the customization archive file.
      The following URL protocols are supported:
      • HTTP
      • HTTPS
      • FTP
      • FTPS
      To include more customization archive files, click Add customization archive.
    2. Optional: If you applied password security to the file, in the Credentials field, specify the user ID and password in the following format:
      user=your user name password=your password
  9. If you do not want the server bundles to start after the database operations of the Maximo Health deployment are completed, clear the System managed checkbox in the Server mode section.
    Then, set Mode to Off to prevent access to the Maximo Health application after deployment. You can restart the server bundle or bundles when you change the configuration to On and activate Maximo Health again.
  10. To connect to PVCs under the Persistent volume claims section, clear the System managed to Off, and click Add PVC. A table with the following columns is displayed.
    Option Description
    PVC name User-defined name of the persistent volume claim, maximum of 63 characters
    Volume name Leave blank as it is provisioned dynamically.
    Size The amount of storage that is required for this persistent claim, for example, 60G
    Mount path Mount path for the volume within the Maximo Health pod.
    When you configure the PVCs in OCP cluster on deployments, use the default storage class name StorageClasses ocs-storagecluster-cephfs to create a ReadWriteMany (rwx) PVC. The storage in the volume that you provisioned are available to all server bundles in the workspace. You can also configure a PVC for specific server bundles in a deployment. If you configure a PVC for a server bundle, the mount path that you specify for the server bundle PVC overrides the path that you specify for the deployment.
    Tip: To configure a PVC in OCP cluster on IBM Cloud® platform, use the default StorageClasses ibmc-file-gold-gid (instead of StorageClasses ocs-storagecluster-cephfs) to create a ReadWriteMany PVC.
    Note: You can activate Maximo Health or you can set the build tag.
  11. If you want to use an earlier build for deployment, in the Build section, set System managed to Off.
    Then, in the Build tag field, specify the build tag. Build images are tagged with a timestamp, for example buildtag: 202011092887843.
  12. To connect to any external systems that Maximo Health is integrated with, import the certificate for the system.
  13. Optional: You might want to specify the time zone that your database server is configured to use. In the "Server time zone" section, clear the System Managed checkbox. In the Time Zone field, select the time zone of your database server.
  14. If you are deploying Maximo Health, you can enable asset investment optimization. In the "Asset investment optimization" section, clear the System managed checkbox. Then, select Asset investment optimization. When asset investment optimization is enabled, the Asset investment optimizer page is available in Maximo Health. Make sure that you deploy and configure Maximo Scheduler Optimization before you enable asset investment optimization.
  15. If you have IBM Watson® Studio, you can set the existing project ID that Maximo Health can use. In the IBM Watson Studio section, clear the System managed checkbox and then specify the Watson Studio project ID.
  16. If you want to use IBM App Connect to load data, you can specify the dashboard URL so that Maximo Health can deploy the configuration files for out-of-box data loader and create the integration server. In the IBM App Connect section, clear the System managed checkbox and then specify the Dashboard URL.