Innovation for Tomorrow and the day after.

eNIGMA:

Fundamentally, Enigma architecture is about the manipulation of data sources. Its encapsulation framework -- whether it is imbedded or positioned as an adjunct--receives data streams and performs the necessary transformation that are needed to make it compatible to the next application-tier or business-process down the line.

Traditionally, this has been accomplished for quite a while in the form of hard-coded interfaces that had to be constructed for each translation. This approach to the integration problem is never a lasting solution, it's been more like a work-around waiting for the right technological solution.

eNIGMA is a distributed framework providing an application and protocol transparency layer enabling negotiation of communication protocol qualities, comprehensive support services for heterogenous application and a novel interaction architecture.

Provide support services for applications and an interaction framework which allows the description of workflow-like interactions between autonomous modules.

Enigma enables any application or data store to share information with any other application or data store that exists within the enterprise value chain.

The primary objective of the enigma architecture is to provide a reliable, consistent, and flexible, "framework" for software creation that can rapidly address the enterprise application integration market needs. The concepts discussed below contribute to uniqueness of this intitiative.

Division of functional responsibilities
- Modularity achieved by first defining and labeling the functional parts (modules) of the enterprise ecosystem and secondly by describing the scope of responsibility for each identified module.

Platform independence
- The enigma architecture design includes a public message interface which accomodates the constraints of involving dissimilar application platforms and operating system environments. This allows the creation of an application integration framework that is not concerned with nor dependent upon a specific application platform or operating system. This approach allows for the mixing of software solutions from various programming languages and operating systems.

proprietery messaging protocol
- every enigma application integration bridge is designed to be a self-contained, stand-alone executable program whose only exposure to the enterprise ecosystem is through a public message interface or protocol.(This means that all inter-dependent applications remain encapsulated and independent to perform their designated task(s) within the bounds defined in the system design.)

Event-driven operation
- Applications integrated through the enigma framework respond to asynchronous, dynamic events that transpire over time. For example, the creation of a "transaction" in the system sets off a series of events that may involve interaction between multiple modules via the public message interface. Broadcast message dispatches are another example of efficient event-driven operation. These events typically transpire as the result of some change in state or timed condition. The recipient is instantly made aware of the change in state without having to query (or poll) the source.

Public message interface
- All interaction between functioning modules is managed through a well-defined public message interface. This byte-oriented, serial interface is called Inter-Module Communication. This interface allows an application to transmit and receive data via a defined packet structure. The interface is totally asynchronous in nature, full-duplex in operation, multithreaded, and is not constrained by protocol or strict timing specifications.

The enigma environment has been structured to isolate the application from the transport layer of the interface. The application is responsible for populating the data portion of an outbound inter module communcation packet and indicating the intended recipient. The transport layer components of the system are responsible for delivering the packet. Correspondingly, received packets are delivered to the application in a system-provided message/fifo queue.

Established lines of division combined with a consistent public message interface provide a stable environment for the integration of enterprise applications.