(r2) MQTTMessageBrokerDeploymentOptions < Deployment

Engineering Lifecycle Management Wiki - Deployment

Community information and contribution guidelines

~~EditAttach~~Printable

TWiki > Deployment Web > DeploymentPlanningAndDesign > MQTTMessageBrokerDeploymentOptions

Revision 2 - 2020-07-02 - 19:29:42 - TimFeeney

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! IBM !MessageSight deployment options with IBM Engineering Lifecycle Management solution <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.TimFeeney<br>
Build basis: 6.0.6.x, 7.0
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

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 
      * see [[https://www.ibm.com/support/knowledgecenter/SSYMRC_7.0.0/com.ibm.jazz.install.doc/topics/c_ccm_cluster.html][Change and Configuration Management clustered environment]] and [[https://www.ibm.com/support/knowledgecenter/SSYMRC_7.0.0/com.ibm.jazz.install.doc/topics/c_qm_cluster.html][Quality Management clustered environment]]
   1. Deep skew detection in global configurations of contributions from EWM SCM or RMM 
      * see [[https://www.ibm.com/support/knowledgecenter/SSYMRC_7.0.0/com.ibm.rational.gcapp.doc/topics/t_detect_deepskew.html][Finding multiple different configurations of the same component in EWM SCM and RMM contributions (Detecting deep component skew)]]
   1. Building global configurations with contributions from other GCM servers 
      * see [[https://www.ibm.com/support/knowledgecenter/SSYMRC_7.0.0/com.ibm.rational.gcapp.doc/topics/t_mult_inst.html][Enabling GCM servers to contribute configurations to 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 [[https://www.ibm.com/support/knowledgecenter/en/SSWMAJ_2.0.0/com.ibm.ism.doc/QuickStartGuide/qs00030_.html][IBM !MessageSight - Provisioning your operating system]]).

IBM recommends that !MessageSight be clustered for both scalability and high availability purposes.  See [[https://www.ibm.com/support/knowledgecenter/en/SSWMAJ_2.0.0/com.ibm.ism.doc/Overview/ov00150_.html][Clustering in IBM IoT !MessageSight]] and [[https://www.ibm.com/support/knowledgecenter/SSWMAJ_2.0.0/com.ibm.ism.doc/Planning/clusteringconsiderations.html][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 [[https://jazz.net/wiki/bin/view/Deployment/Common605Beans][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.

<sticky></div></sticky>

Copyright © by IBM and non-IBM 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.