Installing client managed IBM Maximo Application Suite for private paid offer

The paid AWS product can be installed from the AWS Marketplace based on your infrastructure needs. A new Red Hat® OpenShift® instance is created as part of the Maximo® Application Suite installation.

Before you begin

Before you can install Maximo Application Suite on Amazon Web Services, you must configure prerequisites and gather information that you need to complete the installation.

For more information, see Prerequisites for installing Maximo Application Suite on Amazon Web Services.

Consider other criteria, such as the type of Maximo Application Suite offering that you want and whether you want to create a Red Hat OpenShift cluster or reuse an existing one.
Note: The existing cluster must be created by using the automated deployment option only.
For more information, see Preparing to install Maximo Application Suite on Amazon Web Services.
This product requires an internet connection to deploy properly. The following code is downloaded on deployment for setting up the Maximo Application Suite Red Hat OpenShift Container Platform cluster:

About this task

The Maximo Application Suite client-managed solution is available with two different Marketplace products.

Maximo Application Suite client-managed with Red Hat OpenShift entitlement
This product includes the subscription for the Red Hat OpenShift cluster that is deployed during the installation process.
The following CloudFormation templates are available as fulfillment options:
  • A new Red Hat OpenShift cluster by using the Installer Provisioned Infrastructure (IPI)
  • A new Red Hat OpenShift cluster by using the User Provisioned Infrastructure (UPI)
Maximo Application Suite client-managed without Red Hat OpenShift entitlement
This product does not include the subscription for the Red Hat OpenShift cluster that is deployed during the installation process or the existing one provided by the user. You must have your own Red Hat OpenShift subscription to deploy Maximo Application Suite by using this product.
The following CloudFormation templates are available as fulfillment options:
  • An existing Red Hat OpenShift cluster
  • A new Red Hat OpenShift cluster by using the Installer Provisioned Infrastructure (IPI)
  • A new Red Hat OpenShift cluster by using the User Provisioned Infrastructure (UPI)

After you select the Paid product from Amazon Web Services Marketplace, you can complete the following steps for a private paid offering.

You can avail a private offer for IBM Maximo Application Suite subscription contract with custom configuration and pricing by contacting a IBM sales representative or viewing https://www.ibm.com/products/maximo/pricing page. After discussions and agreements, the IBM sales representatives share the offer URL page link.

