Product :::Administration

Administration
As a self contained application server utilizing a standard http server, EA WebModeler eliminates the overhead, maintenance, and administration requirements of competing portal solutions. Deployed as a standard web-client solution, configuration management is literally reduced to a single server for an entire enterprise. EA WebModeler's usage of standard relational databases for storage, enables maintenance, backup, and other administrative activities to be performed by in-house dba's, eliminating the need for specialized resources. And, in addition to built-in design for low administrative impact, EA WebModeler includes browser based administrative tools to accomplish tasks such as monitoring and terminating sessions, bulk data changes, and generating repository usage/coverage statistical reports.

Security
EA WebModeler implements a comprehensive security model. This is necessary since EA WebModeler may be used in environments where a great deal of sensitive information is held. This may pertain to corporate strategy, personnel evaluations, or patient histories. The model has been designed to be very flexible, but at the same time relatively easy to administer.

EA WebModeler Users and User Groups
An individual with a password to sign on and use the EA WebModeler tool is an EAWebModeler User. An EA WebModeler user can belong to none, one or more User Groups. Where rights are assigned to a group, all users in that group will have the relevant rights. A user can belong to several groups, thereby acquiring the rights of all the groups of which he/she is a member. Users are assigned to groups by creating an EA WebModeler User for the group, assigning the desired privileges to this user; creating EA WebModeler Users for each of the group members, but not assigning any privileges to these; then linking the users to the group via the "Group has members / is member of group" relationship.

Area Security
Area security is a concept that allows us to control what functions (e.g. browsers) within the tool a user or group may access. This would allow us to exclude users from maintaining types, for example, using the Type Browser. Each major functional area of the tool has an associated Area Security item.

Access Level
Access Level items reflect the access privileges of a user or group to a type, default item, or instances of the type (items). Each entry has five or less characters, with assigned meanings as follows:

C = Create - user is allowed to create items of this type
V = View - user may view items of this type
U = Update - user may edit and change items of this type
D = Delete - user may delete items of this type
T = Template - user may modify templates associated with this item

Access Levels are used to control access at three different levels:
Meta - Permissions related to working with the type definition

Default - Permissions related to working with the default node for the type
Instance - Permissions related to instances (items) of the type

If the relevant code is present in the correct level of the access level linking a user (or group) to the type in question, then the action can be performed. For example if we are dealing with an Access Level entry that looks like this:
MetaAccess V
DefaultAccess VU
InstanceAccess CVUDT

then the user could:

View the meta data (the type definition in the Type Browser)

View and Update the Default item for the type

Create, View, Update, Delete and work with templates for the items of the type

Effect of Rights
EA WebModeler filters all information rendered to a user using the security settings. Any functions, items, actions etc. that are not permitted are simply not shown to the user. I.e. if a user does not have rights to use a certain browser or function, it will not appear on a toolbar and/or associated buttons will not be present. If a user may not see certain types, they will not appear in any lists presented to the user. If a user may not see defaults for a type, they will not appear in the instance lists, and so on.

Timing
Security information can be altered at any time by an authorized user. Settings for a user are read at logon time and will remain in force for the duration of that session. If you want to change rights for a logged on user, they may be altered, but the user will have to log out and log in again to see the changed rights.

Sessions
A new session is started each time a user logs in to EA WebModeler successfully. If EAWebModeler detects long inactivity for a user, the session will expire (this is to preserve security when users do not log out, but leave their browser open and logged on). If the session has expired and further activity is attempted, the user is informed that the session has expired and a new log on is required. The immediate effect will sometimes be that all functions and lists in the browser are blank - this occurs because EA WebModeler filters the information provided by what is allowed, which is nothing if the session has expired!

We invite you to discover our exciting EA solution. Please complete the form below and a representative will contact you soon