<div style="display:inline;"> <img height="1" width="1" style="border-style:none;" alt="" src="//googleads.g.doubleclick.net/pagead/viewthroughconversion/1066880148/?value=0&amp;label=4oTQCMyJzwQQlJnd_AM&amp;guid=ON&amp;script=0">

Interloc Solutions Blog

Interested in anything & everything Maximo? Subscribe to the Interloc Solutions 100% Maximo blog to stay up-to-date on the latest IBM Maximo news.

Julio Perera

Blog Feature

By: Julio Perera
August 21st, 2024

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.

Blog Feature

By: Julio Perera
June 24th, 2024

This is a continuation of our series of blogs about deployment of MAS. In this case, we are going to describe how to configure Automatic Certificate Management via the JetStack Cert Manager or the IBM Cert Manager Operators. Installing either is not part of this Blog Entry and the IBM Cert Manager should come automatically with the MAS Core as a dependency; however, we prefer to use the JetStack Cert Manager as it supports wider use cases than the IBM Cert Manager (such as split horizon DNS setups). We should be also aware of that IBM has officially supported the IBM Cert Manager and made statements that they will support other Cert Managers (RedHat’s or JetStack). In our experience, the JetStack Cert Manager works well with the MAS Core (and applications) up to the latest version at the time of writing 8.11.10.

Blog Feature

By: Julio Perera
June 7th, 2024

This is a continuation of our series of blogs about deployment of MAS. In this case, we are going to describe how to configure Automatic Certificate Management via the JetStack Cert Manager or the IBM Cert Manager Operators. Installing either is not part of this Blog Entry and the IBM Cert Manager should come automatically with the MAS Core as a dependency; however, we prefer to use the JetStack Cert Manager as it supports wider use cases than the IBM Cert Manager (such as split horizon DNS setups). We should be also aware of that IBM has officially supported the IBM Cert Manager and made statements that they will support other Cert Managers (RedHat’s or JetStack). In our experience, the JetStack Cert Manager works well with the MAS Core (and applications) up to the latest version at the time of writing 8.11.10.

Blog Feature

By: Julio Perera
April 24th, 2024

This is a continuation of our series of blogs about deployment of MAS on Bare Metal or on-premise scenarios. In this case, we are going to describe how to configure the Image Registry in the RedHat OpenShift Cluster, so it is backed up by persistent Shared Storage. Notice that Cloud Deployments will typically have the Cluster Image Registry already configured using one of the Storage options that is provided by the Cloud Provider. However, for Bare Metal scenarios, including SNO, such provisioning is not configured by default.

Blog Feature

By: Julio Perera
February 27th, 2024

This is the second part of the two-part blog where we are showing the sequence of specific steps, we followed to install a Local Storage Provider to be used for SNO deployments over Bare Metal. To see important considerations and general discussion, feel free to see previous blog entry.

Blog Feature

By: Julio Perera
February 6th, 2024

At Interloc, many of our Maximo consultants are continuously improving upon their MAS functional and technical skills. For those resources focusing on MAS installations, we use the Single Node OpenShift deployment option to create our own, individual environments to replicate issues and probable solutions. Considering these SNO instances are predominantly deployed either in Bare Metal hosts or in Virtualized platforms (like VMware ESXi as VMs) then a solution to have a locally provisioned Storage Class is needed in order to have all MAS and dependencies use it for Shared Storage.