Planning

When you plan your IBM® IoT MessageSight solution, you must make a number of decisions to ensure your solution works effectively.

Installation planning
Before you install IBM IoT MessageSight, you must consider the hardware and software requirements.
Messaging patterns
The messaging patterns identify common message flows that are used in messaging solutions. There are five messaging patterns: fan out broadcast, fan in per device notification, fan out per device notification, fan out per device request-reply, and fan in per device request-reply.
Messaging planning
Key points to consider when you plan the messaging aspects of your IBM IoT MessageSight solution.
Clustering considerations
Key points to consider if you are planning to use clustering in your IBM IoT MessageSight solution.
Capacity planning
IBM IoT MessageSight can store messages to assure delivery to clients and devices that might not be connected. The amount of storage is limited, and if it fills, the server rejects new messages.
Performance planning
To optimize performance, review the guidelines in this section and plan your solution accordingly.
High availability planning
High availability (HA) enables messaging services to continue over the outage of a server. In an HA environment, two servers are connected and configured as an HA pair so that, if one of the servers (the primary) fails due to a planned or unplanned outage, the other server (the standby) can take over as the primary and messages can continue to be processed. When the original primary becomes available again after the outage, it acts as the standby in the HA pair.
Connecting to an existing infrastructure
You can connect IBM IoT MessageSight to IBM MQ by using MQ Connectivity. You can connect IBM IoT MessageSight to WebSphere® Application Server by using the IBM IoT MessageSight resource adapter.

Parent topic: Product overview