IBM Maximo Developer Area - SDKs and Samples for Maximo Development

 Reference Link : 

 https://github.com/ibm-maximo-dev

 

Backing & Restore Maximo Manage namespace with a script

1)  Use the manage-backup-restore.sh script to back up the Maximo Manage namespace.

Run the following command to back up the Maximo Manage namespace.

• manage-backup- restore.sh -w <mas-workspace-id> -i <MAS_INSTANCE_ID> -f <BACKUP_FOLDER> -m backup 

 

-w, --mas-workspace-id

The Maximo Manage workspace ID that you are backing up.

-i, --mas-instance-id

The Maximo Application Suite instance ID that you are backing up.

-f, --backup-folder

The folder where the backup artifacts are written to.

-m, --mode

Indicates whether to backup or restore. Use the value restore.

• manage-backup-restore.sh -w <mas-workspace-id> -i dev -f ./ -m backup

 Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=namespace-backing-up-maximo-manage-script&mhsrc=ibmsearch_a&mhq=MAS%20backup%20and%20restore

2) Restore your backed up Maximo Manage namespace manually or by using the manage-backup-restore.sh script.

To restore manually, use the oc cli command to restore the resources that you backed up.

The command applies the configuration that is specified in the file that is provided. Run the command for each *.yaml file that you created when you did the backup.

• oc apply -f <filename>

To restore the Maximo Manage namespace by using the manage-backup-restore.sh script, run the following command.

• manage-backup-restore.sh -w <mas-workspace-id> -i <MAS_INSTANCE_ID> -f <BACKUP_FOLDER> -m restore
• manage-backup-restore.sh -w <mas-workspace-id> -i dev -f ./ -m restore 

The script runs the oc apply command on all the *.yaml files in a specified folder, which restores the files.

Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=mm-namespace&mhsrc=ibmsearch_a&mhq=MAS%20backup%20and%20restore

IBM Maximo Application Suite installation with Ansible collection

 To automate some of the manual steps that are involved with installing Maximo® Application Suite and its components, use the Ansible collection roles that match your installation path or use case.

The IBM® Maximo Application Suite development team maintains a public Ansible collection that automates the installation and configuration of Maximo Application Suite and its dependencies. The Maximo Application Suite DevOps Ansible collection includes a number of automated tasks, referred to as roles and playbooks. These automated tasks can be used to streamline processes from having a simple Red Hat® OpenShift® cluster, to having Maximo Application Suite including multiple applications and its required dependencies.

Please find the below link for more information : 

https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=installing-ansible-collection

What's new in Maximo Application Suite 8.11

 Installation 

•  Support for MongoDB 5.0 and 6.0

Configuration

• Manage trusted certificate authorities
• Customizing the workload
• Horizontal and vertical pod scaling
• Pod scheduling with affinity and anti-affinity
• Pod scheduling with tolerations

Suite administration

• Configuring multiple login options
• Login notification
• Activate and deactivate users
• Enhancement to delete users
• Support for roll back and version lock
• API keys for user management
• Audit log generation to support the Federal Information Security Management Act (FISMA)
• Configuring passwords settings page moved to local authentication

Maximo Application Suite enhancements on Microsoft Azure

• Support for new databases  :Starting in Maximo Application Suite 8.11, configure databases such as Microsoft SQL Server or Oracle Database for using IBM Maximo Manage.
•  These databases can be hosted on private subnet of another VPC.

Maximo Application Suite enhancements on Amazon Web Services

Support for new databases :Starting in Maximo Application Suite 8.11, configure databases such as Microsoft SQL Server or Oracle Database for using IBM Maximo Manage. These databases can be hosted on private subnet of another VPC.

VPC peering is used to establish connection between the VPC of Amazon Web Services stack to the VPC of a database to establish database connection when the stack is deployed.

Support for selecting EBS volume type

Starting in Maximo Application Suite, support for selecting either gp3 or io1 as EBS volume type for worker nodes.

• FIPS and FISMA support for Maximo Application Suite on Amazon Web Services Marketplace in US GovCloud regions
• A Federal Information Processing Standard (FIPS) and Federal Information Security Management Act (FISMA) supported Maximo Application Suite can now be installed in the Amazon Web Services US GovCloud regions.
• The BYOL option is available for installing Maximo Application Suite in private hosted zone for existing Red Hat OpenShift cluster and New Red Hat OpenShift cluster by using the User Provisioned Infrastructure (UPI).

User assistance improvements

• Upgrading from IBM Maximo Asset Management to IBM Maximo Manage

Applications, industry solutions, accelerators, and add-ons

IBM Maximo IT

IBM Maximo IT is now available in Maximo Application Suite. Maximo IT provides a single point of user support and enterprise service management of information technology (IT) and operational technology (OT) assets and processes.

Reliability Strategies

Reliability Strategies is now available in Maximo Application Suite. 

By using Reliability Strategies, you can access a library of maintenance strategies that are based on reliability-centered maintenance and include both failure details and mitigation activities for each failure.  The library was developed by industry and domain experts and contains hundreds of assets and tens of thousands of possible failures across all known operating contexts.

New accelerators in the Maximo Application Suite catalog

Accelerators are solutions that are provided by IBM and IBM partners to complement or extend Maximo Application Suite capabilities. 

IBM Maximo Models for Electrical Distribution

IBM Maximo Models for Electrical Distribution provides model templates to enhance the reliability of energy and utility assets to anticipate downtime, degradation, and failures. 

