Key Principles (Magic xpa 3.x)
Most programs in a business application share a common schematic flow. The key principle of the Magic xpa deployment engine is that the code for supporting the common flow of a business task has already been written, compiled and tested to facilitate any specific business program. You can then fine-tune the skeleton of the business program to serve the needs of the actual program. Fine-tuning the schematic and pre-complied program unit of an application is done by declaring what actual artifacts are to be handled by the program, what is the precise logic needed to be executed by the program and what is the user interface design required for the program.
This metadata definition of the programs, together with other elements of the application that are also described in a metadata form, such as models, data sources, and Help screens, are stored in XML-based files that constitute the application source “code”.
The pre-compiled deployment engine is designed to support any business application functionality to provide application virtualization. The engine caters to every technological requirement and is transformed into your unique individual application by metadata driven specifications.
Being pre-compiled and metadata driven, the Magic xpa server engine serves as a virtual machine, enabling the implementation of the application on various server machines without making any modification to the application metadata. The virtual machine keeps a clear separation between the specific environment definitions and the application business logic, enabling customization for new deployments.
Magic xpa also provides compatibility with existing Magic applications, including eDeveloper and uniPaaS applications. This means that legacy business applications can be migrated to become available over the Web, while at the same time catering to the existing on-premise installed base.
One of the challenges of producing cross enterprise applications that centralize the IT of disparate units is the ability to properly support multiple languages both in terms of the user interface of the application and the collected and presented live data.
When you build an application you do not always know what languages your end users might speak. Magic xpa has built-in support for multiple languages, so you can add language support after your application is already built.
This is done using the MLS, or Magic Language Service. The MLS changes what is displayed to the user. The actual source application does not change at all.
Magic xpa lets you use the Unicode standard for data conversion and transmission. This capability is in addition to Magic xpa’s ANSI and OEM support.
