XML (eXtensible Markup Language)

In the real world, computer systems and databases contain data in incompatible formats. One of the most time consuming challenges for developers has been to exchange data between such systems over the Internet. Converting the data to XML can greatly reduce this complexity and create data that can be read by different types of applications. Consequently, XML has become the lingua franca of Internet communication but at the same time has splintered into incompatible implementations that require an intermediary like MitemView. An integration server, like MitemView, is also required to convert between XML messages and other messaging formats like HL7, WebSphere MQ and TIBCO.

MITEM natively supports XML-based messaging protocols by fully implementing and insulating the transport and parsing functions inside a pre-built MitemView adapter.

This advanced adapter offers multiple advantages over the typical low-level, code-intensive implementations that are found in other integration servers:

  •  Single-step routing and transformation of messages
  •  Consistent development experience across all formats and protocols
  •  Substantially less programming
  •  Graphical interface for mapping and message processing
  •  Fastest message processing at runtime
  •  More robust error handling & recovery
  •  Externalization of host dependent meta-data
  •  Connects with 3rd party repositories

MitemView's Enterprise Messaging Architecture allows different message and document types (e.g. XML) to be transmitted over different protocols and transports (e.g. WebSphere MQ, SOAP or TIB/ActiveEnterprise) in a normalized way. By insulating the developer from working with low-level APIs the learning curve is reduced dramatically and message formats and protocols can be changed in the future without requiring a re-write of the integration control and business logic.

Other integration servers that look similar to MitemView on the surface have only crude, if any, support for messaging protocols. Rather than normalizing the development experience they require discrete knowledge of vendor or community APIs. This low-level approach greatly increases the cost and complexity of interfacing between multiple systems by forcing the developer to learn the programming model for every protocol. In contrast, a developer that knows how to use MitemView to interface with one system automatically has all the requisite knowledge and skills to interface with any other.

A further defining characteristic of the MitemView framework is the real-time processing of messages across multiple in-bound and outbound connections. This real-time, asynchronous processing enables maximum flexibility in n-tier server architectures and produces superior end-to-end system performance. MitemView performance levels meet or exceed the near real-time performance of other messaging systems, while eliminating the complex conditional programming required for coordinating multiple transactions. Furthermore, multiple host transactions can be combined, or marshaled, into a single message thereby reducing the total number of transactions that need to be developed and managed.

| contact us | company | products | solutions | customers | news & events | site map

© Copyright 2015 MITEM Corporation. All Rights Reserved
Privacy Policy