edgeCore is a new platform from the ground up and in concept carries over many features from enPortal / AppBoard along with completely new approaches. Consult the Feature Matrix for a quick overview of enPortal / AppBoard features and how they map to edgeCore features.
Due to the product differences, migrating from enPortal / AppBoard cannot simply be a case of exporting a backup (archive) from the old system and have this load and work in edgeCore . This document outlines a migration process and items for consideration when migrating to edgeCore .
This section highlights the key differences and similarities between enPortal / AppBoard and edgeCore .
enPortal / AppBoard
Roles are also similar in that a user may be a member of one or more roles. The differences are that in enPortal/AppBoard a user is only ever represented by a single role when logged in, and they are able to switch between roles via the role selector. In edgeCore a user’s display is a combination of all roles, and there is no role selector. The main implication of this is a user will see the aggregate of all content assigned to them from all roles when logged into edgeCore . There is also a special AllUsers role that all users are automatically a member of. Also in edgeCore roles cannot be assigned to domains, and Credentials can only be assigned at the global, domain, or user level – not to roles.
The main difference is with the ability to configure pre-authentication server execution (via JSP in enPortal/AppBoard) along with custom authentication flows. For assistance with this in edgeCore , please contact Support.
When configuring a connection the credentials could be either Static or Variable. Static credentials are provided directly as part of the connection configuration. In this scenario, everyone accessing the content would be using the same credentials and this is more typically the case when accessing data sources. More likely for web-content, Variable credentials will be used. In this scenario, a reference is made to a system managed credential which could resolve to Global, Domain, or User specific values depending on how it is configured. The most specific value takes precedence just as with enPortal SSO tokens.
A benefit here over enPortal is that the system-managed credentials are not tied to a host+port as with enPortal. They are associated with connections via configuration so that a single system managed credential could be used for multiple connections if that happens to apply. edgeCore also allows for credential expressions in order to support pass-through authentication (e.g. password used by user to log in to edgeCore is passed through when authenticating to a particular connection).
Web Adapters include rules and other materials for officially supporting particular applications, but edgeWeb can also be extended through the use of custom rules.
For example, the edgeData equivalent of a DB source with 3 queries would be a DB Connection and 3 Feeds.
Also note that credentials for Connections are managed using the new Credentials system (refer to Credentials above).
It is likely that the Stacks in an AppBoard deployment would roughly correspond to the top-level Content Tree Folders and Pages in edgeCore .
edgeCore offers many new features and different ways of solving problems for customers compared to enPortal and AppBoard. While the focus of migration may be to quickly get up and running on the new platform, it is recommended to also visit some of the new capabilities in a second or subsequent pass in order to deliver even greater value to users of the system. Some recommendations:
Unlike AppBoard, all Visualizations are supported on mobile devices. Also, installation of an app on the mobile device is not needed – simply navigate to the edgeSuite URL in the mobile browser.
For cases where a Web Widget was used to directly reference external web content, there is no equivalent for this widget in edgeCore. At the point it is introduced, it is still likely to make use of Page Variables and Node Variables to set the URL (or part-URL).