Extending ISA Server Storage
This section describes how to add data for extensions to Microsoft Internet Security and Acceleration (ISA) Server 2006 or ISA Server 2004 using a FPCVendorParametersSets collection of FPCVendorParametersSet objects.
A third-party component must use the ISA Server configuration management facilities to store its configuration. These facilities hide the storage location (local registry or Configuration Storage server), and provide support for propagation to a Configuration Storage server, central backup-and-restore capabilities, and sharing with all array members. A vendor can create new objects or associate additional information with system-defined objects by means of the FPCVendorParametersSets collection.
In particular, data for an application filter can be added to the ISA Server configuration by using the FPCVendorParametersSets collection. For example, a list of Multipurpose Internet Mail Extensions (MIME) content types and file extensions that a filter needs for filtering traffic according to MIME content types and file extensions can be added to the FPCVendorParametersSets collection associated with the filter when it is installed; this data will be written to storage by means of the collection's Save method and will be available to the filter. After this extension is made to ISA Server, the vendor-specific data will be backed up with all other ISA Server configuration settings.
ISA Server storage is hierarchical. An extension developer can pick any supported node to extend. For example, you may want the extension to be per array, and therefore stored under the array node, or per computer, and therefore stored under the computer node.
To secure the information you store, use encrypted data in the FPCVendorParametersSet objects.