Scense Administrator Guide

  1. Home
  2. Docs
  3. Scense Administrator Guid...
  4. Scense Architecture

Scense Architecture


Scense overview

The Scense system consists of several components:

  • Server components
    The server components shape Scense’s “Business Logic”.

These components provide all required data to the Client components.

  • Client components
    The Client components ensure tasks are actually executed on the user’s workstation.
  • Scense Explorer
    The administrator uses Scense Explorer to manage and control the Scense data stored in the Scense database.
  • Scense Database
    The Scense Database contains all necessary data for Scense to function properly.

Scense Architecture

C:\Users\rkuiper\Desktop\Scense Architecture.png

The Scense architecture exists of several tiers:

  • Scense Client
    This component executes scripts (logon, logoff etc.), 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. Scense Executive receives tasks from Scense_Client.exe and from Scense.exe. After receiving these tasks Scense Executive communicates with the Scense Engine.
  • Scense Engine
    This server component forms the heart of the Scense system. Through HTTP, this web service is used by Scense Executive.
    Scense Engine receives tasks from Scense Executive and then communicates with the database engine.
    The Scense server component makes maximum use of the scalability of Internet Information Server (IIS). Clustering can also be used for the Scense server component.
  • Database
    Ensures data storage. Scense is compatible with Microsoft SQL Server (2005 or higher), and Oracle (9 or higher).
    The database engine receives queries from Scense Engine.

Task structure.

Starting from Scense_Engine, the abstraction level of the tasks increases gradually while passing to Scense_Client.

  1. For example, Scense_Client gives Scense_Exec the task to ‘Execute Logon Script’.
  2. Scense_Exec will ask the Scense Engine to retrieve all relavant Scopes for this user’s logon script.
  3. Scense Engine will execute detailed SQL-statements on the Database Server to retrieve all relevant Scopes and the corresponding Criteria.
  4. Scense_Exec receives the Scopes and Criteria and starts consolidating and prioritizing the criteria so it will have to test as least criteria as possible and still determine the result of all Scopes.
  5. After Scense_Exec has tested the Criteria it will ask the Scense engine to return all relevant TaskSet/Session-Events for the ‘passed’ scopes only.
  6. When Scense_Engine has collected all necessary data, it will respond to Scense_Exec.
  7. Then, when Scense_Exec has received all data from Scense_Engine, it will execute the collected tasks.
  8. When Scense_Exec executed the complete Logon Script it will return to Scense_Client.

Scense_Client will constantly be informed by Scense_Executive on the progression and details of the tasks being executed. This enables Scense_Client to provide feedback to the user by means of a progress indicator.