Directory Layout
Noojee Provision is deployed into a standard directory structure.
By default it is installed into /opt/njprovision with the following set of subdirectories.
/opt/njprovision
|--- config
NoojeeProvision.xml
log4j.xml
database.jocl
njprovision
sample.dhcp.conf
|--- sql
create.sql
createDB.sql
createSIP.sql
createVM.sql
|--- fileservice
|--- fileservice-vm
|--- handsets
|--- <directory for
each supported handset manufacturer>
|---templates
<handset specific provisioning files>
|--- lib
<java libraries (jars) for Noojee Provision>
Directory details
config
The configuration files used to control how Noojee Provision operates. 02. NoojeeProvision.xml settings is the key configuration file.
sql
SQL scripts used to initialise a My SQL database ready for Noojee Provision.
Fileservice
Noojee Provision is essentially a specialised TFTP/HTTP service designed for the provisioning of handsets. There are however some circumstances when you simply need to use Noojee Provision as a straight TFTP service. Any files located in the fileservices directory can be retrieved using Noojee Provision's TFTP service without any special processing of the request or the file.
Fileservice-vm
The fileservice-vm works in a similar way to the fileservice directory except that all files are treated as Velocity Macros and pre-processed using Velocity before the are served.
Handsets
- used to store each of the manufacturer specific files. A subdirectory exists for each manufacturer.
Lib
Tthe set of jars requried by Noojee Provision