If you’re using the Maximo REST API, then that will still work the same way in Maximo Application Suite.

By default, we install the MAS standard (WebSphere) JMS queues like CQIN, CQOUT, SEQIN, and SEQOUT so those will be running like they do for you in prior Maximo versions. However, file-based integrations where you need to share a file/UNC location with other systems, either for Maximo to write out files or read in files placed there, are problematic in MAS. We have a proven solution that is a fairly close replacement for those integrations (even more so than using S3) that we can share with you.

One major benefit of the MaxStack dedicated server and private cloud architecture is it makes a true “Lift & Shift” from on-premises to cloud possible, without having to redesign and recreate your interfaces. This is because Maximo can still reach your external integrated systems and vice-versa. This is not possible in other MAS SaaS offerings using shared application clusters.