Basic Understanding of the Need for Data Bridge Interface

Enterprise Console will be deployed as a central server, which can serve multiple applications simultaneously.

Each application could potentially have its own Users Database. For example, one of the applications might be connecting to Active Directory, other might be connecting to Database, something to LDAP or ADAM.

When AVEVA Work Tasks deals with each of these applications, it needs to ensure that users of these applications can work with AVEVA Work Tasks without any complicated configurations, and also in a secure manner which ensures only authorized functionality is available to each and every resource.

Enterprise Console will also act as a Work Bench for all the workflow participants, hence it needs to allow user authentication from variety of sources. For example, an Application spanning internal as well as external vendors and customers, needs to have variety of database access requirements possible.

Different applications might be using the same Authentication source, but might have different Metadata and grouping information with them. For example, the authentication source could be an active directory, but there could be five other applications that are using the same user and maintain application-specific user metadata. Hence, in reality if all the information is needed about the user it needs to be collected from across all the application as well as active directory.

Sometimes it is expensive to query every time on the user database, so the results are cached heavily.

The user integration is outside the Application boundary since the users can span across multiple applications.