ePortal Generator Architecture

The following diagram describes ePortal and EAE/AB Suite integration architecture and how the ePortal generator is used:

Figure 41. ePortal and EAE/AB Suite Integration Architecture

ePortal and EAE/AB Suite Integration Architecture

A Component Enabler (CE) bundle can be deployed for an EAE or AB Suite application using the ePortal generator. The ePortal generator generates a set of XML files based on the ispec data definitions and the Presentation properties of the forms designed in EAE or AB Suite Painter. This generator generates one XML file for each ispec in the CE bundle.

Using the ePortal Import Wizard, you can import the generated XML files into an ePortal Data Source for the EAE or AB Suite application. The corresponding Server messages are created in the same ePortal Data Source. When you create an ePortal Presentation, Client Messages are automatically created, as appropriate and presentation information contained in the XML files is used to generate corresponding forms or services in the ePortal Presentation project.

Refer to the ePortal Developer Online Help for more information on Import process and ePortal Import Wizard.

Figure 42. ePortal Runtime Architecture

ePortal Runtime Architecture

The ePortal runtime uses connectors to interact with applications on MCP and OS 2200 host platforms. The connector exchanges data between the host application and the supported presentation types such as ASP.NET Web Forms for desktop and mobile applications, WCF, REST and ASP.NET Web Services. These applications use client messages to communicate with the ePortal runtime environment. An orchestration module intercepts the client messages and creates server messages that are sent to the host system through a connector. The AB Suite/EAE connector interfaces to the ePortal orchestration module and provides access to AB Suite or EAE applications through the Component Enabler/RATL interface.

The following figure illustrates the development process of an ePortal solution for an EAE/ AB Suite application:

Figure 43. ePortal Runtime Architecture

ePortal Runtime Architecture

To develop an ePortal solution for an EAE/AB Suite application, perform the following:

  1. Setup a Component Enabler folder (bundle) in AB Suite or EAE Developer containing the ispecs required for use in the ePortal solution.

  2. Generate the Component Enabler bundle folder using the ePortal Generator. This creates the XML files in the specified output directory.

  3. If your solution requires images, add them to the output directory in the appropriate location.

    Refer to Adding Images to the Generated Output Folder for more information.

  4. If your solution requires a custom field translator, add it to the output directory in the appropriate location.

    Refer to Field Translators for more information.

  5. Create an AB Suite/EAE Data Source project in ePortal Developer.

  6. Import the files from the generated output directory into the AB Suite/EAE Data Source project using the ePortal Import Wizard.

  7. Configure the Component Enabler connection options for the host application.

  8. Create the required ePortal Presentation Project from information contained in the Data Source project

  9. Build the solution.

    Refer to the Portal Developer Online Help for more information on the development process steps.