r2 - 2020-07-02 - 19:29:42 - TimFeeneyYou are here: TWiki >  Deployment Web > DeploymentPlanningAndDesign > MessageSightDeploymentOptions

IBM MessageSight deployment options with IBM Engineering Lifecycle Management solution todo.png

Authors: TimFeeney
Build basis: 6.0.6.x, 7.0

In IBM Engineering Lifecycle Management (ELM) 7.0, there are three primary reasons why IBM MessageSight, an MQTT message broker, is needed.

  1. EWM or ETM clustering for user scalability
  2. Deep skew detection in global configurations of contributions from EWM SCM or RMM
  3. Building global configurations with contributions from other GCM servers

It is quite possible and highly likely that a client deployment will need MessageSight for one or more of the reasons stated.  Note MessageSight only runs on CentOS and RHEL operating systems (see IBM MessageSight - Provisioning your operating system).

IBM recommends that MessageSight be clustered for both scalability and high availability purposes.  See Clustering in IBM IoT MessageSight and IBM MessageSight - Clustering considerations. ELM provides several JMX MBeans that reporting on aspects of the MQTT MessageBroker, i.e. MessageSight, used by ELM. In particular, see the MQTT service metrics MBean in Common Managed Beans.

IBM requires that a MessageSight cluster be shared between ELM instances that are contributing to a common global configuration.

IBM recommends that ELM instances requiring MessageSight for clustering or deep skew detection have their own independent cluster (vs shared with other ELM instances).

IBM recommends that production, test, development, etc. environments have their own independent MessageSight clusters.

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.