Customizing Config Store Registration

When an IVI driver is installed on an end user system, a number of entries for the driver must be created in the IVI Configuration Store. Information such as the driver's repeated capability physical names, supported IVI instrument classes, and IVI-C prefix is all required by the IVI specifications to be placed in the IVI Configuration Store by the IVI driver installer.

Nimbus maintains the IVI Configuration Store entries for a driver in a special XML file with the following name:

<project>.xml

This file (referred to simply as the Config Store XML file) contains all of the information that the Nimbus driver installer will use when the IVI driver is deployed on the end user system. This Config Store XML file is actually a complete "mini" IVI Configuration Store, with all of the requisite formatting and entries. The driver installer merges the contents of this file with the end-user's IVI Configuration Store file.

Customizing IVI Configuration Store registration for a Nimbus driver consists only of editing the Config Store XML file (<project>.xml) to add the desired entries. Editing the Config Store XML file can be performed in two ways:

1. Directly editing the Config Store XML with a text editor.

   Caution
   If you customize the Config Store XML file by directly editing it, you must take great care not to invalidate the file. Nimbus roundtrips this file automatically as the driver project is edited, so it must always be a valid XML file. It must also always comply with the IVI Configuration Store schema. Make certain that any edits performed directly on this file maintain its validity.

2. Using a 3rd-party IVI Configuration Store editor.

   One of the chief benefits of the Nimbus Config Store XML file being a complete IVI Configuration Store is that it can be edited using any available IVI Configuration Store editor, such as NI-MAX^® from National Instruments^®. The advantages of this approach are that there is no danger of corrupting the format of the Config Store XML file and that the customization can be performed without having to understand the details of the IVI Configuration Store file format.