The IBM® Maximo® Application Suite (BYOL) can be installed from the Amazon Web Services Marketplace based on your infrastructure needs. You can install a new
Red Hat® OpenShift® cluster before you install Maximo Application Suite
or you can use your existing Red Hat OpenShift cluster to install Maximo Application Suite.
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 following three fulfillment options (CloudFormation templates) are
available for installing
Maximo Application Suite:
- New Red Hat OpenShift cluster by using the Installer Provisioned
Infrastructure (IPI)
- New Red Hat OpenShift cluster by using the User Provisioned Infrastructure
(UPI)
- Existing Red Hat OpenShift cluster
Note: Starting in 8.11, for US GovCloud regions, you can install Maximo Application Suite in private hosted zones for existing Red Hat OpenShift cluster
and New Red Hat OpenShift cluster by using the User Provisioned Infrastructure
(UPI).
Procedure
-
In the AWS Marketplace service console, click Discover product and
search for
IBM Maximo Application Suite (BYOL)
. The product is sold by
IBM
Maximo.
- Open Maximo Application Suite.
- Review the product information to select a fulfillment option and click
Continue to Subscribe.
- In the subscription page, to create the subscription, review the terms and conditions and
click Accept Terms.
- After the subscription is created, click Continue to
Configuration.
- In the configuration page, in the Region field, select a supported
geographical region where you want to install the Maximo Application Suite.
- Accept the default values in the other fields and click Continue to
Launch.
- In the Launch page, select .
- To open the CloudFormation stack wizard, click
Launch.
- In the Create stack wizard step, accept the default values, and
click Next.
- In the Specify stack details step, in the Stack
name section, enter a unique name.
- 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.
- Enter 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.
Starting in 8.11, for US GovCloud
regions, you can configure the offering type Maximo Application Suite Core or Maximo Application Suite and
Maximo Manage. Cloud Pak for Data is not available for configuration.
- All parameters in the Cluster and bootnode access and Keys and
licenses sections.
- To reuse an existing Red Hat OpenShift cluster, complete the
Existing Red Hat OpenShift cluster connection details
section.
- To reuse an existing network infrastructure, complete the
steps that are given in Connection details
for using an existing network infrastructure section.
- In the optional parameter groups, such as the group of IBM Maximo Manage database configuration parameters, ensure that you either specify all parameter values or leave
all empty.
Note: Follow the instructions commented in the field to know how to fill them. For the field
MASManageDBJdbcUrl
, you can specify it by using one of the following JDBC URL
formats. Ensure that the Port that is used contains the SSL enabled port of the database.
- IBM Db2®
- For Db2 SSL database connections in Maximo Manage, 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;
- Oracle Database
- Starting in 8.11, for US GovCloud regions, you can configure an Oracle Database. You must ensure that the Oracle Database follows
the Federal Information Processing Standard (FIPS).
For more information, see Configuring Oracle Database
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.
- To configure Amazon Managed Streaming for Kafka, select Yes.
The
Amazon Managed Streaming for
Kafka is configured to
process streaming data 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.
Starting in 8.11, for US GovCloud regions, Amazon Managed Streaming for Kafka configuration is
not required.
- To configure a DocumentDB instance, you can select any of
the following options.
- Configure a new MongoDB community edition.
- Use an existing MongoDB
Add existing MongoDB connection details such as the username, password, MongoDB hostname, and CA certificate.
Starting in 8.11, for US GovCloud
regions, you must ensure your existing MongoDB connection is FIPS
compliant.
- 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.
Add 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.
Starting in 8.11, for US GovCloud regions, DocumentDB is not
available for configuration.
- 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
Nonproduction installations. These specifications are also visible in the metrics that are shared
with IBM and on the product UI.
- Click Next.
- 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.
- In the Review step, review the values that you entered and
acknowledge the message that relates to identity and access management (IAM) resources.
- 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
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.