openlsd.server.admin.LSDInitDBFromConfigFiles Class Reference

Collaboration diagram for openlsd.server.admin.LSDInitDBFromConfigFiles:

Detailed Description

Main Class to show an example of initialization of DB only from config files.
It creates no storage as they should be automatically created when it will be necessary. However, even if they would be automatically created after when needed, The Storage administrator should handle filesystems creations and mounts and so LSDStorage creation using the LSDAdmin function (or Web interface).

Warning: The size in Lehacy must be less than real size since encryption should add some bytes. In general, depending on average files size and crypto mode, 5 percent less than the real size should be enough.

Author:: Frederic Bregier LGPL


Static Public Member Functions
static void	main (String[] args)
Private Member Functions
	LSDInitDBFromConfigFiles (LSDLoadConfig llc)
boolean	initLSD ()
Private Attributes
LSDDbAdmin	admin = null
ConcurrentHashMap< Long, LSDLegacy >	LegacyHMap = null
LSDServerInstance[]	LSI = null
String	serverip = null

Constructor & Destructor Documentation

openlsd.server.admin.LSDInitDBFromConfigFiles.LSDInitDBFromConfigFiles ( LSDLoadConfig llc ) [private]

Create a LSDInitDB from driver ans server args

Parameters:

llc

Member Function Documentation

static void openlsd.server.admin.LSDInitDBFromConfigFiles.main ( String[] args ) [static]

Main Class to show an example of initialization of DB only from config files.

Parameters:

args

with 1-openlsddb client config file, and 2-openlsd server config file and 3-IP(or DNS entry) of LSD Server

boolean openlsd.server.admin.LSDInitDBFromConfigFiles.initLSD ( ) [private]

Sample of Initialization of LSD from DB point of vue: 4 IpPort, 4 Services and associated Legacies are created. If the Legacy are already created in DB, then nothing is done.