Architecture Scense

The graphic below shows a simplified overview of the Scense architecture. End users work on client devices (physical or virtual). These client devices contain the Scense client software. The scense client interacts with the Scense database via the Scense engine object (or with the local cache if the database is not available). The database, containing all the business logic of the desktop environment, is managed by the administrator by using Scense Explorer.

architecture Scense

Scense Client

This component executes tasks on the desktop and gives feedback to the user by means of a progress indicator. The Scense Client component also provides a user interface which enables the user to execute several tasks on the workstation. 

Scense Executive

This component actually executes the tasks at the user’s workstation. After receiving these tasks Scense Executive communicates with the Scense Engine.

Scense Explorer

The administrator uses Scense Explorer to manage and control the Scense data stored in the Scense database.

  

Scense Engine / Repository

These server components form the heart of the Scense system. Through DCOM, these COM+ objects are used by Scense Executive. Scense Engine receives tasks from Scense Executive and then communicates with the database engine. The Scense server components make maximum use of the scalability of COM+. Network Load Balancing can also be sed for the Scense server components.

Scense Database \ Local Cache

The Scense Database contains all necessary data for Scense to unction properly. Scense is compatible with Microsoft SQL Server (7.0 or higher), and Oracle (8i or higher). The database engine receives queries from Scense Engine. To ensure a functional desktop hen a connection to the central database is not available, information about the desktop is also tored in a local cache.