kBOS Features Open Architecture (n-tier Architecture) Based on Microsoft Technologies · COM+ · .NET Technologies · SQL Server Clients · Windows Client · Web Client · Custom Clients kBOS High Level Architecture kBOS architecture is deeply routed in the principles of model driven software development since these concepts were introduced in the beginning of the 90s. Model Driven Architecture (MDA) describes how to create technology-independent models of business concepts, and then map them to different specific technologies.The kBOS architecture was extended in the last three years to combine model driven architecture with web services, thus creating an exceptionally rich environment for building flexible enterprise solutions. Central to the kBOS Architecture is the business services (work flow, document management, information modelling, learning modelling, services/applications management and organisational design). These services are implemented as COM+ components that run on a server machine. Each Business Service spans three layers (Presentation, Workflow and Business). Each service may also include specific database objects (tables, stored procedures, views, functions, etc.). The Presentation layer creates the user interface, receives and displays data from the workflow layer and passes user actions to the workflow layer for execution. The Presentation layer doesn’t perform any data operations itself, apart from simple validations. The workflow layer receives requests to perform specific jobs from the Presentation layer (typically in response user actions) and contacts the components responsible for executing the job in the business layer. The workflow layer knows how to call each component and pass it the appropriate parameters. It doesn’t perform any data manipulation itself, but it can translate parameters to a format understood by the other component and ensure that the parameters passed to the other component are correct. The Workflow layer contains one or more processor classes, which the presentation layer calls to perform a job on behalf of the presentation layer. A job may be as simple as forwarding the data to a processor on the Business layer, or as complex as calling multiple kBOS services on the Business layer and handling their output. Transactions that start at the Workflow layer are rather coarse-grained and shouldn’t be specified indiscriminately. If an operation takes a long time, the transaction and its locks will remain active for that time, preventing access to data. Furthermore, a transaction started at the Workflow layer may lock data that didn’t need transaction support. The components of the business layer provide the core business functionality for each Business Service. They enforce business rules, retrieve and store data through the data layer, and communicate with other Business and System Services. The components of the System Services layer provide functionality needed by all components in the business layer that is not part of any specific Business Service. System Services include logging and auditing support, versioning, communications, cryptography, etc. The data layer handles both query execution and database object manipulation. The data layer can create new database objects as needed using a set of code templates.
kBOS Features
Open Architecture (n-tier Architecture)
Based on Microsoft Technologies
· COM+
· .NET Technologies
· SQL Server
Clients
· Windows Client
· Web Client
· Custom Clients
kBOS High Level Architecture
kBOS architecture is deeply routed in the principles of model driven software development since these concepts were introduced in the beginning of the 90s. Model Driven Architecture (MDA) describes how to create technology-independent models of business concepts, and then map them to different specific technologies.The kBOS architecture was extended in the last three years to combine model driven architecture with web services, thus creating an exceptionally rich environment for building flexible enterprise solutions.
Central to the kBOS Architecture is the business services (work flow, document management, information modelling, learning modelling, services/applications management and organisational design). These services are implemented as COM+ components that run on a server machine.
Each Business Service spans three layers (Presentation, Workflow and Business). Each service may also include specific database objects (tables, stored procedures, views, functions, etc.).
The Presentation layer creates the user interface, receives and displays data from the workflow layer and passes user actions to the workflow layer for execution. The Presentation layer doesn’t perform any data operations itself, apart from simple validations.
The workflow layer receives requests to perform specific jobs from the Presentation layer (typically in response user actions) and contacts the components responsible for executing the job in the business layer. The workflow layer knows how to call each component and pass it the appropriate parameters. It doesn’t perform any data manipulation itself, but it can translate parameters to a format understood by the other component and ensure that the parameters passed to the other component are correct.
The Workflow layer contains one or more processor classes, which the presentation layer calls to perform a job on behalf of the presentation layer. A job may be as simple as forwarding the data to a processor on the Business layer, or as complex as calling multiple kBOS services on the Business layer and handling their output.
Transactions that start at the Workflow layer are rather coarse-grained and shouldn’t be specified indiscriminately. If an operation takes a long time, the transaction and its locks will remain active for that time, preventing access to data. Furthermore, a transaction started at the Workflow layer may lock data that didn’t need transaction support.
The components of the business layer provide the core business functionality for each Business Service. They enforce business rules, retrieve and store data through the data layer, and communicate with other Business and System Services.
The components of the System Services layer provide functionality needed by all components in the business layer that is not part of any specific Business Service. System Services include logging and auditing support, versioning, communications, cryptography, etc.
The data layer handles both query execution and database object manipulation. The data layer can create new database objects as needed using a set of code templates.