KOMET Unleashed - DSS Kernel

Figure 1: Class Diagram of the DSS Kernel (Click the image to enlarge it)

The DSS kernel is responsible to mediate between the subsystems of the KOMET architecture (layer orientation). The DSS kernel defines different services, which are requested by the components of the subsystems (service orientation), to fulfill this responsibility. This works in a way that a component sends a service request to the DSS kernel, which uses the request to perform further operations, generates a service response and sends it back to the component. KometML (see here) serves as common language, which service requests as well as service responses are coded in.

• Scenario Information Service
  The Scenario Information Service provides basic solver configuration data. Posible data are e. g. the thinning strategy or the type of harvesting technique used (manually with chainsaw or mechanised with harvesters).
• Scenario Write Service
  The Scenario Write Service stores the changed scenario definition data in the data base
• Solver Data Write Service
  It is possible to activate or de-activate every solver individually. This information is stored in the data base by the Solver Data Write Service.
• Solver Information Service
  The Solver Information Service reads the registered solvers from the data base and groups them in layers based upon their dependencies. That is, all solvers of a certain layer are dependent on results provided by solvers residing in a lower layer.
• Data Information Service
  The Data Information Service provides information about solver data. Ontology data such as object class and assigned container class (see here) are sent to the DSS kernel, which sends a response containing table name, column name, etc.
• Data Query Service
  With help of the Data Query Service, an SQL command can be sent to the DSS kernel. The result of this command is sent back to the requesting client.
• Result Information Service
  The Result Infomation Service provides information to the complete amount of solver data registered in the SDSS.
• Ontology Query Service
  With help of the Ontology Query Service, a command in the ontology query language RDQL can be sent to the DSS kernel to query information stored in the semantic network. The result of this command is sent back to the requesting client.
• Registration Service
  Solvers are registered in the SDSS with help of the Registration Service.
• Unregistration Service
  The Unregistration Service is used to delete solvers from the SDSS.

The reference implementation of the DSS kernel in Java consists of 28 classes and four interfaces. the interface KometKernel serves as call interface of the DSS kernel. Its only method is KometKernel.request. A string containing the service request serves as method parameter, a string containing the service response is returned by this method.

• KometKernelImpl
  The server class, which interprets the service requests and passes them on to the class KometMetaDB. An instance of KometKernelImpl is generated by the class KometKernelServer, which starts and initialises the DSS kernel.
• KometKernelClient
  This is a local placeholder class, which initialises the network coupling to KometKernelImpl and passes service requests. Thus, network specific implementation details of the KOMET Architecture are hidden from a programmer.

Das Klassendiagramm ist in Abbildung 2 dargestellt.

Martin Döllerer - zuletzt geändert am 01.01.1970 um 01:00 Uhr