Before You Deploy: The Art of Not Flying Blind
Welcome back to our MAS 9 installation series! In our first article, we took a high-altitude tour of the shift from WebSphere to OpenShift, discussing how MAS 9 embraces a cloud-native, containerized architecture. Now it’s time to roll up our sleeves and start the actual journey toward installation. But before we can install anything, we need to gather our supplies.
Read 👉🏽 Part 1: Shifting from WebSphere to OpenShift: Welcome to Your New Cloud-Native Adventure
Think of this phase like preparing for a cross-country road trip. You wouldn’t just hop in the car and start driving without checking if you have gas, a map (or GPS, for the modern folks), and maybe a few snacks. Similarly, installing MAS 9 on OpenShift requires some key ingredients that you’ll need to collect and verify before the fun begins. Forget one of these, and you’ll find yourself stranded somewhere between “almost installed” and “why isn’t this working?”
In this article, we’ll walk through the essential prerequisites for a Single Node OpenShift (SNO) installation, which is perfect for development, testing, or proof-of-concept environments. We’ll cover what you need, where to get it, and what to expect as you plan your deployment.
The Essential Ingredients: What You’ll Need Before Installation
Before you can install MAS 9 on OpenShift, you’ll need to gather several critical components. Let’s break these down into manageable pieces.
1. IBM Entitlement Key: Your Golden Ticket
The IBM Entitlement Key is essentially your access pass to IBM’s container registry. Without it, you won’t be able to pull the MAS images needed for installation. Think of it like the VIP lanyard at a tech conference: no lanyard, no access to the good sessions (or in this case, the container images).
How to obtain your IBM Entitlement Key:
- Navigate to the IBM Container Library at https://myibm.ibm.com/products-services/containerlibrary
- Log in with your IBMid (the same credentials you use for IBM support, Passport Advantage, etc.)
- Click “Copy key” to copy your entitlement key
- Store this key securely. You’ll need it during the MAS installation process
Pro tip: This key is tied to your IBM account and the products you’re entitled to use. If you’re working in a team environment, coordinate with whoever manages your IBM licensing to ensure you have access to the correct entitlements for MAS 9.
2. IBM License File (license.dat): Proof of Purchase
The license.dat file is your proof that you’ve actually purchased MAS. IBM uses an AppPoints licensing model for MAS 9, which provides flexibility in how you deploy and use the suite’s various applications. Your license file contains information about your available AppPoints and is required during installation.
How to obtain your license file:
- Go to the IBM License Key Center at https://licensing.flexnetoperations.com
- Log in with your IBM credentials
- Navigate to “Get Keys” and locate your Maximo Application Suite entitlements
- You should see entries for “IBM Maximo Application Suite AppPoint” licenses
- Download the license.dat file and store it securely
Important note: AppPoints are shared across your MAS environments. Even with concurrent users logged into multiple instances, they draw from the same pool. Plan your point allocation carefully, especially if you’re running Dev, Stage, and Production environments simultaneously.
3. Red Hat OpenShift Pull Secret: The Other Golden Ticket
Since MAS 9 runs on Red Hat OpenShift, you’ll need a pull secret from Red Hat to access the OpenShift container images. This is separate from your IBM entitlement key because OpenShift has its own container registry.
How to obtain your Red Hat pull secret:
- Navigate to the Red Hat Hybrid Cloud Console at https://console.redhat.com
- Log in with your Red Hat account credentials
- Go to OpenShift > Downloads and locate the pull secret section
- Download or copy the pull secret JSON and store it securely
You’ll use this pull secret when configuring your OpenShift cluster to authenticate with Red Hat’s container registry.
4. OpenShift Cluster Name and Base Domain: Your Address in the Cloud
Before installation, you need to decide on your cluster name and base domain. These form the foundation of how your MAS instance will be accessed. For a Single Node OpenShift (SNO) installation, you’ll typically use a format like:
Cluster Name: sno (or something descriptive like “masdev”)
Base Domain: mas.yourdomain.edu (or your organization’s domain)
The full cluster address will combine these as: [cluster-name].[base-domain] (e.g., sno.mas.yourdomain.edu).
DNS Configuration: Making Sure Everyone Can Find You
One of the most critical (and often overlooked) aspects of OpenShift installation is DNS configuration. MAS OpenShift requires specific DNS entries to function properly. Forget these, and you’ll spend hours wondering why nothing can connect to anything else.
Required DNS Entries for OpenShift (SNO):
For a Single Node Operator installation, you’ll need these three DNS entries pointing to your node’s IP address:
| DNS Entry | Points To | Purpose |
| api.[cluster].[domain] | Node IP (e.g., 10.70.14.17) | API server access |
| api-int.[cluster].[domain] | Node IP (e.g., 10.70.14.17) | Internal API access |
| *.apps.[cluster].[domain] | Node IP (e.g., 10.70.14.17) | Wildcard for application routes |
Additional DNS Entries for MAS Manage:
Once MAS is installed, you’ll also need DNS entries for the various MAS services. These typically include:
| DNS Entry | Purpose |
| admin.mas.[domain] | MAS Suite Administration |
| api.mas.[domain] | MAS API endpoint |
| auth.mas.[domain] | Authentication services |
| home.mas.[domain] | MAS Home page |
| *.home.mas.[domain] | Home subdomains |
| manage.mas.[domain] | Maximo Manage application |
| *.manage.mas.[domain] | Manage subdomains |
Heads up: Coordinate with your network team early. DNS changes can take time to propagate, and nothing kills momentum quite like waiting 24-48 hours for a DNS record to become available. The IT team will need time to create these entries, so submit your requests well in advance.
SSL Certificates: Trust, But Verify
MAS 9 requires SSL certificates for secure communications. You have two options: self-signed certificates for development/testing environments, or trusted CA certificates for production use.
Your certificates should cover the following domains:
- auth.mas.[yourdomain]
- admin.mas.[yourdomain]
- home.mas.[yourdomain]
- [workspace].manage.mas.[yourdomain]
- [workspace].home.mas.[yourdomain]
- api.mas.[yourdomain]
For production environments: Work with your security team to obtain certificates from your organization’s trusted Certificate Authority. A wildcard certificate for *.mas.[yourdomain] can simplify certificate management significantly.
For development/testing: Self-signed certificates work fine, but expect browser warnings. Your users will need to accept security exceptions, which is fine for a dev environment but definitely not for production.
Hardware Requirements: What’s Under the Hood
For a Single Node OpenShift (SNO) installation suitable for development or testing, you’ll need hardware that meets or exceeds these specifications:
| Component | Minimum | Recommended |
| Processor | 16-core CPU | 16+ core CPU |
| Memory (RAM) | 64 GB | 200+ GB |
| Primary Disk Space | 300 GB SSD | 1 TB SSD/NVMe |
| Storage Dedicated | 500 GB SSD | 1 TB SSD/NVMe |
| Network | 1 Gbps | 10 Gbps |
Note: These specifications are for a non-production SNO environment. Production deployments typically require a multi-node cluster with significantly more resources. We’ll cover production sizing in a future article.
Storage Considerations:
- Use separate fast SSD/NVMe storage for database and application layers
- Dedicate storage for logs, backups, and indexing
- RAID 10 or NVMe-based storage recommended for high performance
The Bastion Host: Your Command Center
A bastion host is a separate server used to manage your OpenShift cluster(s). Think of it as mission control: you’ll use this machine to issue commands against your cluster without cluttering the cluster itself with management tools.
Bastion Host Requirements:
| Component | Specification |
| Processor | 4-core CPU |
| Memory (RAM) | 8 GB |
| Primary Disk Space | 1 GB Drive |
| Network | 1 Gbps (10 Gbps recommended) |
The bastion host will run tools like the OpenShift CLI (oc), the MAS CLI, Docker, and other utilities needed for cluster management. You’ll SSH into this server whenever you need to run installation commands or manage the cluster.
Network Ports: Opening the Right Doors
Your firewall will need to allow traffic on specific ports for the cluster to function properly:
| Port | Purpose |
| 80 | HTTP traffic (redirects to HTTPS) |
| 443 | HTTPS traffic (web console, application access) |
| 6443 | Kubernetes API server |
Work with your network security team to ensure these ports are open between your bastion host, the OpenShift node, and any clients that need to access the cluster.
Database Considerations: Where Your Data Lives
MAS 9 supports SQL Server as an external database (among other options). While the database isn’t required for Day 1 of installation, you’ll need it configured before starting the MAS 9 application installation.
If using SQL Server:
- Ensure the Maximo user on SQL Server is the db_owner of the Maximo database
- Test login credentials using SQL Server Management Studio
- Verify connectivity from your Linux environment to SQL Server on port 1433
Connectivity test from Linux: Use nc -zv [sqlserver-hostname] 1433 to verify you can reach the SQL Server port from your cluster node.
Folder Structure: Getting Organized
Before installation, set up a logical folder structure on your bastion host. Here’s a recommended layout:
| Folder | Purpose |
| /opt/ibm | Root folder for IBM products |
| /opt/ibm/mas9 | MAS install packages, YAMLs, scripts |
| /opt/ibm/mas9/oc/ | OpenShift CLI |
| /opt/ibm/mas9/mas-cli/ | MAS command line tools |
| /var/mas/ | Optional: local temporary files for logging or backups |
| /usr/local/bin/ | Tools such as oc, kubectl, mas binaries |
Create a masconfig folder within your installation directory to store your pull-secret and license.dat files. Keep these files secure because they contain sensitive credentials and licensing information.
What to Expect: The Road Ahead
With all prerequisites gathered, here’s a preview of what the installation process looks like:
- Create an ISO Image: Using Red Hat’s Assisted Installer, you’ll generate a bootable ISO configured for your environment. This ISO will bootstrap your OpenShift node.
- Boot and Configure OpenShift: The server boots from the ISO, connects back to Red Hat’s console, and completes the OpenShift installation. This process typically takes 30-40 minutes.
- Install MAS Core: Using the MAS CLI from your bastion host, you’ll install the MAS Core components, which provide the foundation for all MAS applications.
- Configure and Deploy Applications: Finally, you’ll install Maximo Manage and any other MAS applications you need, configure database connections, and set up user authentication.
We’ll cover each of these steps in detail in upcoming articles. For now, focus on gathering your prerequisites and coordinating with your IT and network teams.
Pre-Installation Checklist: Are You Ready?
Before proceeding to installation, verify you have:
- IBM Entitlement Key copied and stored securely
- IBM license.dat file downloaded
- Red Hat OpenShift pull secret obtained
- Cluster name and base domain decided
- DNS entries requested from your network team
- SSL certificate requirements identified (self-signed or CA-trusted)
- Hardware provisioned meeting minimum requirements
- Bastion host set up with network access to the cluster
- Required ports opened in firewall
- Database server ready (if using external database)
Conclusion: Ready, Set… Almost Go
Gathering prerequisites might not be the most exciting phase of an installation, but it’s arguably the most important. Taking the time to collect everything upfront will save you hours of troubleshooting later. Trust us, there’s nothing quite like getting 80% through an installation only to discover you’re missing a critical license file or DNS entry.
In our next article, we’ll dive into the actual installation process: creating the OpenShift ISO, booting the cluster, and getting Red Hat OpenShift up and running. We’ll include the actual commands and configurations you need, so you can follow along step-by-step.
Until then, gather your ingredients, coordinate with your IT team, and maybe grab that stress ball we mentioned in the first article. You’re about to need it. Just kidding, it’ll mostly be fine. Probably.
Resources to bookmark:
- IBM Container Library: https://myibm.ibm.com/products-services/containerlibrary
- IBM License Key Center: https://licensing.flexnetoperations.com
- Red Hat Console: https://console.redhat.com
- IBM MAS Documentation: https://www.ibm.com/docs/en/mas
Stay tuned for Part 3: Installing Red Hat OpenShift!
