Good question. Assuming your configuration is relatively standard for the messaging engine, you should be fine. What I mean by standard is you're using files on a file share (IE \\servername\jms\myserver) that all JVMs can access or using a database. You're not using local file paths (IE D:\JMS) as that causes fragmented JMS stores where each VM has only a portion of the messages.
How you configure the JMS queues also matters. We recommend configuring everything at a Cell level scope (not a cluster level). When configured at a cell level, that means that every JVM in any cluster can access all the JMS queues (IE UI1 can access CQIN & SQOUT, not just SQOUT). This would mean that while the messaging engine is running on the UI cluster, your other JVMs (including Anywhere) can write messages to the SQOUT which would then get consumed. It's pretty easy to test this inside of Maximo, as testing the queues in the External System application (in the Add/Modify Queues dialog using the View Queue Data action) from the JVM you're interested (such as UI or Anywhere) will throw an error if it can't access the queue. Assuming the Anywhere JVM can access the SQOUT queue, you'll be fine without any other changes.
------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------
Original Message:
Sent: Thu October 22, 2020 12:14 AM
From: Prashant Bavane
Subject: Maximo Anywhere separate cluster
Hi Steve ,
I we separate out AnyWhere cluster from UI , do we need to have this cluster also added in service integration bus for any outbound events to trigger integrations and also need to have SEQOUT instances running on AnyWhere
------------------------------
Prashant Bavane
Original Message:
Sent: Mon May 18, 2020 09:23 AM
From: Steven Shull
Subject: Maximo Anywhere separate cluster
As Pam mentions in her post, Maximo is pretty flexible and allows you to isolate specific workloads (including Anywhere) if you need it. But what is required is very subjective and dependent on the organization, to make it difficult to provide a hard and fast rule as to whether or not you should isolate functionality. As an example, if you have 1 million locations or 100 locations is a large difference on the load that it will put on the Maximo system when you retrieve lookup data. Your users may primarily work offline, so they may put a heavy load early in the morning and evening as they download the work list & synchronize back to Maximo but then during the day have a negligible impact on the Maximo system because transactions aren't being sent while they're disconnected. And if you have 500 active Anywhere users at a time, that makes it much easier to justify dedicated JVMs than if you have less than 50 users.
Based on what we've seen with our customer base who typically have connectivity, we've chosen to scale the UI cluster over creating dedicated JVMs for the purpose of synchronizing Anywhere data and transactions. But it is something you should evaluate based on the load you expect Anywhere to put on your system.
------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
Original Message:
Sent: Fri May 15, 2020 03:25 AM
From: santhosh Kumar
Subject: Maximo Anywhere separate cluster
Hi Team,
Do we require separate JVM for Maximo anywhere 7.6.4 ?
Thanks & Regards,
Santhosh
------------------------------
santhosh Kumar
------------------------------
#MaximoAnywhere
#AssetandFacilitiesManagement
#Maximo