Procedure

  1. Click the private URL shared by the IBM sales representatives, and click Continue to Subscribe.
  2. Review the number of AppPoints, contract duration, and contract pricing information for the private offer, and click Create Contract.
  3. Confirm the contract terms on the confirmation dialog.
    You see a message that AWS is processing the request. It takes couple of minutes to complete the processing. Until then, Continue to Configuration is unavailable and for Create Contract displays the label as Pending.
  4. After you confirm the contract terms of purchase to register the product with your AWS account, complete the registration by using an IBM ID from https://www.ibm.com/marketplace/connector/landing/aws/services/amicontractsetup. You can also get this URL from the Overview section of the product page.
    Select the Maximo Application Suite product for which you subscribed, provide the necessary details like the AWS account number, and confirm the pending order by verifying the quotation number. You see the product summary page for your purchase. The browser tab can be closed. You receive an email notification within few minutes to obtain the IBM entitlement key from My IBM portal required for the product deployment.
  5. After you retrieve the entitlement key, link your IBM Maximo Application Suite subscription with Red Hat OpenShift account by following the steps at https://www.ibm.com/docs/en/cloud-paks/1.0?topic=iocpc-accessing-red-hat-entitlements-from-your-cloud-paks, obtain the Red Hat OpenShift pull secret from the Red Hat OpenShift account, return to product page, and click Continue to Configuration.
    Note: Linking the IBM Maximo Application Suite subscription with Red Hat OpenShift account is required only if you are deploying IBM Maximo Application Suite with new Red Hat OpenShift cluster. It is not required if you decide to use existing Red Hat OpenShift cluster. (Support for existing Red Hat OpenShift cluster is not available yet.)
  6. In Fulfillment option, select the appropriate deployment mode.
    For Maximo Application Suite deployment with new Red Hat OpenShift cluster, you can select either new network infrastructure (IPI) or existing network infrastructure (UPI), or existing Red Hat OpenShift cluster. For more information, refer to the fulfillment options explained earlier in this section.
  7. In Software version, select the latest version.
  8. In Region, select a supported geographical region where you want to install the Maximo Application Suite.
  9. Accept the default values in the other fields and click Continue to Launch.
  10. In the Launch page, select Choose Action > Launch CloudFormation.
  11. To open the CloudFormation stack wizard, click Launch.
  12. In the Create stack wizard step, accept the default values, and click Next.
  13. In the Specify stack details step, in the Stack name section, enter a unique name.
  14. In the Parameters section, enter the installation parameters by using the information that you gathered when you configured the Prerequisites for installing Maximo Application Suite on Amazon Web Services and Preparing to install Maximo Application Suite on Amazon Web Services.
  15. Enter all of the mandatory parameters.
    • The Maximo Application Suite offering type, such as Maximo Application Suite Core and Cloud Pak for Data or Maximo Application Suite and Maximo Manage.
      Note: If you choose to install Maximo Application Suite with Manage, you can use the default IBM Db2® instance that is provisioned by IBM instead of configuring your own external Db2 instance. To configure the default IBM Db2, do not add information in the username, password, JDBC URL, certificate URL, and demo data fields.

      The internal Db2 configuration is available from Maximo Application Suite 8.10 or later.

    • All of the parameters in the Cluster and bootnode access and Keys and licenses sections.
  16. To create a new cluster, complete the New OpenShift cluster configuration details section.
  17. In the optional parameter groups, such as the group of Maximo Manage database configuration parameters, ensure that you either specify all of the parameter values or leave all of them empty.
  18. To configure Amazon Managed Streaming for Kafka, select Yes.
    The Amazon Managed Streaming for Kafka is configured to process data streaming of applications such as IoT and IBM Maximo Monitor from Maximo Application Suite.

    You can configure the default Amazon Managed Streaming from Maximo Application Suite 8.10. or later.

  19. To configure a DocumentDB instance, you can select any of the following options.
    • Configure a new MongoDB community edition
    • Use an existing MongoDB

      You must input existing MongoDB connection details such as the username, password, MongoDB hostname, and CA certificate.

    • Configure a new Amazon DocumentDB
    • Use an existing Amazon DocumentDB

      Add existing DocumentDB connection details such as the username, password, DocumentDB hostname, and CA certificate.

      You must input the VPC ID of the region in which the Amazon DocumentDB is deployed. Ensure that the DocumentDB does not have a matching or overlapping IPv4 CIDR block 10.0.0.0/16.

    You can configure the default DocumentDB from Maximo Application Suite 8.10. or later.

  20. In the Other parameters, select the OperationalMode as Production or Non-production.
    You can specify deployments for Production or Nonproduction environments. Nonproduction installations can be used for internal development and testing. The installation AppPoints are unused in the Non-production installations. These specifications are also visible in the metrics shared with IBM as well as on the product UI.
  21. Click Next.
  22. In the Configure stack options step, configure any additional options that you require . To know more about the stack options, click the "Learn more" links available in each option. Click Next when done.
  23. In the Review step, review the values that you entered and acknowledge the message that relates to identity and access management (IAM) resources.
  24. To begin the installation, click Create stack.

What to do next

During the installation process, the AWS CloudFormation stack template that you configured is used to create a Bootnode. The Bootnode contains all required resources to complete the installation. To verify that the Bootnode is created successfully, in the CloudFormation > Stacks page, confirm that the stack status is updated to CREATE_IN_PROGRESS

For more information, see Monitoring IBM Maximo Application Suite installation on Amazon Web Services.