|
Here you’ll find an overview about the main features Hermine Server has:
Configuration
Most of the parts of Hermine Server are flexible and might be put together depending on the needs of the environment it is used. For that a configuration file is used. The server includes classes reading this configuration file and defines a way to fit to process of starting to individual needs.
Error handling and logging
All server side exceptions are transported to the client and optionally logged at the server. There is an extension interface where the logging might be customized. Within the default development the is a simple text file logging and a logging into the system debug monitor. Customized logging may write those information about the exception into a database or depending on kind of exception sending mails to inform administrators.
Consoleapplication as host
A simple consoleapplication constitute the process container. It may used for development only or manual start and stop of the server.
Windowsservice as host
A windows service hosts the Hermine Server so it might be executed with system start and stopped with system shutdown. Admins usually prefer this kind of host.
Adding tags, getting information about tags
There is an interface for adding tags and retrieve information about this. This interface is WCF based and the used protocol depends on the host configuration.
Getting tagclouds by timespan
Getting a tagcloud by the input parameter start and end time.
Getting tagclouds by relatives
Getting all relatives from a tag as input.
Batchbuild
Besides the using of a Visual Studio solution a batch file for building all assemblies, documentation and other things might be useful. It is a console batch file that uses msbuild.
Observers
Observers are the best way to find and consume meta information. They may searching for files or other sources of data. They get passed a set of tools for analysing text and putting the results into the Hermine Server persistence.
Singletime observer execution
The observer is called once and then finished.
Scheduled observer execution
The execution of the server may be scheduled and iterative.
Client API
There is an API for clients for tag controlling.
API documentation
For the use of the client api it needs to have a api documentation. We use sandcastle for building that.
Simple client console
The interface for development and inspecting the functionality of Hermine Server is a simple client console application. It has no other sense but for that it is useful.
System integration
For local desktop use a system integration is useful. It is configurable for local users as far as they like the see the results Hermine Server gives.
GUI based client
All functionality might be available by a GUI-based client application.
|
