Universal Messaging 10.11 | Release Notes | Overview | License Types and Feature Sets
 
License Types and Feature Sets
To use Universal Messaging in a production environment, you require one of the following licence types:
NUMWF/NUMTF
Universal Messaging Fully Featured / TC Universal Messaging Fully Featured.
NUMWI
Universal Messaging for Integration Active/Passive.
NUMWS
Universal Messaging for Integration Active/Active.
Note:
You can only use this license type if you also have the NUMWI license type.
The following table shows the feature sets available with each of the license types:
Feature Name
Description
NUMWF / NUMTF
NUMWI
NUMWS
Max Resources
Can create channels, queues, data groups and data streams
Unlimited / Specified
Unlimited
Mixed Channels
Can create channels that contain messages that are persistent or reliable
x
x
Reliable Channels
Can create channels that contain messages that are reliable (current event ID persisted to disk)
x
x
Persistent Channels
Can create channels where all events are stored on disk
x
x
Queues
Messaging paradigm where only one consumer can read a message from a queue. If more than one consumer is subscribed to a queue then the messages are distributed in a round-robin fashion.
x
x
JMS Clients
Clients can use the JMS API
x
x
Java Clients
Clients can use the native Java API
x
x
Enterprise Clients for C++ (deprecated), C#
Clients can use additional native APIs (C++, C#)
x
x
Zones
Organize servers within one namespace
x
x
Joins
Joins can be used to forward messages between servers or clusters
x
x
Publish Keys
Uniquely identify messages on a channel, used for merging or replacing
x
x
Snoop
Peek at messages on a queue or topic
x
x
Messaging Priority
Server can reorder messages based on priority
x
x
Horizontal Scaling
Clients can seamlessly publish/consume events to/from multiple independent realms and clusters using a single connection
x
x
Active/Active Clustering
Clusters are formed of multiple active servers for high availability
x
x
Web Clients
Web browser-based clients
x
Mobile Clients
Mobile-based clients (Apple iOS, Google Android)
x
Plugins
Server can expose additional functionality (e.g. files, REST) over HTTP interfaces
x
Data groups
Group of consumers to which publishers can send messages, as an alternative to using channels (JMS topics). The messaging is focused on allowing management and alteration of client subscriptions.
x
Data streams
Consumers which are members of data groups
x
HTTP Support
Connect over HTTP interfaces
x
AMQP
Use the AMQP protocol for messaging with queueing
x
MQTT
Use the MQTT lightweight protocol for embedded devices
x
Shared Memory
Low latency interface communication on the same machine
x
Multicast
Reliable multicast over UDP for efficient routing of messages
x
Note:
Universal Messaging ships with a trial license, which allows the full-feature server to run for a maximum of 90 days from first run. During the installation procedure, you can either choose to use the trial license, or you can specify the name of the production license file. If you start off with the trial license and later decide to move to a production license, follow the instructions in the section License Management of the Installation Guide.