[WEBINAR] Bulletproof: How Today's Business Leaders Stay on Top

Enterprise Messaging System (EMS)

Definition - What does Enterprise Messaging System (EMS) mean?

Enterprise messaging system (EMS) is a messaging system allowing software applications and systems to communicate semantically. The semantics can be applied by sending precise messages to and fro throughout the enterprise. The messages are asynchronous data (messages not sent or processed in real time, meaning not like a chat room or telephone conversation) sent by one application or system to another application or system and stored in the queue of the receiving program until processed. The system is not dependent on a particular operating system or programming language.

Techopedia explains Enterprise Messaging System (EMS)

EMS may describe email, fax or instant messages where there is human-to-human interface. However, EMS messages are asynchronous and consist of report and event data designed to be received by the enterprise’s applications and not by humans. The message coordinates enterprise systems and records the progress towards enterprise project goals and objectives.

Enterprise messaging system processes are facilitated by XML messaging, SOAP and Web services.

An enterprise messaging system should be able to meet certain criteria:

  1. Policy: There must be a centralized policy of messages allowing different classes or responsibilities of users to access appropriate messages.
  2. Security: Messages traveling over public facilities must be encrypted and authenticated or digitally signed.
  3. Routing: Messages must be efficiently routed; and intermediate nodes are used if the body is encrypted.
  4. Subscription Systems: Systems should have the ability to subscribe to all messages matching a specific pattern and differing content messages should have different type of routing, such as meeting different security or priority policies.
  5. Metadata: Body of message must be unambiguous and use metadata registries for each element of data.

EMS messages are usually in two sections, message header and message body. The message header design contains data necessary to route it correctly from one node to another. It is analogous to the information on the outside of a letter, such as name, address, zip code, etc. The message body semantics contains the precise definition of the data elements. These are aided by a precise data dictionary documenting metadata, which is data about one or several aspect of the data such as means of creation, purpose along with time and date of creation.

Java Message Service is an example of an application programming interface (API) implementing EMS.

Share this:

Connect with us

Email Newsletter

Join thousands of others with our weekly newsletter

The 4th Era of IT Infrastructure: Superconverged Systems
The 4th Era of IT Infrastructure: Superconverged Systems:
Learn the benefits and limitations of the 3 generations of IT infrastructure – siloed, converged and hyperconverged – and discover how the 4th...
Approaches and Benefits of Network Virtualization
Approaches and Benefits of Network Virtualization:
Businesses today aspire to achieve a software-defined datacenter (SDDC) to enhance business agility and reduce operational complexity. However, the...
Free E-Book: Public Cloud Guide
Free E-Book: Public Cloud Guide:
This white paper is for leaders of Operations, Engineering, or Infrastructure teams who are creating or executing an IT roadmap.
Free Tool: Virtual Health Monitor
Free Tool: Virtual Health Monitor:
Virtual Health Monitor is a free virtualization monitoring and reporting tool for VMware, Hyper-V, RHEV, and XenServer environments.
Free 30 Day Trial – Turbonomic
Free 30 Day Trial – Turbonomic:
Turbonomic delivers an autonomic platform where virtual and cloud environments self-manage in real-time to assure application performance.