It begins with your current business processes and your specific organizations needs and goals. Using MTG Frameworks, we then build an integration structure that enables each individual team to maximize the functionality of your "best of breed" applications while still being able to share data seamlessly with other functional areas of your business.
The end result is a "custom" integration solution that matches your business needs and goals with little or, more commonly, no custom programming. Because no programming is required, the client is left with an integration solution that can be managed with internal staff and without extensive external support.
These are "process driven" integrations that exactly match your business.
A core aspect of MTG Frameworks and "process driven" integrations are the integration services running on the server. The combination of services allows for the automated execution of the designed "process driven" integrations without end-user intervention.
This fundamentally means that transactions occur according to defined business process rules without the need for a user to invoke a transaction. Information arrives in each system, at the place, and the right time.
The adapter is the source of all documents and the final destination of all documents. We have built adapters for all systems we integrate with and we are continuously adding more. These adapters are 'pluggable' meaning we can go back to any completed solution and install a new adapter to expand a client's integration solution. This means a single platform that can grow with your business. We can also create custom adapters for the "in-house" solutions companies have built to run their business.
|Oracle Primavera||Contract Manager||2001||Yes|
|IBM||AS400 / DB400||2001||Yes|
|Trimble||Prolog Manager / Converge||2004||Yes|
This is the primary application for building all integrations in MTG Frameworks. Thru this application, integrations are implemented to mirror business processes. It is a completely configurable environment that allows the application to enforce all necessary business rules, record the success or failure of each transaction, and to record a history of all transactions.
Integrations can be configured to run manually, by schedule, or by "listeners" which is a service that can be configured to look for specific data conditions and when they are present, automatically submit the integration to the engine.
This is the primary application where the individual who has the responsibility to manage and maintain the integration will spend most of their time - we refer to this person as the "integration owner".
This application is used to manage the results of the integration after it has been processed by the integration engine. The primary purpose of this application is to access the transactional history of the integrations to view successes and errors and to actually view the corresponding documents associated with those transactions.
This application differs from the Designer in that no modifications to the integrations are permitted. This is a view only application designed to analyze the results of an integration process and allows for users other than the "integration owner" to help manage the integrations.