This accelerator includes prebuilt notebooks and configuration files for several transmission and distribution asset classes, incorporating features available in IBM Maximo Health and IBM Maximo Predict.

Maximo Manage has new function to reduce system downtime when you do an update

After you upgrade to IBM Maximo Application Suite operator version 8.11, configure a database state to reduce Maximo Manage system downtime as you upgrade to Maximo Manage 8.7. and subsequent Maximo Manage upgrades.

Removal of Maximo Health and Predict - Utilities and Parts Identifier

Starting in Maximo Application Suite 8.11, the following industry solution and add-on are no longer available:

• Maximo Health and Predict - Utilities
• Parts Identifier

For More information please follow the below link.

https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=new-in-811

Prerequisites for On-premises MAS Installation

1) Cluster Information:

Node details The cluster consists of 3 master nodes, 5 worker nodes and 3 Infra/storage nodes. There is an installer machine running RHEL which hosts all the installation artifacts and which load balances the request to master and infra nodes.

2) DNS configurations

3) Load Balancers details

Load Balancer	Port	Server Pool	Type
API Load Balancer	6443, 22623	Boot, master0, master1, master2 Boot, master0, master1, master2	Layer 4 load balancing only. This can be referred to as Raw TCP, SSL Passthrough, or SSL Bridge mode. If you use SSL Bridge mode, you must enable Server Name Indication (SNI) for the API routes. A stateless load balancing algorithm. The options vary based on the load balancer implementation.
Application Ingress	80	infra0, infra1, infra2	Layer 4 load balancing only. This can be referred to as Raw TCP, SSL Passthrough, or SSL Bridge mode. If you use SSL Bridge
Load Balancer	443	infra0, infra1, infra2	mode, you must enable Server Name Indication (SNI) for the Ingress routes. A connection-based or session-based persistence is recommended, based on the options available and types of applications that will be hosted on the platform.

Prerequisites

 System requirement

1. All Linux systems (VMs) must be registered to the subscription manager.

2. Ensure that the package manager is configured to allow for package updates across all nodes. 3. The Installation will need the Root access privilege.

 4. Memory and CPU requirement should meet the minimum requirement as given the table under cluster node details

 

 Network requirement

 Network topology diagrams can be unique for every cluster based on the requirements. We can deploy the cluster with different VLANs or in the same VLANs.

• Ensure a block of IP addresses from which pod IP addresses are allocated. This block must not overlap with existing physical networks. These IP addresses are used for the pod networks.

 • Similarly, a block of IP address pool is reserved to use for service IP addresses and must not overlap with existing physical networks.

• Instances (systems) on the network should be able to see each other as being neighbours. Each machine must be able to resolve the hostnames of all other machines in the cluster. Note: Changes to the network post deployment of OCP cluster aren't supported by Red Hat.

DNS requirement In OpenShift Container Platform deployments, DNS name resolution is required for the following components:

 • The Kubernetes API

• The OpenShift Container Platform application wildcard

 • The bootstrap, control plane, and compute machines

Reverse DNS resolution is also required for the Kubernetes API, the bootstrap machine, the control plane machines, and the compute machines.

DNS A/AAAA or CNAME records are used for name resolution and PTR records are used for reverse name resolution. The reverse records are important because Red Hat Enterprise Linux CoreOS (RHCOS) uses the reverse records to set the hostnames for all the nodes, unless the hostnames are provided by DHCP. Additionally, the reverse records are used to generate the certificate signing requests (CSR) that OpenShift Container Platform needs to operate.

 

Port requirement List of required ports that must be available for installation and configuration of an OpenShift cluster. You need to open the ports before you start installing OpenShift.

 

Below link has the port details that are needed to be open:

 https://docs.openshift.com/container-platform/4.10/installing/installing_vsphere/installing-restricted[1]networks-vsphere.html#installation-network-connectivity-user-infra_installing-restricted-networks[1]vsphere

 

Other Firewall requirements:

 Ports should be open from all cluster nodes to the NTP servers

 In connected OpenShift Container Platform environments, all nodes are required to have internet access to pull images for platform containers and provide telemetry data to Red Hat.

 Ensure that ports are open between all the proxy and GLB for all OCP cluster nodes

Installing Maximo Mobile 8.1 for EAM

Follow the below step to install Maximo Mobile.

 

1) Login into IBM Passport advantage website 

2) Download the G016DML part number and download the zip (maximomobile.zip )

 System Requirements: 

 

·       Maximo Asset Management version 7.6.1.2 or later with IBM WebSphere® Application Server or Oracle WebLogic Server. 

·       Interim fix IF006 or later for Maximo Asset Management version 7.6.1.2.

·       Interim fix IF003 or later for Maximo Spatial Asset Management version 7.6.1. 

·       Mobile devices that have Android version 10 or 11 or iOS version 14.3 or later mobile operating systems installed.

Follow the steps defined in the readme file.

Maximo Application Suite 8.x Links

https://www.ibm.com/support/pages/ibm-maximo-application-suite-system-requirements

https://github.com/evilADevil/mas-local/Perceval & Cloud Webinar #3

https://epwt-www.mybluemix.net/software/support/trial/cst/programwebsite.wss?siteId=1790&h=null&p=null

https://github.com/cloud-native-toolkit/operator-masauto

DM - RFC Link

https://smartdesk.dm.gov.ae/smartit/app/#/change/IDGAABS5GMS9LASCB7FNSBBES2NQ3H

MAS_ CLI

https://ibm-mas.github.io/cli/catalogs/v8-231004-amd64/