JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris DHCP Service Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Overview of Solaris DHCP Data Access Architecture

Modular Framework

DHCP Server Multithreading

Data Access Layers

The Framework Configuration Layer

The Service Provider Layer API

Data Store Containers

2.  Architecture Features for Module Writers

3.  Service Provider Layer API

4.  Code Samples and Testing


The Framework Configuration Layer

Functions implemented in are used by the Application/Service Layer to:

The /etc/inet/dhcpsvc.conf contains a number of configuration parameters for the DHCP service, including the following keywords relevant to the public module developer:


Public module to load. The value of RESOURCE matches the public module name. For example, the RESOURCE=SUNWfiles refers to public module Naming the Public Module and Data Store Containers explains the rules for naming public modules.


Location of DHCP containers within the data service that the public module exports. The value of PATH is specific to the data service. For example, a UNIX™ path name would be assigned to PATH for the SUNWfiles resource.


Configuration information specific to the public module. This is an optional keyword that you can use if the data service requires configuration information, such as authentication from the user. If you use this keyword, you must provide a public module management bean to prompt the user for information to set the keyword value. See Data Service Configuration and DHCP Management Tools. The module must also export the configure() function to receive the value of this keyword during module load time. See configure() for more information.

The Framework Configuration Layer also provides to the Service Provider Layer an optional API synchronization service, described in Synchronizing Access to File-System-Based Containers.