MorphIT Technology

Here you can learn everything about the technology of the browser based "user experience" user layer for the ergonomic operation of the CyberEnterprise business OS solutions used.

Integration into the ClassiX® architecture

The MorphIT application layer is an integral part of the ClassiX® architecture. While the application solutions written with InstantView include the functionality provided to a company by its model engineers, the MorphIT applications provide this functionality in an ergonomically optimal way for the user. In the MorphIT user layer, the focus is on the operation or the result to be achieved for the user rather than on the direct, more technical functionality.

The MorphIT application layer is purely browser-based and therefore available from all end devices that have a browser.

ClassiXArchitektur Apr2016 Vertrieb En

The used web framework

It uses the AngularJS http://angularjs.org/ framework, a Google project, which is generally available under the MIT license. ui.bootstrap http://angular-ui.github.io/bootstrap / is used as a basic component collection. ui.bootstrap is a replacement for Bootstrap.js written in AngularJS. Furthermore uiGrid is used for lists and tables.

Scaling of ClassiX® applications

ClassiX® applications can be set up in different scales, depending on requirements and existing infrastructure. From single-desktop operation to MorphIT applications for any number of users, everything is configurable. This section shows how ClassiX can be configured differently (native / MorphIT).

Few users - one workstation

With this type of setup, all the necessary components are installed on a machine from which the application is operated.
If no MorphIT-Launcher is set up on the machine, the ClassiX application must be started manually before the user can access it via MorphIT.

Native MorphIT
BasicSetup BasicMorphIT

Many users - One database server, many fat clients

ClassiX can be installed on several ClassiX workstations, which can access the same database via the local network and thus provide the same application on several workstations. In this constellation the workstations execute the ClassiX processes and must have sufficient hardware resources (fat clients).

Distributed ClassiX application (fat clients)
Distributed ClassiX application (fat clients)

Very many users - One database server, MorphIT and many thin clients

The use of MorphIT offers an even better possibility for scaling. End users only need a browser to use the application and are thus able to operate the software even from a smartphone or tablet (thin clients). Depending on the application, this can also be done via the Internet.

On the one hand, scaling is done by powerful MorphIT launcher machines, which start ClassiX instances according to the current demand and provide the computing power to run the application. On the other hand, the use of the static mode offers a further possibility of scaling. This way all requests that do not require a login are answered by the MorphIT server and a few ClassiX web service instances. In case the application is accessible via the Internet, this mechanism ensures that only those users get a ClassiX instance and thus access to resources that have been successfully authenticated to the server.

Distributed MorphIT application
Distributed MorphIT application
Distributed MorphIT application with web services
Distributed MorphIT application with web services

The pictures shown here show the maximum distribution to as many machines as possible. The MorphIT-Launcher and MorphIT-Server can also be run on the same machine without any problems.

The connection between InstantView and MorphIT

An application written in InstantView consists of one or more windows. Each window is serialised as a JSON and transferred to the MorphIT client (the browser) where it is displayed in the selected design. The user can interact with the interface as usual and thus remotely control the connected ClassiX instance via the browser in a RDP-like manner. The modern web design ensures that MorphIT feels like a real web application and like a mirrored native application.

This mechanism allows an interface & application to be defined once in InstantView and used directly both natively and on the web. To use the extended possibilities of a web interface (e.g. accessibility), there are MorphIT slots and MorphIT properties, which have no effect on the native interface and are only considered for the presentation of the web interface.

Another unique feature of MorphIT are the WebWidgets. Using JavaScript, HTML, CSS and InstantView, any widget can be rendered into a ClassiX window and you can interact with it as if it were a regular widget. The possibilities are only limited by the existing web libraries. WebWidgets are also supported natively, but they are not seamlessly integrated into the application. Instead, a browser window is opened from which the WebWidget can be operated.

Using the MorphIT feature Direct Links, URLs can be created with which you can enter the application at any defined position as soon as you open the link. This is realised by the fact that the URL contains an InstantView message, which is triggered in the connected ClassiX instance as soon as the browser connects to the instance.