IBM | Interloc Solutions | Maximo Implementation | IBM Maximo | Resources | Performance | Interloc | IBM Maximo 7.6 | Maximo Application Suite | Interloc Commitment | Operational Efficiency | Maximo Mapping Solutions | IBM MAS | OpenShift | Maximo Applications Suite 9.1 | RedHat
Abstract: We are continuing our series of Blog Entries to cover some MAS deployment scenarios either left out or not appropriately covered on the IBM Ansible scripts. We are going to also discuss considerations and tips and hints around these deployments. This time we are configuring automated DB2 backups against a pre-existing Storage Class and discussing limitations and considerations as well.
IBM | Implementation | Integration | IBM Maximo | Maximo Usability | Performance | asset management | asset management solution | IBM Mobile Informer | IBM Maximo Resources | maximo implementations | IBM Maximo Web Service Logging | Maximo Hosting | Maximo SaaS | Smart Monitoring | Infrastructure Automation | IBM MAS | OpenShift | RedHat
Abstract: We are continuing our series of Blog Entries to cover some MAS deployment scenarios either left out or not appropriately covered on the IBM Ansible scripts. We are going to also discuss considerations and tips and hints around these deployments. This time we are configuring automated DB2 backups against a pre-existing Storage Class and discussing limitations and considerations as well.
MongoDB Backup | Automated Backups | IBM MAS | OpenShift | Ansible Scripts | MAS Deployment | OpenShift Cron Jobs
Abstract: We are continuing our series of Blog Entries to cover some MAS deployment scenarios either left out or not appropriately covered on the IBM Ansible scripts. We are going to also discuss considerations and tips and hints around these deployments. This time we are configuring automated MongoDB backups against a pre-existing Storage Class and discuss limitations and considerations as well.
Interloc Solutions | Kubernetes | S3 Storage | Object Storage | DaemonSet | Cloud Native | CSI Driver | Kubernetes Storage | YAML Configuration | CSI Provisioner | Kubernetes CSI | Maximo Integration | CSI Node Plugin | Kubernetes RBAC | Infrastructure Automation
Abstract: We are continuing our series of Blog Entries to cover some MAS deployment scenarios either left out or not appropriately covered on the IBM Ansible scripts. We are going to also discuss considerations and tips and hints around these deployments. This time we are configuring and creating a Storage Class for the RedHat OpenShift Cluster so it can be used in some scenarios.
While the IBM Ansible scripting covers the installation of the AI broker, at the time of writing, there are several dependencies and caveats that are not installed by default and the documentation is insufficient to completely do a successful installation.
This is a continuation of our series of blogs about deployment of MAS. In this case, we are going to describe how to configure Kafka Topics as Queues in MAS Manage. In general, the configurations are described in the following URL: https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=applications-integration-apache-kafka. There is an assumption that the Kafka Server has been already installed and it is working in OpenShift. Currently the installation supports both AMQ Streams or Strimzi operators, although we prefer Strimzi as it doesn’t require a license.
