The Framework Configuration Layer

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

• locate, load, and unload public modules

• manage data container version changes

• access the data store containers

• manipulate data store records in the containers

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:

RESOURCE

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

PATH

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.

RESOURCE_CONFIG

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.