Back to > Overview > Developers Guide

The SEP database engine

Authors:
	Szabo Csaba <crow@nolimits.ro>
	Antal Attila <atech@nolimits.ro>

Table of Contents

1. Database Structures
2. The SEP engine block
3. Drivers
4. SEP (Simple Exchange Profile)
5. Utilities

2. The SEP engine block

The SEP engine framework block uploads from the configuration file the database specifications into the memory context.

3. Drivers

BEEP Driver - This driver is used when a client want to make connection to the SEP profile on the server side.
Local Driver - This driver is used for connecting the SEP profile to the database.

4. SEP (Simple Exchange Profile)

For internal language Datastore uses the SEP commands. For parsing those commands we use an antlr based solution. You will find this parser file named sep.g in the datastore_home/src/main/org/media/datastore/sepengine/parser directory. When you make build, from this file will be generated the following files:

sepLexer.java
sepParser.java
sepTokenTypes.java
sepTokenTypes.txt

5. Utilities

The database engine has some utilities. Here are some of the most important:

Lexicon Manager - checks out nonbraked documents, brakes down the data into words and stores them in lexicon and barrels
Log Manager - makes a shortcut between a framework logger and the SEP engine logger, a helper class to put all log messages into the framework logfiles
Sep Intrpreter - builds SQL command from SEP fetch command
SepDBHandler - basic database operations for documents
SepAdmHandler - database operations to administrate users, groups, owners, acces permissions and subtree management