Managing Large Binary Data Files (NSM Procedure)

Large binary data files that form a part of the configuration of Secure Access and Infranet Controller devices are handled differently from the remainder of the configuration in NSM. The size of some of these binary files could make configurations large enough to overload resources on the NSM server. Consequently, only the large binary files you specify are imported into NSM, and those files are configured as shared objects, which avoids duplication if they are applied to multiple devices.

To download a large binary data file and link that file into the Secure Access or Infranet Controller device configuration tree:

  1. In the Device Manager, right-click the device icon and select Import Device from the list to import the Secure Access or Infranet Controller device configuration. When the import job is finished, the device object configuration contains the MD5 stubs for each of the large binary data files.
  2. Upload each mandatory large binary data file onto the NSM client workstation. Use the device Web UI to upload binary files form the Secure Access or Infranet Controller device. Other files, such as ESAP configuration files, should be downloaded form the site of origin.
  3. Create a shared object in the NSM Object Manager for the binary file as follows:
    1. In the Configure panel of the NSM navigation tree, select Object Manager > Binary data, and then click the Add icon.
    2. In the New Binary Data dialog box, enter a name for the object, select a color for the object icon, add a comment if desired, and select the file you uploaded in Step 2.
    3. Click OK.
  4. Link the shared object to the corresponding node in the device configuration tree as follows:
    1. In the Device Manager, double-click the Secure Access or Infranet Controller device to open the device editor, and then select the Configuration tab.
    2. Navigate to the node in the configuration where you want to load the binary file. For example, to load an ESAP package, click Authentication and then select Endpoint Security. In the Host Checker tab, select Endpoint Security Assessment Plug-Ins, and then click the Add icon.
    3. Select the shared object. To continue the ESAP example, in the New Endpoint Security Assessment Plug-Ins dialog box, enter a version number, and select a shared binary data object from the Path to Package list.
    4. Click OK. If the object you want is not in the list, you can add it to the shared binary data list by clicking the Add icon. The Binary Data dialog box appears as in Step 3.
    5. Click OK to save the newly configured links.

Related Documentation