The EMobDa backend is dedicated to the processing. It handles request received from the frontend.
There are 2 types of backend.
The first one is accessible through a socket, and can be hosted by another machine that those on where the frontend is launch, and is therefore called the remote one. More then one one frontend can be connected a once on a backend of this type, as typical on a client/server architecture. This backend takes the shape of a daemon.
The second backend type (under development) takes the shape of a dynamic library and is directly loaded by the frontend, and is therefore called the local one. This architecture is dedicated for a mono-task/mono-user architecture.
Both types of backend share the same locales file and configuration file (although some very few configuration parameters some configuration are needed by one backend type and ignored by the other).
The configuration file is mandatory. You can give a configuration file name using the –cfg option of the emobdadmn application. If you do not so, the backend daemon will use the file named emobdadmn.xcf in the current directory.
The configuration file is in XML format. The Epeios XML preprocessor tags are handled, (like you would apply the expp tool (http://zeusw.org/intl/expp) to the configuration file).
This is the general aspect of a configuration file :
<Configurations> ... <Configuration target="TARGET"> CONFIGURATION </Configuration> ... </Configurations>
The are two values available for TARGET :
emobdadmn if the backend is the daemon (remote) one,emobdalib if the backned is the library (local) one.<Service>SERVICE</Service> <Repository>REPOSITORY</Repository>
SERVICE is the port to which the daemon will listen to, in the case where the backend is the daemon one.
REPOSITORY is the directory path where the databases are stored. The directory must exist (it isn't created by the program).
As an example, the configuration file I use :
<Configurations> <Configuration target="emobdadmn"> <Service>1234</Service> <Repository>..\Repository</Repository> </Configuration> </Configurations>
This is the name of the package for the backend daemon, and you can download it at http://zeusw.org/download/emobdadmn/. This package contains all the sources for this application, and also the executable (emobdadm.exe) for Windows. For Linux, or Cygwin, there is a Makefile to build the executable.
If you have trouble with the Windows executable, take a look at http://zeusw.org/intl/windows_redist.
The emobdadmn application needs a configuration file, as described above, that you have to adapt to your needs.