Enterprise Integration Platform
The Enterprise Integration Platform (EIP) is a three-tier integration architecture designed to cater for all types of integration scenarios required within a complex ICT landscape. The EIP allows for the rapid delivery of integration solutions across the Enterprise by abstracting the complexities of integration architecture from application developers, thus freeing resources to focus on the business problem at hand rather than the “plumbing” code. This results in a more efficient use of software development resources, and significantly lowers the organisational resistance to change caused by restrictions on integration capabilities.
The EIP is comprised of the following Microsoft technologies and components:
- Windows Communication Foundation (WCF) – framework for developing services on the .NET Framework
- Windows Server AppFabric – Application Server for hosting WCF services & workflows
- Windows Azure – Elastic cloud deployment platform
- Microsoft BizTalk Server – on premise integration, messaging & process orchestration engine
- SQL Server Integration Services (SSIS) – data integration & transformation platform
- SQL Server Reporting Services (SSRS) – reporting platform for business processes auditing and operational management
- SharePoint Server & PerformancePoint Services – business intelligence dashboard for overall analysis and understanding of all business processes that are executing within the integration platform
- Mexia Acceleration Framework (MAF) – software framework for jumpstarting integration development projects
The goals of the EIP design are:
- Layered Architecture - To separate the components of the EIP into Services, Business Process Management, and Data processing tiers, each of which is responsible for specific tasks according to the messaging integration requirements
- Message Driven - To develop a message-driven architecture rather than an RPC-style system to support coarse-grained message interfaces. This provides payload flexibility and allows the separation of messaging infrastructure from the application-specific code
- Open - To strive for an open-architecture that allows individual layers to evolve over time without breaking any dependencies
Benefits of using the EIP
The goals of the EIP design are:
n
|
Layered Architecture - To separate the components of the EIP into Services, Business Process Management, and Data processing tiers, each of which is responsible for specific tasks according to the messaging integration requirements;
n Message Driven - To develop a message-driven architecture rather than an RPC-style system to support coarse-grained message interfaces. This provides payload flexibility and allows the separation of messaging infrastructure from the application-specific code;
n Open - To strive for an open-architecture that allows individual layers to evolve over time without breaking any dependencies.
Quick Contact
| Brisbane - 07 3181 5621 |
| Sydney- 02 9089 8624 |
| Melbourne - 03 9008 5996 |
| Request Contact |