Transcendent Integrator release 0.1


Transcendent Integrator is an EAI (Enterprise Application Integration) solution those mission is to provide a graphically oriented approach to data and business integration. We realise the importance of integrating business processes, but much complexity and programming is required in the details. Data integration - the ability to model any data type and transform it to another through rules is a powerful addition to any integration tool. The fusion of both data and business integration processes in a single software suite is what Transcendent Integrator is about.

The technology to be implemented in the integrator will include but not limited to the following -
  • Eclipse - GUIs
  • Java Groups - Clustering
  • JMS - Messaging
  • Log4j - Event Logging
  • JDOM - XML processors
  • BeanShell - Data mapping

The Transcendent Integration vision comprises of the following software components/characteristics.

Data Modeling & Mapping - Most/all data formats can be described in one form or another for processing by a computer. TI will provide the ability to create universal metadata descriptor which map to a transformation engine. The modeling process enables a developer to either import metadata (DTD, IDOC reports) or create data descriptors from scratch. These can be mapped to other data descriptors through a validation and transformation engine.

Business Process Management - The ability to graphically model business process/rules is invaluable. Avoiding overlap between the business rules in this component and the mapping rules There seems to be much overlap with Data Modeling and Business Process Management. Routing and business rules can be done at either levels.

Adapters - Adapters either read from or write to external data sources. Adapters are important to any integration broker. The role of the adapter is to read or write to data sources. An adapter will contain appropriate API calls to communicate with a data source and/or destination. In addition, the adapter should be able to be managed by an external resource or transaction manager. Where possible adapters should conform to the XA or 'two phase' commit paradigms for reliable inter-application transaction management. Adapters are also known as 'connectors'.

Reliability & Visibility - 'Self-healing' software can detect if any one of its components have crashed and recover gracefully. Clustering and replication can solve part of the problem. Monitoring tools are to be provided out of the box to show the status of business processes. This should also involve long running transactions where human intervention is required.

Messaging - Components in a integration broker should be able to pass messages to other brokers or within the same broker. Either an internal or standard messaging mechanism (JMS, MQ, TIBCO/RV) should be used. Delivery of messages should be guaranteed in the event of a crash or power-down.

...more soon