Magic xpi Open Architecture (Magic xpi 4.7)
The Magic xpi Server is the engine behind the integrated business processing environment. The Server provides a highly reliable and scalable platform that enables efficient deployment of strategic business integration solutions.
Magic xpi’s open architecture enables you to make use of the following capabilities.
The Magic xpi Server can be deployed natively on a range of platforms, such as Windows, IBM i, Linux, Windows, AIX, and SUN Solaris. This ability lets the user:
-
Develop a project on the Windows platform and deploy it without changes on different platforms.
-
Split a project between different servers, on different platforms, offering scalability and load balancing capabilities.
-
Create a multi-project environment, where each project includes its own set of business processes and integration flows.
Magic xpi can connect to the following database types: Oracle, MSSQL, DB2/400, DB2, Pervasive.SQL and any other database supporting ODBC.
In addition to its comprehensive toolset, Magic xpi extends its capabilities by providing a built-in Connector Builder that allows the user to define new components and adaptors. The Connector Builder supports developing new component code using Magic Software’s Magic xpa, and wrapping existing Magic xpa or Java classes as Magic xpi components that can be used in any Magic xpi project.
Magic xpi’s environment definitions are saved in a central environment repository, an external XML file that can be updated by any XML tool outside the Magic xpi Studio and can be shared by several projects. All components and services used in a project access the same environment repository file. Using different files during different stages of the project life cycle allows the changing of environment settings without touching the project code.
The following table lists the main building blocks of any Magic xpi project. It is not obligatory for each integration process to involve all of these entities.
|
|
|
|
Resource
|
Definition of servers, DBMSs, applications, Web servers and any other resource in the project IT environment.
|
|
Service
|
Magic xpi’s exposed functionality that defines how flows are invoked from an external system. The Services include Web Services, HTTP, and more.
|
|
Repository
|
Project-related repositories that include components, servers, applications, and variables.
|
|
Integration flow
|
The integration flow is a set of steps and their logic that control the order of the steps' execution, called flow orchestration. The integration flows are executed by the Magic xpi Server during deployment.
|
|
Component instance
|
A component instance is activated as a step or a trigger of an integration flow sequence. Flow components can have connecting, adapting, converting, and processing capabilities.
|
|
Trigger
|
Triggers are used to activate a specific flow due to external activation, such as HTTP or Web Services calls, or due to flow orchestration definitions, such as Scheduling.
|
|
Magic xpi utility
|
Magic xpi utilities provide flow logic orchestration capabilities, such as scheduling, Publish and Subscribe and Invoke Flow, as well as data handling services, such as Flow Data.
|
|
Mapping
|
The Data Mapper is a graphical utility providing data manipulation, transformation, conversion and enrichment capabilities.
|
