Planning the architecture

The architecture of IBM® IoT for Energy and Utilities depends on the applications to be used.

Each node must be installed on a separate computer or on a separate virtual machine image from other nodes.

Important: These node suggestions are for example only. You must check your own requirements for data base size and node requirements.

Asset Performance Management and Asset 360 for Wind

For Asset Performance Management and Asset 360 for Wind you required a three node configuration: App node, SPSS node and DB node. If Cognos BI is also required, then a four node configuration is required that includes a BI node for Cognos and the Cognos BI DB2 database.

Figure 1. Nodes used for Asset Performance Management and Asset 360 for Wind

shows a three or four node configuration including an optional BI node

Connectivity Model with Hortonworks Data Platform (HDP)

For the Connectivity Model application the App node contains the IHS server, LDAP server and the Liberty server. The seven node cluster contains the Hortonworks Data Platform.

Figure 2. Nodes used for Connectivity Model

shows a 1 + 7 configuration for the app node and the HDP nodes

The services that are installed on each node are:

Ambari node: KDC server for Kerberos authentication, Ambari server,; HTTP server for the HDP repository for installation

Master01 node

HDFS, HBase, MapReduce2, App Timeline Server, Resource Manager, Hive

Spark History Server, WebHCat Server, Zookeeper, Spark Thrift Server,

Kafa, Knox, Ambari Metrics, HST Agent, Metrics Monitor,

HDP clients, ambari-agent, kdc-client, ldap-client

Master02 Node

HDFS, HBase, HIVE, Zookeeper, Resource Manager, Spark Thrift Server

Kafa, Knox, HST Agent, Metrics Monitor,

HDP Clients, ambari-agent, kdc-client, ldap-client

Slave01 Node

HDFS DataNode, HDFS JournalNode, HBase Region Server, Zookeeper, Node Manager,

ambari-agent, kdc-client, ldap-client, SmartSence, Metrics Monitor, HST Server,

Slave02/Slave03 Node

HDFS DataNode, HBase RegionServer, NodeManager,

HDP clients, ambari-agent, kdc-client, ldap-client, Metrics Monitor, HST agent

Notebook Node

Zeppelin Notebook, HDP clients, ambari-agent, kdc-client, ldap-client, Metrics Monitor, HST agent

Note: Kafka, Knox, Metrics, HST, SmartSence services are not used by Connectivity Model

Asset Performance Management or Asset 360 for Wind and Connectivity Model with Hortonworks Data Platform

When the Connectivity Model with HDP and either Asset Performance Management or Asset 360 for Wind are required, then you require the configuration 4 + 7. The App node, SPSS node and DB node and the optional BI node are required for the Asset Performance Management application and the App node and the seven node cluster required for HDP is required for the Connectivity Model. The App node is shared between the applications.

Connectivity Model with Hortonworks Data Platform (HDP) in a one plus two topology

The one + two topology is used for developmental purposes. For the Connectivity Model application the roles that are installed on each node are:

App node: Liberty server, LDAP server, IHS server, installer
bigdataNodeOne: cm_backend_contaier, notebook_container, master01_container, slave01_container, cm_blueprint_container, registry
bigdataNodeTwo: repo_container, kdc_container, ambari_container, master02_container, slave02_container

For more information about Ambari, refer to https://ambari.apache.org

For more information about Hortonworks Data Platform (HDP), refer to https://hortonworks.com/products/data-platforms/hdp/