Topics
Prev Next

User Guide

The functionality of the Visibility Levels feature is primarily restricted to System Administrators, in order to setup and configure models to limit access to certain Packages in a model. Generally, users will not be aware of Visibility Levels; they simply won't see certain Packages in the model.

Defining Visibility Level Aware Database Managers

For the most part, defining Database Managers in the Professional ('Pro Cloud') version of Sparx Systems Cloud Service Configuration Client is the same process as for the regular version. These are the exceptions:

DBMS

Discussion

See also

Oracle

All Oracle connections require a 'DefaultSchema={schema_name};' option manually added to the connection string, where {schema_name} is the physical name of the schema that owns the Enterprise Architect tables. For example:

    Provider=OraOLEDB.Oracle.1;Password=pass;Persist Security Info=True;User ID=user1;Data Source=ORA_SN;DefaultSchema=owner_user;

In a typical Oracle connection to an Enterprise Architect model the 'User ID' option is both the owner of the tables and the user credentials that are being used to access the data. However, in a model using the Visibility Levels feature, these options are different, so the 'DefaultSchema' option has been added to define the table owner.

Microsoft SQL Server

All SQL Server connections require an 'Alias' field value that uniquely identifies the database manager on the current server. The 'Alias' value is the name by which Enterprise Architect users know the model.

In previous versions of the Cloud Service, the database manager alias for SQL Server-based connections was automatically determined by the database name, which meant that each SQL Server database could only ever have one database manager defined in the Cloud Service. Now with the use of the 'Alias' field a single database can have an unlimited number of database managers defined.

Enabling the Extended OLSC Interface on a Database Manager

In order for the Pro Cloud Server to allow the use of Visibility Levels in a model the 'Enable extended OSLC interface for WebEA' option must be selected. This is achieved by opening the Sparx Systems Cloud Services Configuration Client application (SSProCloudClient.exe) connecting to the appropriate server. You then select the database manager in the list and click on the Configure button. On the resulting Configure Database Manager screen select the 'Enable extended OSLC interface for WebEA' checkbox.

Visibility Level Administration

When Enterprise Architect is used to connect to a model that has Visibility Levels the only new feature is the 'Set Visibility Level...' menu item available under the 'Package Control' item in the context menu of the project browser.

If your model has security enabled then all application users that require access to the 'Set Visibility Level...' menu item will need to be allocated the 'Visibility Level Admin' security permission, using standard Enterprise Architect permission assignment.

Set a Package's Visibility Level

From within Enterprise Architect, the Visibility Level of a Package can be set using the Project Browser context menu item 'Package Control | Set Visibility Level...'.

This menu item will only be available in models that have been set up for Visibility Levels and when they are being accessed via a Pro Cloud server connection.

Once a Visibility Level has been set on a Package, that Package and all of its children can be viewed, accessed and updated only by users with the corresponding access level or higher, set in user security.

To remove a visibility level from a Package (and all its children), simply set the Visibility Level back to zero.

Visibility Levels users can apply

Users can only set the Visibility Levels on Packages to levels the current database user has access to. For example, a Enterprise Architect client connected to a Cloud connection that uses a database user that has been assigned levels 3 & 4 can update the Visibility Level of any Package to the levels 0, 3 or 4.